Server profile

MCP for Unity

MCP for Unity links AI assistants to the Unity Editor for scene work, asset management, script editing, testing, and builds. It targets game developers who want to direct editor workflows through natural language.

Server facts

MCP for Unity

Tech

Runtime / language
c#C#
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
15,026
Last commit
Data as of

Tags

  • Csharp
  • Editor Automation
  • Game Development
  • Scene Management
  • Unity

Overview

MCP for Unity brings editor operations into an AI assistant's workflow. Through an MCP connection, a compatible client can direct scene creation, GameObject manipulation, asset management, and C# script changes. The README also lists testing, profiling, and building among its capabilities. This makes the project relevant to game development tasks that cross between code and editor state rather than stopping at text generation. It describes 47 focused tool entrypoints and links to a separate catalog, but the supplied README does not enumerate their individual names. Supported clients include desktop assistants, coding agents, editors, and local language model setups.

The quickstart requires Unity versions from 2021.3 LTS through 6.x and Python 3.10 or later through uv. Installation normally begins in Unity's Package Manager using the repository's package URL. A menu action then configures detected clients, after which the developer can issue natural-language requests. An OpenUPM installation command is also supplied. Advanced documentation links cover multiple Unity instances, tool groups, script validation, authenticated remote hosting, and migration details for asset generation. The project is MIT-licensed and explicitly identifies itself as independent from Unity Technologies. It is a practical fit when an assistant needs to operate within an existing Unity project, but initial setup still involves both the editor package and its Python-side requirements.

Install & configure

Requirements

  • Unity 2021.3 LTS through 6.x
  • Python 3.10 or later via uv
  • An MCP-compatible client
  • OpenUPM when using this installation command
Documented launch / install command
openupm add com.coplaydev.unity-mcp

This command installs the Unity package, not a standalone MCP launch process. Alternatively, add https://github.com/CoplayDev/unity-mcp.git?path=/MCPForUnity#main in Package Manager, then use Window > MCP for Unity > Configure All Detected Clients. Individual tool names and a standalone server launch command are not stated in the README.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

Use Settings → Developer → Edit Config when available. Do not assume a Linux configuration path; check the client documentation for your platform. Remote servers use the app’s connector flow when supported, not the local stdio file shown here. Merge this example with existing settings; do not overwrite unrelated servers.

Claude Desktop configuration
{
  "mcpServers": {
    "unity-mcp": {
      "command": "openupm",
      "args": [
        "add",
        "com.coplaydev.unity-mcp"
      ],
      "env": {}
    }
  }
}

Read the Claude Desktop setup guide

Config file · Project: .cursor/mcp.json

User: ~/.cursor/mcp.json

The project path is relative to the workspace root. The tilde denotes your user home directory. Use Cursor’s MCP settings to confirm which configuration and scope your installed version is reading. Merge this example with existing settings; do not overwrite unrelated servers.

Cursor configuration
{
  "mcpServers": {
    "unity-mcp": {
      "command": "openupm",
      "args": [
        "add",
        "com.coplaydev.unity-mcp"
      ],
      "env": {}
    }
  }
}

Read the Cursor setup guide

Config file · Workspace: .vscode/mcp.json

For user scope, use the “MCP: Open User Configuration” command if available. Do not guess a user configuration path across operating systems, profiles, containers, or remote workspaces; check the client documentation. Merge this example with existing settings; do not overwrite unrelated servers.

VS Code configuration
{
  "servers": {
    "unity-mcp": {
      "type": "stdio",
      "command": "openupm",
      "args": [
        "add",
        "com.coplaydev.unity-mcp"
      ],
      "env": {}
    }
  }
}

Read the VS Code setup guide

Config file · macOS/Linux: ~/.codeium/windsurf/mcp_config.json

Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json

Open the MCP configuration through Windsurf’s settings when possible to confirm the active file. Paths can differ in managed or future releases; check the client documentation if this location is not present. Merge this example with existing settings; do not overwrite unrelated servers.

