接入你的智能体
從發布者安裝。不是 PlugMCP 端點。
遠端 URL 還是本機指令? 兩種安裝方式的差異
Give your AI agent 179 commands to build Unity scenes, write C# scripts, validate builds, and ship games — with automatic rollback when things go wrong.
179 CLI commands · 12 MCP tools · 966 PR .NET tests · Windows / macOS / Linux
Benchmarked head-to-head against the official Unity CLI (1.0.0-beta.2 + com.unity.pipeline) on the same editor session — faster round-trips, smaller responses, and every measured gap absorbed the same day. See the benchmark.
Quality gates: every PR runs the .NET Shared/Core/Cli/Mcp test suites on Windows, macOS, and Linux. Unity Editor-dependent validation is separated into the Unity Integration workflow, with init, sample-project doctor, check, scene hierarchy, player-settings set/get, and workflow verify evidence uploaded from nightly/manual runs. Unity Integration requires either a UNITY_LICENSE or UNITY_SERIAL GitHub secret.
Contributors: see CONTRIBUTING.md for the test trust checklist, flaky-test policy, command sync checklist, and Unity live-validation split.
AI agents can write code, but they can't build games — because Unity has no programmatic interface for scene editing, asset management, or project validation.
Existing Unity MCP servers try to fix this, but they create new problems for AI agents:
unityctl is a .NET CLI + MCP server that turns Unity Editor into a programmable API.
For AI agents, this means a closed-loop automation cycle — the agent doesn't just execute commands, it can verify results, diagnose failures, and recover from mistakes:
Other tools give agents hands. unityctl gives agents hands, eyes, and a safety net.
AI agent costs are dominated by tool schemas sent every turn. unityctl uses on-demand schema loading:
The CLI exposes 179 entry points, including convenience wrappers. The 12 MCP
tools keep prompts small by loading 171 canonical command schemas on demand
through unityctl_query, unityctl_run, and unityctl_schema.
Standalone binary — no .NET SDK required (recommended):
# macOS (Apple Silicon) — swap in unityctl-osx-x64 / unityctl-linux-x64 as needed
curl -L https://github.com/Jason-hub-star/unityctl/releases/latest/download/unityctl-osx-arm64.tar.gz | tar xz
./unityctl --version
Windows: download unityctl-win-x64.zip from Releases and unzip.
Each archive contains a self-contained unityctl + unityctl-mcp executable and the embedded Unity plugin template.
Or via .NET tool (requires .NET 10 SDK):
dotnet tool install -g unityctl
dotnet tool install -g unityctl-mcp
Optional agent workflow skill for Claude Code and Codex:
npx skills add Jason-hub-star/unityctl \
--skill unityctl-workflows \
-a claude-code -a codex
The skill teaches agents to discover the live command surface, target the right Unity project, and close every edit with structured readback and verification.
Bootstrap notes:
--source accepts a local Unityctl.Plugin folder or a Git URL: https://github.com/Jason-hub-star/unityctl.git?path=/src/Unityctl.Plugin#v0.6.6# 1. Install the Editor plugin
unityctl init --project /path/to/project \
--source "https://github.com/Jason-hub-star/unityctl.git?path=/src/Unityctl.Plugin#v0.6.6"
# 2. Open the project in Unity Editor, then verify connectivity
unityctl ping --project /path/to/project --json
unityctl status --project /path/to/project --json
# 3. Start building
unityctl gameobject create --name "Player" --project /path/to/project
unityctl component add --id "<PlayerId>" --type "Rigidbody" --project /path/to/project
unityctl scene save --project /path/to/project
# 4. Validate
unityctl project validate --project /path/to/project --json
# 5. Build
unityctl build --project /path/to/project --dry-run # 13 preflight checks
One command per client — it merges into the existing config instead of replacing it:
unityctl mcp install --client claude-code # or cursor / codex
unityctl mcp install --client vscode --project . # VS Code is workspace-scoped
unityctl mcp install --client cursor --dry-run # preview, writes nothing
Or add it by hand:
{
"mcpServers": {
"unityctl": {
"command": "unityctl-mcp"
}
}
}
See GitHub Releases for version history.
MIT — see LICENSE
Unity control plane for AI agents — 178 CLI commands, 12 MCP tools, headless CI/CD, undo rollback, and closed-loop verification.
工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
Unityctl 透過 stdio 在本機執行。
上次檢查時間:2026-10-27。 Unity control plane for AI agents — 178 CLI commands, 12 MCP tools, headless CI/CD, undo rollback, and closed-loop verification.