Claude Code marketplace catalog for Unity Control Protocol.
npx claudepluginhub mflrevan/unity-control-protocolUnity Editor automation plugin powered by the Unity Control Protocol base skill.
CLI-first automation for the Unity Editor.
SVG logo | Discord | Releases | Docs | npm
UCP is a cross-platform CLI plus Unity Editor bridge for programmatic control of Unity projects. It is built for local automation, AI agents, CI/CD, and repeatable editor workflows across scenes, objects, assets, importer settings, packages, tests, builds, and profiler inspection.
UCP is split into two parts:
ucp: a Rust CLI for operators, agents, and scriptscom.ucp.bridge: a Unity Editor package that exposes editor operations over localhost WebSocket JSON-RPCThe bridge writes .ucp/bridge.lock in the Unity project root. The CLI reads that lock file, authenticates with a per-session token, and then talks to the editor through the bridge.
Most bridge-backed commands can now auto-start Unity when the project and editor path can be resolved.
cli/: Rust CLI exposed as ucpunity-package/com.ucp.bridge/: Unity bridge packagenpm/: npm wrapper that downloads the matching released binary and bundles the bridge payloaddocs/: markdown docs sourcewebsite/: Vite/React docs site built from docs/ and skills/skills/unity-control-protocol/SKILL.md: canonical agent skill fileThis is the current happy-path workflow for real project use:
cd /path/to/MyUnityProject
ucp install
ucp open
ucp connect
ucp scene snapshot
ucp scene focus --id 46894 --axis 1 0 0
# edit files locally in your workspace
ucp compile
ucp play
ucp screenshot --view scene --output capture.png
ucp stop
ucp run-tests --mode edit
ucp close
Recommended usage notes:
ucp compile for script iteration.ucp files read|write|patch when you intentionally want bridge-mediated project file I/O.ucp files write|patch automatically reimport edited Unity assets and .meta files under Assets/ and Packages/ unless you pass --no-reimport.ucp asset import-settings ... over hand-editing .meta files.ucp asset reimport <path> when you intentionally deferred apply work or changed an imported asset on disk outside Unity's importer workflow.ucp packages ... for Unity Package Manager workflows and ucp packages unitypackage ... for selective .unitypackage inspection/import.ucp open when you want an explicit lifecycle step.ucp connect when you want "make sure Unity is running and verify the bridge is healthy" in one command.ucp scene snapshot to discover instance IDs, then ucp scene focus and ucp screenshot for visual iteration loops.npm install -g @mflrevan/ucp
pnpm add -g @mflrevan/ucp
pnpm approve-builds
git clone https://github.com/mflRevan/unity-control-protocol.git
cd unity-control-protocol/cli
cargo build --release
This repository is also Claude Code marketplace-compatible.
For local development or one-off testing:
claude --plugin-dir .
For marketplace-style installation from GitHub:
/plugin marketplace add mflRevan/unity-control-protocol
/plugin install ucp@unity-control-protocol
The default Claude Code marketplace install exposes only the base Unity automation skill:
/ucp:unity-control-protocolRepository support files for Claude Code users:
.claude-plugin/plugin.json: plugin manifest.claude-plugin/marketplace.json: root marketplace catalogskills/unity-control-protocol/SKILL.md: base skill shipped to Claude CodeFrom a Unity project root:
ucp install
Default behavior:
com.ucp.bridge dependency into Packages/manifest.json--confirmfile: dependencyExplicit local bridge development modes:
ucp install --devucp install --embeddeducp install --bridge-path <path>ucp open.ucp/bridge.lockucp connect