How do I link Claude Code to Unity?

Through an MCP (Model Context Protocol) server that runs inside the Unity Editor. As of October 2026 there are three main options: Unity's official Unity MCP, which ships in the com.unity.ai.assistant package for Unity 6 and connects through a relay binary in ~/.unity/relay/; MCP for Unity by CoplayDev (free, MIT, Unity 2021.3 LTS to 6.x, Python 3.10+ via uv); and Unity-MCP by IvanMurzak (Apache-2.0, installed with the unity-mcp-cli npm tool). Install one in your project, then register it with Claude Code using claude mcp add or the server's auto-configure button.

What's the best way to code a Unity game with Claude?

Run Claude Code in your project folder for C# scripts and connect it to the Editor through an MCP server so it can inspect scenes, create GameObjects, read the console and run tests. Keep the project in git and commit before every agent session, ask for one system at a time, and have Claude run Unity's tests or check the console after each change rather than trusting that code compiles.

Is Unity MCP still in beta or production-ready?

Unity's official MCP server arrived with the Unity AI open beta (Unity blog, May 11, 2026), and the package documentation is still versioned as pre-release (Assistant 2.7.0-pre.3). Treat it as beta. The community MCP for Unity is more mature as software (v10.0.0 on June 30, 2026, about 14,700 GitHub stars), but any tool that lets an agent edit scenes and assets should be used with version control.

Which Unity MCP server should I use?

Use Unity's official server if you are on Unity 6 and already use Unity AI. Use CoplayDev's MCP for Unity if you are on an older LTS (2021.3 or later), want a free MIT tool with 48 tool entrypoints and a large community, or use several AI clients. Use IvanMurzak's Unity-MCP if you want its CLI-driven setup and its runtime and testing focus.

Quick Answer

How to Link Claude Code to Unity: 3 Unity MCP Options

Published: October 6, 2026

The short answer

Claude Code talks to Unity through an MCP server running in the Unity Editor. Install one of three servers in your project, register it with Claude Code, and Claude can read your scene hierarchy and console, create and modify GameObjects, edit C# scripts and trigger editor actions instead of you copy-pasting errors. On Unity 6 with Unity AI, use Unity’s official server; otherwise MCP for Unity by CoplayDev is the default.

The three options

	Unity MCP (official)	MCP for Unity (CoplayDev)	Unity-MCP (IvanMurzak)
Ships in	`com.unity.ai.assistant` package	Unity package + Python server	Unity package + `unity-mcp-cli` (npm)
Unity versions	Unity 6 (6000.0) or later	2021.3 LTS → 6.x	See repo
Licence / cost	Part of Unity AI (open beta)	MIT, free	Apache-2.0, free
Status (Oct 2026)	Beta; docs at 2.7.0-pre.3	v10.0.0 (June 30, 2026), ~14,700 stars, active	~4,400 stars, active
Clients	Claude Code, Cursor, Windsurf, Claude Desktop, VS Code Copilot	Any MCP client (Claude, Codex, Cursor, VS Code, Gemini CLI…)	Claude Code, Codex, Cursor, Cline and others
Pick when	You’re on Unity 6 and want Unity’s supported path	You want the most-used free option or an older LTS	You want CLI setup and its skills/test loop

Option 1: Unity’s official MCP server

Install the AI Assistant package (com.unity.ai.assistant) in a Unity 6 project.
Open Edit → Project Settings → AI → Unity MCP Server and check that Unity Bridge shows Running. The bridge starts with the editor and installs a relay binary to ~/.unity/relay/.
Under Integrations, select Claude Code and Configure — or add the relay yourself:

claude mcp add unity-mcp -- ~/.unity/relay/relay_mac_arm64.app/Contents/MacOS/relay_mac_arm64 --mcp

On Windows the relay is %USERPROFILE%\.unity\relay\relay_win.exe, on Linux ~/.unity/relay/relay_linux. The --mcp flag is required; some clients don’t expand ~, so use the absolute path. With several editors open, add --project-path <path> to target one project.

Option 2: MCP for Unity (CoplayDev)

The most widely used community server. It needs Unity 2021.3 LTS or newer and Python 3.10+ through uv, and exposes 48 tool entrypoints for scenes, GameObjects, C# scripts, assets, tests, profiling and builds. Add the package from its GitHub URL in the Package Manager, open its window in the editor and use its client setup for Claude Code. It is MIT-licensed and maintained with sponsorship from Aura, an AI assistant for Unreal and Unity.

Option 3: Unity-MCP (IvanMurzak)

Installs through a CLI: npm install -g unity-mcp-cli, which can also install Unity, create a project and configure agents including Claude Code. It describes itself as a full AI develop-and-test loop with skills, MCP tools and a CLI, and is Apache-2.0.

A workflow that works

Commit first. Agents that edit scenes and prefabs can make changes that are tedious to undo by hand.
Give Claude a CLAUDE.md describing your folder layout, render pipeline, input system and coding conventions.
One system per session: “add a stamina system to the player controller and a UI bar,” not “build the game.”
Close the loop: ask Claude to read the console and run edit-mode tests after each change. The MCP connection is what lets it see compile errors itself.
Merging two games or projects: have Claude inventory both projects’ scripts, scenes and packages first, port one system at a time into a new branch, and resolve package-version conflicts before moving scenes.

The pick

Unity 6 + Unity AI: official Unity MCP.
Any other setup, or several AI clients: MCP for Unity (CoplayDev).
CLI-first or testing-heavy workflow: Unity-MCP (IvanMurzak).

Last verified: October 6, 2026. Star counts and versions from GitHub on that date.