Server facts
MCP for Unity
Project
- Author
- justinpbarnett
- Repository
- github.com/justinpbarnett/unity-mcp
- License
- MIT
- Category
- Games & 3D
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
openupm add com.coplaydev.unity-mcpThis 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.
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.
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.
{
"mcpServers": {
"unity-mcp": {
"command": "openupm",
"args": [
"add",
"com.coplaydev.unity-mcp"
],
"env": {}
}
}
}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.
{
"mcpServers": {
"unity-mcp": {
"command": "openupm",
"args": [
"add",
"com.coplaydev.unity-mcp"
],
"env": {}
}
}
}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.
{
"servers": {
"unity-mcp": {
"type": "stdio",
"command": "openupm",
"args": [
"add",
"com.coplaydev.unity-mcp"
],
"env": {}
}
}
}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.
{
"mcpServers": {
"unity-mcp": {
"command": "openupm",
"args": [
"add",
"com.coplaydev.unity-mcp"
],
"env": {}
}
}
}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.
{
"mcpServers": {
"unity-mcp": {
"type": "stdio",
"command": "openupm",
"args": [
"add",
"com.coplaydev.unity-mcp"
],
"env": {}
}
}
}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
Independent listing, not an affiliation or security review. Grant the least access needed and verify the upstream instructions before running code.