Unity MCP Server
Wtzd8645/Unity-MCP-Server
Integração bidirecional Claude ↔ Unity Editor via protocolo MCP
Ver no GitHubServidor MCP que expõe controle total da Unity Editor via HTTP/Named Pipe, permitindo que clientes Claude (e outros) leiam, escrevam e executem operações em projetos, cenas, GameObjects, prefabs e assets. Integra um gateway .NET que traduz requisições MCP em comandos nativos do editor.
Instalação
npx convez-ai Wtzd8645/Unity-MCP-Server1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Automação de workflows de criação de cenas e prefabs via IA
- Leitura e manipulação de estruturas de projeto e GameObjects remotamente
- Assistência IA contextualizada dentro do pipeline de desenvolvimento Unity
- Execução de builds e testes automatizados disparados por agentes Claude
Veredito

MCP server robusto e bem-arquitetado para integrar Claude profundamente com o workflow Unity. Exige conhecimento técnico de C#, .NET e MCP, mas oferece controle granular da editor com abstrações bem definidas (project/scene/gameobject/asset modules).
README
A tradução para o português deste README ainda está na fila.
Unity MCP Server
This repository is the Unity package root and contains two components:
Editor/: Unity Editor control package source (HTTP/Named Pipe tool endpoint)Gateway~/: MCP gateway source process (.NET, streamable HTTP)
Unity Editor Control
Use the Control package and open:
Tools/Unity MCP Control
The control window manages both:
- Control endpoint lifecycle (start/stop and settings)
- Gateway process lifecycle (start/stop/restart and process monitoring)
The settings panel currently provides:
- Gateway process settings such as
Dotnet ExecutableandGateway Project Path Enabled Modulesas a multi-select dropdown sourced fromGateway~/schemas/mcp-tool-modules.jsonControl Transportwith transport-specific fields shown conditionally- shared control settings such as timeout, path allowlist, component allowlist, and auto-start flags
By default, MCP clients connect to the gateway at http://127.0.0.1:38100/mcp.
The gateway calls Unity Control over Named Pipe, so only one HTTP endpoint is exposed.
Runtime Contract
Common environment variables:
UNITY_MCP_ROOT(default should point toGateway~/)UNITY_MCP_ENABLED_MODULES(comma-separated module names such asproject_read,scene_read,prefab_read,asset_read)UNITY_MCP_GATEWAY_TRANSPORT(streamable-httpdefault, orstdio)UNITY_MCP_STREAMABLE_HTTP_URL(defaulthttp://127.0.0.1:38100/mcp)UNITY_MCP_CONTROL_TRANSPORT(pipedefault, orhttp)UNITY_MCP_CONTROL_HTTP_URL(optional HTTP control endpoint, defaulthttp://127.0.0.1:38110/)UNITY_MCP_CONTROL_PIPE_NAMEUNITY_MCP_CONTROL_TIMEOUT_MSUNITY_MCP_ALLOWED_PATH_PREFIXESUNITY_MCP_ALLOWED_COMPONENT_TYPES
Current runtime tool names are defined by the active schemas in Gateway~/schemas/ and routed by Editor/Control/ControlToolDispatcher.cs.
Module Taxonomy
The runtime taxonomy is target-first and operation-second:
project_read,project_execute,project_writeeditor_read,editor_execute,editor_writeruntime_read,runtime_executescene_read,scene_execute,scene_writegameobject_read,gameobject_writeprefab_read,prefab_writeasset_read,asset_write
Current authoring boundaries are:
scene_*: scene container and scene asset lifecycle onlygameobject_*: scene live object inspection and mutation, including scene component operationsprefab_*: prefab module boundary, with explicitprefab_asset_*andprefab_instance_*tool names under itasset_*: generic project asset search, inspection, import, creation, and file-level mutation
AI temporary scene workflows should prefer additive scene loading and closing over replacing the user's current loaded scene setup.
Scene context-changing tools use dirtyEditorContextPolicy so dirty loaded scenes and dirty Prefab Stage sessions are handled without interactive save prompts.
The current foundation includes:
- project read surfaces plus build-target switch, player build, and test execution tools
- editor selection and console tools
- runtime playmode status and start/stop tools
- scene open/close/create/save tools
- scene live GameObject and component read/write tools
- prefab asset inspection and prefab instance lifecycle/override tools
- asset search/reference tools plus import, copy/move, rename, delete-to-trash, and native asset creation tools