Unity 7 Roadmap: Public API, CLI and a Free MCP Bring the Editor to Non-Users and Coding Agents

In Brief:

• At Unite Seoul, Unity revealed its Unity 7 roadmap, introducing a public API and a command-line interface so artists, producers and developers can validate assets, ship builds and collaborate without needing full Editor access.
• A free-to-use MCP will wire coding agents like Claude Code and Cursor straight into Unity, and the Unity CLI can be used right now.
• An early beta is set for December 2026, followed by a full launch targeted for the first quarter of 2027.

Unity wants its Editor to be useful even to people who never launch it. Speaking at the Unite Seoul conference on July 21, the company detailed a Unity 7 roadmap centered on a public API and a command-line interface, letting artists, producers and developers validate assets, push builds and operate from their preferred tools without opening the full Editor. On top of that, a free-to-use MCP will link coding agents directly into Unity.

The company made its case plainly on X. “We’re opening the Editor to EVERYONE,” Unity wrote, noting that “a game isn’t built in the Editor alone.”

What the API opens up

For two decades, the Editor has been the one venue where work took place. The new API and services relocate portions of that work beyond it.

Adam Smith, senior vice president of product at Unity, explained that a coding agent could “plug in and validate a build,” or a producer might inspect a scene in a browser without ever launching the Editor. The MCP hooks large language model agents such as Claude Code and Cursor into a live project, granting access to the scene hierarchy, GameObjects, component values, console output and build settings.

The CLI ships now

Ahead of the full launch, the Unity CLI is already available. From a single binary it installs and manages editors, controls a running Editor via a script and runs live C# within a project.

An experimental package, com.unity.pipeline, allows the CLI to drive either a running Editor or a dev Player build through a local API. Teams surface their own commands using a [CliCommand] attribute. The unity command eval call executes C# live inside a running Editor or Player and hands back the result, without any project-level recompile or domain reload.

Since eval can touch whatever API a project is able to call, an agent has the same reach as Unity itself: rendering, physics, animation, the asset database and the Editor, along with any code the team has written.

Speed and a no-break upgrade

Unity 7 is powered by a modernized core built on CoreCLR. It pledges near-instant Play Mode, domain reloads that only affect the code that actually changed, and shader builds as much as 90% faster.

According to the company, moving on from Unity 6 won’t demand a conventional upgrade. Nothing needs to be rebuilt and there’s no new language, with Unity stating that “all projects, skills, and code will carry forward smoothly into the next generation.” Smith noted that foundational elements like CoreCLR and Surface Cache GI are being delivered and production-verified within Unity 6 releases before they arrive in Unity 7.

Timing

Early beta testing kicks off in December 2026, and the full release is slated for the first quarter of 2027.

Unity positioned the platform for teams where people and coding agents operate together, while stressing that the AI tooling is optional. “If your studio has committed to keeping AI out of your creative work—you’re not on the sidelines of this release,” Smith said. “Unity 7 is built for a future where humans and coding agents can work together. But the choice is always the team’s, not the platform’s.”

“Game development is changing faster than at any point in history,” said Matt Bromberg, president and CEO of Unity. “The future belongs not to the biggest team, but to those who can use new technology to create something unique and find an audience. Unity 7 is the platform that meets this moment.”