MCP Unity
MCP server that connects an AI agent to the Unity Editor: scene, objects, packages and project resources
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Changes objects and components in a real Unity project
- Can install packages into the project
Install
Manual install
{
"mcpServers": {
"mcp-unity": {
"command": "node",
"args": ["ABSOLUTE/PATH/TO/mcp-unity/Server~/build/index.js"]
}
}
}Copy the absolute path from Tools > MCP Unity > Server Window.
This is third-party code. Review the repository files before installing.
What it does
MCP Unity gives an agent access to the Unity Editor over the Model Context Protocol. Through a set of tools the agent can work with scene objects, change components, install packages in the Package Manager, read project state and get step-by-step guidance for common tasks. The server runs on Node.js and a package is installed inside Unity via the Package Manager, after which a client such as Cursor, Claude Code, Codex or Windsurf connects over MCP.
Who it is for. For Unity game developers who want to drive the editor and project through an AI agent.
Good fit when
- You want an agent to change Unity scene objects and components
- You want to manage Unity packages through an assistant
- You want an agent to read Unity project state
Not a fit when
- The project is not on Unity
- You cannot keep the Unity Editor and a Node.js server running
Example request
List the project's installed packages and add an empty controller object to the sceneLimitations
It needs Unity 6 or newer, Node.js 18 or newer and an open editor. Setup is multi-step: the Unity Package Manager package, then the server and the client config with an absolute path. The agent changes a real project, so version control matters.
How to disable. Remove the server entry from your MCP config and remove the MCP Unity package from the Package Manager.
MCP
- Transport
- stdio
- Authentication
- not required
Security check
- Changes objects and components in a real Unity project
- Can install packages into the project
README in short
The README describes an MCP plugin that connects the Unity Editor to AI clients over the Model Context Protocol. Setup takes several steps: Node.js 18 or newer, the MCP Unity package in the Package Manager, running the server and configuring the client via a config file with an absolute path. It offers tools for objects and components, package installs, reading project resources and guidance for common tasks. MIT licensed.
FAQ
What is installed in Unity itself?
The MCP Unity package via the Package Manager; it opens the server window and the editor bridge.
Which clients are supported?
Cursor, Claude Code, Codex, Windsurf and other MCP-capable clients.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything