Let an AI agent drive the Editor
With MCP, your AI assistant reads your real Console, inspects your real scene and edits your real scripts, instead of guessing from what you paste into a chat box.
15 chapters About 150 minutes in all Free, no signup
Every command and config here was verified on a working setup on 10 Aug 2026: Unity 6000.3.14f1, AI Relay 1.0.12-build.97, mcpforunityserver 10.0.0, Windows 11.
Two servers, one nickname
Most confusion about "Unity MCP" comes from there being two separate projects with the same name. Unity ships an official relay in the AI Assistant package from Unity 6.3, and a community server has existed for longer and supports older versions. Their install steps and config are not interchangeable.
Pick one deliberately
The comparison chapter puts both side by side, tested on the same machine, so you can choose before you spend an evening on the wrong one.
Then keep your project safe
An agent editing scenes is useful and risky. Safety and git hygiene covers what to commit, which tools to restrict, and how to recover.
All 15 chapters, in order
- What is Unity MCP Letting an LLM drive the Editor
- Official vs Community Server Unity AI Relay or MCP for Unity
- Installing Unity MCP Both servers, start to finish
- Connect Claude Code Config, transport, first run
- Connect Cursor mcp.json, stdio, troubleshooting
- Connect VS Code Copilot Agent mode and tool approval
- Prompt Recipes Prompts that actually work
- Safety & Git Hygiene Never let an agent eat your scene
- What The Tools Actually Do A reference for the Unity MCP tool surface
- Debugging With MCP One bug, start to finish
- LLMs Inside Your Game When it works, and when it does not
- Calling Claude From Unity UnityWebRequest, JSON, and the reply
- API Key Security Why your key cannot ship in the build
- Streaming NPC Dialogue Words appearing as they are written
- Cost, Latency & Caching Making it affordable at player scale