Unity Editor MCP Server

Unity Editor MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Unity Editor MCP (Model Context Protocol) enables AI assistants like Claude and Cursor to interact directly with the Unity Editor, allowing for AI-assisted game development and automation.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What the assistant can call

Once Unity Editor MCP is connected, these are the calls the assistant has available:

• Prerequisites — The Prerequisites tool exposed by this server
• Installation — The Installation tool exposed by this server

Configuration and credentials

You will need 4 environment variables: UNITY_MCP_INSTANCE_ID, UNITY_PROJECT_PATH, UNITY_MCP_PROJECT_PATH, UNITY_MCP_WORKSPACE_ID. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• ✅ Unity 2020.3 LTS or newer - ✅ Node.js 18.0.0 or newer - ✅ Claude Desktop or Cursor

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the unity editor mcp mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Unity Editor MCP's toolset — Prerequisites, Installation — is a fair guide to whether it matches your workflow. It is maintained by ozankasikci; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Unity Editor MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.