Unity CLI Is Free With Unlimited MCP — Terminal-Native Agents, live C# eval, and CI Without Hub Headaches

On July 21, 2026, @unity posted the line CI engineers have been waiting for: the Unity CLI is free, Unity MCP is free, and there are no concurrency limits on the MCP server. Same Unite Seoul week as the Fortnite cross-engine demo — but this announcement targets a different pain point: AI agents and build pipelines that could write C# but could never see whether the game actually worked.

bunpav's take: Unity is betting that the next platform war is not HDRP vs Lumen — it is who gives coding agents a closed feedback loop inside the engine. The unity command eval REPL is the headline. "Free with no concurrency limits" is the trust repair after the runtime-fee debacle still haunting replies under Unity's own tweet.

TL;DR — what people are actually asking

What did Unity announce?

Unity's July 20, 2026 tech blog — "Meet the Unity CLI: manage Unity from your terminal" by VP Authoring Platform Etienne Whittom — ships three layers that stack:

Unity's social post added the pricing punchline missing from older engine-tooling models:

"We want to remove barriers to innovation, so we are making these tools free! Both the CLI and MCP will be free, with no concurrency limits on the MCP server."

For teams burned by per-seat agent tooling, that concurrency line matters as much as the dollar price — CI farms can run parallel agent jobs without hitting an artificial cap.

How do you install and use it?

Unity documents a beta-channel install — no Unity Hub UI required:

# macOS or Linux
curl -fsSL https://public-cdn.cloud.unity3d.com/hub/prod/cli/install.sh | UNITY_CLI_CHANNEL=beta bash

# Windows (PowerShell)
$env:UNITY_CLI_CHANNEL='beta'; irm https://public-cdn.cloud.unity3d.com/hub/prod/cli/install.ps1 | iex

Then explore:

unity --help
unity install 6000.2.10f1 -m android ios webgl
unity editors --format json
unity open /path/to/project
unity auth login

Automation-friendly details from the blog:

Install an editor with modules in one line; list module IDs with unity modules list 6000.2.10f1. Unity claims the native binary starts noticeably faster than the old Hub headless path (-- --headless) — meaningful when agents fire dozens of calls per job.

What is com.unity.pipeline?

The Pipeline package turns a running Unity 6.0 LTS+ Editor into a programmable automation target. Add it to a project:

unity pipeline install
unity pipeline list

Register custom commands with attributes — no manual registration step:

using Unity.Pipeline.Commands;
using UnityEngine;

public static class MyPipelineCommands
{
    [CliCommand("greet", "Log a greeting and return its length")]
    public static int Greet(
        [CliArg("name", "Who to greet", Required = true)] string name)
    {
        Debug.Log($"Hello, {name}!");
        return name.Length;
    }
}

Run from terminal: unity command greet --name World

The connected Editor self-describes available commands when you run unity command with no arguments — important for agents that discover tools at runtime instead of relying on hardcoded lists.

Experimental caveat: Unity labels Pipeline experimental; expect API churn. Fine for CI labs and agent prototypes — verify stability before production release gates depend on it.

Dev Player runtime hook

Pipeline is not Editor-only. Drop the runtime component into a development build and aim the CLI with:

unity command --runtime <player exec name> ...

Unity documents this as localhost-only, off by default — for dev/QA builds, never production. Same API surface lets scripts pull live logs, query runtime state, or hot-reload in a playing build.

What makes unity command eval different?

Registered [CliCommand] methods cover anticipated operations. unity command eval covers everything else — a Roslyn-compiled C# expression on the Editor main thread:

unity command eval "return Application.version;"
unity command eval "return UnityEditor.EditorApplication.isPlaying;"
unity command eval "var s = Application.dataPath; return s.Length;" --json
unity command eval_file "path/to/script.cs"

Unity's demo video (embedded in the tech blog) shows the agent loop:

1. Developer pastes: "the player sometimes falls through the floor"
2. Agent evals the live scene — finds a collider disabled at runtime
3. Agent re-enables collider, re-enters Play mode, verifies fix
4. No human relaying console screenshots

That closes the gap between "LLM wrote a script" and "LLM confirmed the script fixed the bug" — the same verification problem Roblox Build solves on mobile with retention-ranked publishing instead of terminal REPL.

Security: eval power is gated behind a security token. Treat token leakage like handing someone remote Editor access — because functionally, it is.

MCP Mode — why not kill Unity MCP?

Unity's X thread addressed the obvious migration question: Unity MCP remains fully supported. The CLI adds "MCP Mode" so existing MCP-based agents keep working while teams test Pipeline integrations.

Third-party assistants, Unity's in-Editor AI suite, and custom scripts all consume the same execution layer per Unity's blog — Unity AI reasons; CLI/Pipeline executes.

What is the community actually arguing about?

Replies under Unity's announcement split into predictable camps — worth addressing directly:

"Terminals should work INSIDE Unity, not outside it." Developer @lamiancegames captured the UX complaint: alt-tabbing between Editor and terminal breaks flow for artists and designers. Fair — the CLI targets automation, CI, and agents, not replacing the Editor for human iteration. Unity 7's pitch is "whole team contributes" — CLI for pipeline roles, Editor for creative roles.

"How much does it cost?" / "Paid?" Unity answered: free, including MCP without concurrency limits. Several replies treated this as suspicious — legacy of the 2023 runtime fee announcement that Unity later walked back. Trust is a separate product from tooling.

"What's the catch?" Honest answers today:

• Pipeline and eval are powerful and experimental
• eval requires token discipline
• Player runtime API is dev-build only
• Unity still sells cloud builds, ads, Vector monetization — free CLI does not mean free everything

"Free with no concurrency limits is huge for CI." @AgentOrToy nailed the enterprise angle — per-seat agent costs blocked serious pipeline adoption. Removing the cap is a real friction cut.

"MCP mode lets teams keep old toolchain while testing new integrations." Pragmatic — Unity is not forcing a day-one MCP rip-and-replace.

How does this fit Unity 7 and Fortnite week?

Unite Seoul 2026 bundled three narratives:

Unity 7's "Open, Collaborative Ecosystem" pillar explicitly names CLI + MCP. You can start on Unity 6 LTS today without waiting for Unity 7 GA in Q1 2027.

For indie teams using AI-generated assets in Unity or the 48-hour game jam pipeline, the CLI does not replace mesh import — it replaces "did the import break Play mode?" guesswork with agent-verifiable checks.

Unity CLI vs Unreal / Godot agent paths

Unity's bet is structured JSON + live eval beats scraping Editor logs — the same design choices that make CI reliable make LLM tool calls reliable.

What should developers do this week?

1. Install the CLI beta — run unity --help on a throwaway machine first; use unity doctor if auth or PATH fails.
2. Add Pipeline to one test project — unity pipeline install, register a trivial [CliCommand], confirm unity command sees it.
3. Try eval on a known bug — reproduce a small Play-mode issue and script an eval inspection before trusting an agent on production repos.
4. Keep MCP running if it works — enable MCP Mode when ready; no forced migration deadline announced.
5. Do not enable Player runtime API in shipping builds — Unity's docs say dev/QA only, localhost-only.
6. Join the discussion — Unity linked CLI Discussions and the full tech blog from their X thread for feedback that shapes GA.

Caveats — read before you wire production CI

• Experimental Pipeline — APIs may change; pin versions in CI images.
• eval is not sandboxed magic — token-gated full Editor API access; compromised tokens are catastrophic.
• Trust is earned separately from pricing — free tooling does not erase runtime-fee history; evaluate Unity's business model for your studio independently.
• Human creatives may hate the terminal — CLI complements Editor; it does not replace in-Engine UX for art and level design.
• Brew/winget/apt coming soon — curl install is beta-channel today; check docs before standardizing org-wide.

Related reading

• Unity x Fortnite integration — Unite Seoul 2026 demo
• Roblox Build — mobile AI game creation July 2026
• The game jam 3D asset pipeline — 48-hour workflow
• AI-generated 3D models in Unity and Unreal — import survival guide
• Auto-rigging explained — skeletons for Unity Humanoid Avatar
• Unity CLI tech blog — Meet the Unity CLI
• Unity CLI Discussions
• Unity 7 roadmap — Unite Seoul investor release

CLI commands, Pipeline package status, and pricing are accurate as of publication (July 21, 2026). Unity labels Pipeline experimental — verify current docs before production CI hardening.