Data as of
MCP for Unity for VS Code: Setup & Config
MCP for Unity links VS Code to the Unity Editor for scene work, asset management, script editing, testing, and builds.
MCP for Unity VS Code configuration
Choose VS Code configuration scope
For MCP for Unity, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.
Add MCP for Unity to VS Code
Use the unity-mcp entry below in servers. Keep MCP for Unity's documented stdio connection fields and your other VS Code entries.
Check MCP for Unity in VS Code
MCP for Unity: Start in VS Code’s MCP controls; inspect output and trust prompts.
Config file · Workspace: .vscode/mcp.json
{
"servers": {
"unity-mcp": {
"type": "stdio",
"command": "openupm",
"args": [
"add",
"com.coplaydev.unity-mcp"
],
"env": {}
}
}
}MCP for Unity in VS Code: stdio checks
- MCP for Unity's openupm add command installs a Unity package. Follow the upstream editor setup before expecting a stdio connection in VS Code.
- Make openupm available in the workspace, container, or remote environment hosting MCP for Unity. Start through VS Code's MCP controls; inspect output and trust prompts.
MCP for Unity — details. VS Code guide
Frequently asked questions
For MCP for Unity, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.
VS Code's unity-mcp example uses stdio.
MCP for Unity's VS Code configuration invokes openupm. MCP for Unity's openupm add command installs a Unity package. Follow the upstream editor setup before expecting a stdio connection in VS Code.