Potencialize seu agente
Instalação do publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
Ainda não há uma versão empacotada no registro. Siga o README do repositório.
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
Unity MCP Server — 268 tools for AI-assisted game development. Connect Claude, Cursor, or any MCP client to Unity Editor & Unity Hub. Scene management, GameObjects, components, builds, profiling, Shader Graph, Amplify, terrain, physics, NavMesh, animation, MPPM multiplayer & more. Free & open source by AnkleBreaker Studio.
Build worlds. Coordinate agents. See every action. Connect your AI assistants to scene authoring, running games, multiplayer scenarios, tests, builds and profiling through Model Context Protocol. Built by AnkleBreaker Studio for workflows that span more than one editor and one assistant.
Get started · Watch the demos · Measured improvements · Multiple projects · Tool catalog · Changelog
Counts reflect the checked-in definitions; optional tools require their corresponding Unity packages. The advanced proxy also discovers routes advertised by newer plugins.
Neon brick breaker: scene construction, materials, gameplay scripts and visual iteration, with the assistant and Unity visible together.
Recorded, accelerated excerpts. The silent videos export the same recordings as the GIFs; their duration is not a build-time benchmark. Media details and example prompts.
The combination is the strength: routing, scheduling, multiplayer controls and observable results in one workflow. See choosing a Unity integration for a sourced comparison.
Why choose AnkleBreaker? Each agent keeps its project identity, each editor has its own queue, and supported actions leave a history you can inspect and undo. Advanced tools extend that workflow into multiplayer iteration, Unity Hub and project-specific integrations. Those behaviors have dedicated regression checks and real-editor evidence, not just a feature list.
Install from source: the commands below install main in both repositories, including the improvements documented here. Published npm packages and version tags may lag behind main.
In Unity, open Window → Package Manager → Add package from git URL:
https://github.com/AnkleBreaker-Studio/unity-mcp-plugin.git#main
The MCP status dropdown appears automatically in Unity's main toolbar. Open the Dashboard from it, Window → AB Unity MCP, or Tools → AnkleBreaker → Unity MCP. Verify the bridge is running there. If you previously hid the indicator, choose Show Toolbar Status. Toolbar and menu access.
Use Node.js 18 or newer; a maintained Node.js LTS is recommended.
git clone --branch main https://github.com/AnkleBreaker-Studio/unity-mcp-server.git
cd unity-mcp-server
npm ci
For clients that accept an mcpServers JSON configuration:
{
"mcpServers": {
"unity": {
"command": "node",
"args": ["C:/path/to/unity-mcp-server/src/index.js"]
}
}
}
Use the absolute path to your checkout. On macOS and Linux, use its Unix path. Clients with another configuration format need the same command and arguments. Restart or reconnect the client's MCP session after editing the configuration.
Editor discovery is automatic. Unity Hub is only needed for Hub commands; set UNITY_HUB_PATH if it is installed elsewhere. See all configuration options.
List my running Unity projects. Select my prototype, inspect its scene and compilation errors, create a platform, then capture the scene so I can review it.
Find the multiplayer tools. List my MPPM scenarios and the players configured in the selected project.
Inspect the scene's memory use and largest objects, then show me the actions performed by each agent.
Terrain, houses, materials, trees, fences and paths: the assistant constructs a scene and inspects the result as it goes.
Multi-room construction, lighting adjustment and a first-person walkthrough in the recorded project.
Keep an agent on your game, another on a package test project, and use the multiplayer tools to inspect Host/Client scenarios. Project routing and per-agent scheduling are separate responsibilities, so requests retain their destination while waiting for Unity.
unity_list_instances and identify the project by name and path.unity_select_instance with projectName or a discovered port.port on editor calls when coordinating simultaneous tasks.Discovery checks the live Unity identity before adopting a port, including registry and default-port fallbacks. Named selection keeps that identity through verification, and stale discovery cannot overwrite a newer project choice. Identity, concurrent selection and compatibility.
{"name":"unity_editor_state","arguments":{"port":7891}}
7891 is an example; use the port returned by discovery. MCP callers can pass _meta.agentId (or the compatible _meta.agent_id) to keep agent selections and queue attribution separate. Each stdio process has its own default identity.
Within an editor, the plugin serializes writes and batches up to five reads per update. Different editor processes have independent queues. Simultaneous agents can still make conflicting edits to the same object, so assign clear ownership for shared scene work.
Discover advanced capabilities with unity_list_advanced_tools. Filter by category or search, retrieve the schema for the tool you need, then call it through unity_advanced_tool. Full category guide and examples →
These are example prompts, not automatic scripts. Select the intended project first and let the assistant discover the current tool schemas and available packages.
Measurements use separate before/after fixtures and historical baselines on Unity 6000.6.2f1 / Windows. Each linked report states its scope. These results do not measure whole-editor FPS or establish a speed ranking against other MCP products.
The plugin declares Unity 2021.3.18f1+ support. Server and plugin versions advance independently and do not need matching version numbers. Current live validation uses Unity 6000.6.2f1 on Windows; minimum-version C# compilation also passes. Actual older-editor execution is deferred.
263 server tests pass across eight CI configurations (Node 18/20/22/24 on Windows/Linux), and the plugin's registry check covers 338 routes. Real-editor workflows include mixed released/current components, two editors, MPPM Host/Client, ParrelSync and actual script reloads. These checks have different recorded source checkpoints; the delivery summary identifies them and the remaining coverage limits.
Run the server's ordinary regression suite:
npm ci
npm test
These tests run the real MCP stdio process against isolated mock bridges. The companion plugin's Unity runner and the server's opt-in live suites are documented with their prerequisites and results in the linked guides. Full evidence and follow-up limits · Final documentation and media checks.
Actual Dashboard capture from a Unity 6.6 validation project. The deliberately long agent/request names exercise layout behavior; displayed counters belong to that test session.
The plugin Dashboard shows queue activity, agent sessions, HTTP activity and recent actions. Agent cards update in place, sections remember their state, and long request text stays readable through tooltips. HTTP counters include input refused before ticket creation, body traffic and domain reloads. Dashboard behavior · HTTP fields and measurements.
Requested editor-window captures preserve keyboard focus, identify ambiguous windows explicitly and bound native image allocations. Docked captures exclude tab chrome; inactive tabs require an explicit temporary-switch option. Owned Windows fixtures verify actual UI Toolkit/IMGUI pixels and Dashboard layouts at 360 and 640 px.
Code execution reuses bounded compiler metadata and reports cache activity in unity_editor_state.codeExecution. A local Unity 6.6 benchmark of twenty small calls fell from 15.85 s to 1.01 s; this measures one workload, not every Unity operation. Execution behavior, measurements and limits.
unity_queue_info, unity_agents_list and unity_agent_log. Ticket status separates queue wait and processing time; queue info also exposes inactive-session retention and evictions. Monitoring fields and measurements →isCompiling: false, then inspect compilation errors. An empty error list during compilation is inconclusive.UNITY_MCP_COMPACT_TOOLS=1. Full parameter documentation remains available through advanced discovery.Which AI clients can use it? Clients that support spawning an MCP stdio server can connect using the Node command above. Configuration syntax and image/tool support depend on the client; no specific model is required by the bridge.
Do I need every optional Unity package? No. The core bridge works independently of optional integrations. Enable the relevant categories and install the packages needed for your workflow; use advanced discovery to inspect available tools.
Can several assistants work on the same project? Yes. Requests are attributed and scheduled per agent. Assign ownership of shared objects: scheduling does not resolve conflicting design changes.
Can I undo every AI action? Supported Unity writes have named undo groups and history. Filesystem operations, arbitrary code and some deferred workflows have different recovery limits. Inspect the Undo contract before relying on rollback.
Is this already a released upgrade? No. This README documents the modernization branch. Existing server/plugin version numbers remain independent; the installation instructions above select the development preview explicitly.
How does it compare? Start with the sourced comparison: routing, fair scheduling, retry recovery, multiplayer controls, monitoring and tool discovery. The measured gains above compare AnkleBreaker revisions under specific workloads.
Support development through GitHub Sponsors or Patreon. Report reproducible issues with the server version, plugin version, Unity version and the affected tool.
Distributed under the AnkleBreaker Open License v1.0. See LICENSE for the full terms, including attribution and restrictions on reselling the tool. AI client and model usage costs are separate.
Unity MCP Server — 268 tools for AI-assisted game development. Connect Claude, Cursor, or any MCP client to Unity Editor & Unity Hub. Scene management, GameObjects, components, builds, profiling, Shad
Visão geral
Unity MCP Server — 268 tools for AI-assisted game development. Connect Claude, Cursor, or any MCP client to Unity Editor & Unity Hub. Scene management, GameObjects, components, builds, profiling, Shader Graph, Amplify, terrain, physics, NavMesh, animation, MPPM multiplayer & more. Free & open source by AnkleBreaker Studio.
Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Unity roda localmente via stdio.
Última verificação: 2026-11-16. Unity MCP Server — 268 tools for AI-assisted game development. Connect Claude, Cursor, or any MCP client to Unity Editor & Unity Hub. Scene management, GameObjects, components, builds, profiling, Shader Graph, Amplify, terrain, physics, NavMesh, animation, MPPM multiplayer & more. Free & open source by AnkleBreaker Studio.