Give your AI agent full control of the Unity Editor.
Scenes, objects, assets, builds, tests, profiling - everything, from the terminal.
Documentation · Releases · Discord · npm
Unity has no CLI. If an agent wants to move assets, run tests, tweak a material, or trigger a build - it can't. The editor is a GUI-only black box.
UCP opens that box. It's a Rust CLI that connects to a bridge package running inside the Unity Editor over localhost WebSocket. Every editor operation becomes a structured command with --json output. The agent talks to the CLI, the CLI talks to Unity, and Unity does the work.
No cloud. No accounts. No plugins to configure. Install the bridge, connect, and the agent has the editor.
The entire Unity Editor lifecycle - from bootstrapping a project to shipping a build - exposed as structured, automatable operations.
An agent can search every reference to a material, rename and relocate hundreds of assets in a single batch, verify nothing broke, recompile, and run the full test suite - without a human touching the editor. Moves go through Unity's AssetDatabase, so GUIDs, .meta files, and serialized references stay intact.
Write scripts in the workspace, recompile through the bridge, assemble GameObjects and components in the live scene, persist them as prefabs, capture screenshots for visual verification, and run tests - all in one continuous agent loop. The agent never leaves the terminal.
Connect to the editor, trigger compilation, run edit-mode or play-mode test suites with structured JSON results, configure scripting defines, build the player, and shut down cleanly. Every step is gated and machine-readable.
Start a profiler session, enter play mode, capture frame data, analyze hot paths and hierarchy timings, export structured snapshots - all programmatically. The agent can diagnose performance issues without a human opening the profiler window.
Snapshot the scene hierarchy to discover objects, focus the scene camera, capture screenshots, modify properties, capture again. The agent gets spatial awareness of the Unity scene and can iterate visually.
npm install -g @mflrevan/ucppnpm / cargo / binary
# pnpm
pnpm add -g @mflrevan/ucp && pnpm approve-builds
# From source
git clone https://github.com/mflRevan/unity-control-protocol.git
cd unity-control-protocol/cli && cargo build --releaseOr download a binary from GitHub Releases.
Then in any Unity project:
ucp install # add the bridge package
ucp open # launch Unity and connect
ucp doctorvalidates your setup - Unity resolution, bridge health, and project serialization settings.
UCP ships as a Claude Code plugin. The skill file (not limited to Claude Code, can be used in other harnesses too) teaches the agent the full control surface, common workflows, and edge-case handling.
# Local, only for the duration of the session (https://code.claude.com/docs/en/plugins-reference#plugin-caching-and-file-resolution)
claude --plugin-dir /path/to/unity-control-protocol
# Marketplace, installed for future sessions
/plugin marketplace add mflRevan/unity-control-protocol
/plugin install ucp@unity-control-protocolEvery command supports --json - agents can always get structured, parseable output.
| Platform | Architecture |
|---|---|
| Windows | x64 |
| macOS | x64, ARM (Apple Silicon) |
| Linux | x64 |
Unity 2021.3+. Tested across Unity 6 (6000.0 – 6000.4).
cli/ Rust CLI - the ucp binary
unity-package/com.ucp.bridge/ Unity Editor bridge package
npm/ npm distribution wrapper
docs/ Markdown documentation source
website/ Docs site (unityctl.dev)
skills/ AI agent skill files
scripts/ Build, validation, and release helpers
See CONTRIBUTING.md for development setup, testing, and release workflow.