Know what references what.
Search project content, follow dependencies, find reverse references and understand where components are actually used.
ucp --index --scope AssetsA Unity-aware MCP bridge that lets coding agents inspect, change, compile, test and verify the real Editor — end to end.
ucp --installMCP config · skills · docs installeducp --index --scope AssetsAsset graph ready · GUID refs resolveducp --graph --scope Assets --timeout 300Semantic C# graph ready · Roslyn appliedThe missing interface
Unity Control gives coding agents a precise way to understand the project, operate the real Editor, and verify outcomes instead of guessing from source files alone.
Project intelligence
UCP gives coding agents a connected view of Unity content and C# behavior — enough to reason about impact without exposing the machinery behind it.
Search project content, follow dependencies, find reverse references and understand where components are actually used.
ucp --index --scope AssetsTrace call paths, state access, inheritance and Unity-aware relationships with semantic analysis.
ucp --graph --scope AssetsBuilt beyond scene CRUD
Unity Control is built around the costly parts of agentic Unity development: focus, project locks, raw logs, runtime state and unsafe YAML edits.
Find asset relationships, component usage and downstream impact without asking an agent to scan the entire project.
Trace calls, state access and inheritance with semantic confidence instead of relying only on text search.
See how a code change reaches the scenes, prefabs and assets that ship in the game.
Targeted queries return the answer an agent needs while keeping irrelevant project data out of context.
A deliberately small surface covers the development loop and preserves more context for the actual work.
Editor-aware operations protect serialized content and make high-impact changes explicit.
Documented payload budget
UCP replaces broad project dumps with narrow questions and compact answers.
| Workflow | Broad output | Unity Control | Reduction |
|---|---|---|---|
| Single UI assertion | ~3,865 tok | ~30 tok | 99.2% |
| Filtered UI snapshot | ~3,865 tok | ~200 tok | 94.8% |
| Structured query output | JSON baseline | Text default | ~50% |
Payload guidance from current UCP operations. Actual usage varies by project and query. The public benchmark reports output size only; internal indexing and query strategy remain undisclosed.
Full editor access
Resolve dependencies, reverse references, component usages and prefab contents from a persistent project index.
Trace calls, reads, writes and inheritance with Roslyn semantics plus Unity lifecycle, assembly, attribute and asset-reference metadata.
Inspect, create, modify, compile, test, profile and verify Unity through a compact MCP interface.
Local by design
A focused control layer connects your development tools with the Unity Editor and returns predictable, structured results.
Install from npm
Install the latest UCP CLI globally, then let it configure the MCP client, skills and local documentation.
npm install -g @gmg-studio/ucp@latestucp --install02Restart your MCP clientCommon questions
Unity Control is an MCP bridge and command-line tool that gives coding agents a Unity-aware way to inspect projects, operate the Editor, run verification, and reason across code and assets.
The asset index maps Unity content and references. The semantic code graph maps C# behavior and relationships. Together they help an agent understand the likely impact of a change before editing.
No. UCP connects automation and AI coding tools to the real Unity Editor. Unity remains the source of truth for serialized assets, play mode, compilation, tests, and runtime state.
UCP runs as an MCP server over standard input and output, so it is designed for MCP-compatible coding clients. Install the npm package, then run ucp --install to configure the supported client environment.