1. Home
  2. Godot MCP
  3. Godot MCP for VS Code: Setup & Config

Data as of

Godot MCP for VS Code: Setup & Config

Godot MCP lets VS Code open the editor, run projects, and inspect debug output.

What you can do with Godot in VS Code

Pick it for Godot execution feedback and scene operations within the same MCP workflow.

  • Run a game project and inspect errors from an AI assistant.
  • Load sprites or export MeshLibrary resources for GridMap.

Before you start: Godot in VS Code

  • Godot Engine installed locally
  • Node.js 18.0.0 or newer and npm
  • An MCP-compatible agent
  • Godot 4.4 or newer for UID operations

GODOT_PATH overrides automatic executable detection and can be omitted when discovery works. DEBUG=true enables detailed server logging. Ensure project paths contain project.godot.

Godot VS Code configuration

  1. Choose VS Code configuration scope

    For Godot MCP, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

  2. Add Godot MCP to VS Code

    Use the godot-mcp entry below in servers. Keep Godot MCP's documented stdio connection fields and your other VS Code entries.

  3. Check Godot MCP in VS Code

    Godot MCP: Start in VS Code’s MCP controls; inspect output and trust prompts.

Config file · Workspace: .vscode/mcp.json

JSON
{
  "servers": {
    "godot-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "@coding-solo/godot-mcp"
      ],
      "env": {
        "GODOT_PATH": "<Path to the Godot executable; optional discovery override>"
      }
    }
  }
}

Godot tools available to VS Code

Godot's stored tool list documents 14 tools; compare it with VS Code's connected tool list, because the stored list is not a live check.

launch_editor

Look for launch_editor among VS Code's agent-mode tools after starting Godot through the MCP controls.

Open the Godot editor for a selected project.

run_project

Look for run_project among VS Code's agent-mode tools after starting Godot through the MCP controls.

Execute a project and collect its output.

get_debug_output

Look for get_debug_output among VS Code's agent-mode tools after starting Godot through the MCP controls.

Read the current runtime logs and error output.

stop_project

Look for stop_project among VS Code's agent-mode tools after starting Godot through the MCP controls.

End the project execution currently controlled by the server.

get_godot_version

Look for get_godot_version among VS Code's agent-mode tools after starting Godot through the MCP controls.

list_projects

Look for list_projects among VS Code's agent-mode tools after starting Godot through the MCP controls.

get_project_info

Look for get_project_info among VS Code's agent-mode tools after starting Godot through the MCP controls.

create_scene

Look for create_scene among VS Code's agent-mode tools after starting Godot through the MCP controls.

Generate a Godot scene file.

add_node

Look for add_node among VS Code's agent-mode tools after starting Godot through the MCP controls.

Insert a node into an existing scene.

load_sprite

Look for load_sprite among VS Code's agent-mode tools after starting Godot through the MCP controls.

Assign sprite content to a Sprite2D node.

export_mesh_library

Look for export_mesh_library among VS Code's agent-mode tools after starting Godot through the MCP controls.

save_scene

Look for save_scene among VS Code's agent-mode tools after starting Godot through the MCP controls.

get_uid

Look for get_uid among VS Code's agent-mode tools after starting Godot through the MCP controls.

update_project_uids

Look for update_project_uids among VS Code's agent-mode tools after starting Godot through the MCP controls.

Godot: full stored tool descriptions

Troubleshooting Godot in VS Code

  • Make npx @coding-solo/godot-mcp (Node.js/npm) available in the workspace, container, or remote environment hosting Godot MCP. Start through VS Code's MCP controls; inspect output and trust prompts.
  • For Godot MCP, keep GODOT_PATH out of version control; VS Code documents input variables and secret handling.
  • Godot MCP uses stdio here: VS Code must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: Requires an installed Godot engine and Node.js 18 or newer.
  • Known limitation: UID operations require Godot 4.4 or newer.
  • Known limitation: Project paths must point to directories containing project.godot.
  • General VS Code troubleshooting lives in the /clients/vscode guide.

Godot MCP — details. VS Code guide

Frequently asked questions

For Godot MCP, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's godot-mcp example uses stdio.

Godot MCP's VS Code configuration invokes npx @coding-solo/godot-mcp (Node.js/npm).

VS Code's Godot MCP example references GODOT_PATH. Check these names if startup or authentication fails; the example alone does not distinguish required from optional values.

Godot MCP's stored list contains 14 tools, including launch_editor, run_project, get_debug_output. Compare those names with VS Code's connected tool list; the stored list is not a live check.

Yes. The documented tools start and stop projects and retrieve debug output and error messages.

Set GODOT_PATH to the Godot executable, overriding automatic detection.