Godot MCP for Cursor: Setup & Config

What you can do with Godot in Cursor

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

• Load sprites or export MeshLibrary resources for GridMap.
• Maintain project resource UID references on Godot 4.4 or newer.

Before you start: Godot in Cursor

• 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 Cursor configuration

1. Choose Cursor configuration scope

   For Godot MCP, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.

2. Add Godot MCP to Cursor

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

3. Check Godot MCP in Cursor

   Godot MCP: Enable in Cursor’s MCP settings; inspect tools.

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

Godot tools available to Cursor

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

launch_editor

Find launch_editor under Godot in Cursor's MCP settings; inspect its arguments when the agent requests a call.

run_project

Find run_project under Godot in Cursor's MCP settings; inspect its arguments when the agent requests a call.

get_debug_output

Find get_debug_output under Godot in Cursor's MCP settings; inspect its arguments when the agent requests a call.

stop_project

Find stop_project under Godot in Cursor's MCP settings; inspect its arguments when the agent requests a call.

get_godot_version

Find get_godot_version under Godot in Cursor's MCP settings; inspect its arguments when the agent requests a call.

list_projects

Find list_projects under Godot in Cursor's MCP settings; inspect its arguments when the agent requests a call.

get_project_info

Find get_project_info under Godot in Cursor's MCP settings; inspect its arguments when the agent requests a call.

create_scene

Find create_scene under Godot in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Generate a Godot scene file.

add_node

Find add_node under Godot in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Insert a node into an existing scene.

load_sprite

Find load_sprite under Godot in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Assign sprite content to a Sprite2D node.

export_mesh_library

Find export_mesh_library under Godot in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Export scene content as a MeshLibrary resource.

save_scene

Find save_scene under Godot in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Persist scene changes to a file.

get_uid

Find get_uid under Godot in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Read a file’s resource UID on Godot 4.4 or newer.

update_project_uids

Find update_project_uids under Godot in Cursor's MCP settings; inspect its arguments when the agent requests a call.

Resave resources to refresh project UID references on Godot 4.4 or newer.

Godot: full stored tool descriptions

Troubleshooting Godot in Cursor

• Cursor must find npx @coding-solo/godot-mcp (Node.js/npm) for Godot MCP. Enable the project/user entry in MCP settings and inspect its tools.
• Review GODOT_PATH for Godot MCP before sharing project .cursor/mcp.json; project scope travels with the repository.
• Godot MCP uses stdio here: Cursor 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 Cursor troubleshooting lives in the /clients/cursor guide.

Frequently asked questions