Windsurf configuration
{
  "mcpServers": {
    "unity-mcp": {
      "command": "openupm",
      "args": [
        "add",
        "com.coplaydev.unity-mcp"
      ],
      "env": {}
    }
  }
}

Read the Windsurf setup guide

Config file · Project scope: .mcp.json at the repository root

The project file uses mcpServers. For user scope, use claude mcp add --scope user rather than assuming .mcp.json in your home directory is the user configuration. Check the client documentation for managed settings and storage details. Merge this example with existing settings; do not overwrite unrelated servers.

Claude Code configuration
{
  "mcpServers": {
    "unity-mcp": {
      "type": "stdio",
      "command": "openupm",
      "args": [
        "add",
        "com.coplaydev.unity-mcp"
      ],
      "env": {}
    }
  }
}

Read the Claude Code setup guide

Examples are translated from the published configuration. Supply your own credentials and verify requirements in the upstream README. Remote connectors are shown only where a supported configuration format is known.

Tools

No individual tool names were confirmed in the source material. Check the repository for its current tool list.

Names, permissions, and defaults can change. Check the current upstream documentation before granting access.

Use cases

  • Create scenes and GameObjects from natural-language instructions.
  • Edit C# scripts while working with Unity Editor state.
  • Automate asset management and game development tasks.
  • Run tests, profile a project, and initiate builds.

Strengths

  • Covers code, scene, asset, test, and build workflows.
  • Provides an editor action to configure detected clients.
  • Supports a broad range of MCP clients under an MIT license.

Limitations

  • Requires a supported Unity installation and Python through uv.
  • Individual tool identifiers are not stated in the supplied README.
  • Advanced routing and remote authentication require separate documentation.

Frequently asked questions

It lists Unity 2021.3 LTS through 6.x, together with Python 3.10 or later through uv.

No. The README describes compatibility with any MCP client and names Claude, Codex, VS Code, local LLMs, and others.

Yes. The README includes scene and asset operations, testing, profiling, and builds.

No. The project describes itself as an independent, open-source Unity Editor tool licensed under MIT.

Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.

Related MCP servers

MCP Toolbox for Databases

Databases

MCP Toolbox for Databases connects agents and IDEs to enterprise data through prebuilt tools or custom query definitions. It combines database access with connection pooling, authentication integration, and observability.

IDA Pro MCP

Security & Reverse Engineering

IDA Pro MCP connects AI clients to IDA for binary inspection, decompilation, database changes, and optional debugging. Its recommended headless path manages persistent analysis workers and explicit database sessions.

BlenderMCP

Games & 3D

BlenderMCP links AI assistants to Blender for scene inspection, object and material changes, and Python execution. Optional asset integrations add Poly Haven downloads, Sketchfab models, and generated 3D assets.

Godot MCP

Games & 3D

Godot MCP lets AI agents open the editor, run projects, and inspect debug output. It also supports scene and node operations, sprite loading, mesh-library export, and UID maintenance for supported Godot versions.

Unreal MCP

Games & 3D

Unreal MCP links assistant requests to Unreal Editor through a Python server and C++ plugin. It covers scene objects, Blueprint construction, and viewport adjustments, but the project explicitly remains experimental.

MCP Unity Editor

Games & 3D

Connect AI assistants to Unity Editor through a Unity package and Node.js MCP bridge. Manage scenes, GameObjects, materials, packages, tests, and console logs, with resources and guided workflow prompts.

Unreal Engine Generative AI Support Plugin

Games & 3D

This Unreal Engine plugin combines generative AI API integrations with MCP-based editor control. Assistants can manipulate scene objects, work with some Blueprint features, and run editor scripts, although MCP development is inactive.

Minecraft MCP Server

Games & 3D

Minecraft MCP Server lets an AI assistant control a Minecraft character through Mineflayer. Tools cover movement, blocks, inventory, smelting, entities, and chat, with a documented local LAN-world setup.