Godot MCP Server

What is Godot MCP Server?

Godot MCP Server is a community-built godot mcp integration that lets AI assistants launch the Godot editor, run your project, read its debug output and edit scenes through the Model Context Protocol. It gives agents a direct feedback loop with a real Godot project.

The project is developed by Coding-Solo on GitHub under the MIT license and is published on npm as @coding-solo/godot-mcp. It is not an official Godot Engine product. It runs locally over stdio and talks to your installed Godot executable, so nothing leaves your machine except what your AI client sends to its model.

How to use Godot MCP Server?

Requirements from the README:

• Godot Engine installed on your system
• Node.js 18.0.0 or newer, with npm
• An AI client that supports MCP

No API key is needed. Two optional environment variables are supported:

Variable	Purpose
GODOT_PATH	Path to the Godot executable (overrides automatic detection)
DEBUG	Set to "true" for detailed server-side debug logging

Claude Code

claude mcp add godot -- npx @coding-solo/godot-mcp

With environment variables:

claude mcp add godot -e GODOT_PATH=/path/to/godot -e DEBUG=true -- npx @coding-solo/godot-mcp

Restart Claude Code and the Godot tools become available.

Cursor

In the UI, open Cursor Settings > Features > MCP, click + Add New MCP Server, and enter name godot, type command, command npx @coding-solo/godot-mcp. You may need to press refresh on the server card to load the tool list. For a per-project setup, create .cursor/mcp.json:

{
  "mcpServers": {
    "godot": {
      "command": "npx",
      "args": ["@coding-solo/godot-mcp"],
      "env": {
        "DEBUG": "true"
      }
    }
  }
}

Claude Desktop, Cline and other clients

Any MCP-compatible client, such as Claude Desktop or Cline, can use the generic configuration from the README:

{
  "mcpServers": {
    "godot": {
      "command": "npx",
      "args": ["@coding-solo/godot-mcp"],
      "env": {
        "GODOT_PATH": "/path/to/godot",
        "DEBUG": "true"
      }
    }
  }
}

For Cline, the README places this in cline_mcp_settings.json and shows an autoApprove list of tool names if you want to skip confirmation prompts.

Building from source

git clone https://github.com/Coding-Solo/godot-mcp.git
cd godot-mcp
npm install
npm run build

Then point your MCP client at build/index.js instead of using npx.

Key features of Godot MCP Server

• Launches the Godot editor for a specific project
• Runs projects in debug mode and captures console output and errors
• Starts and stops a running project programmatically
• Reports the installed Godot version and finds Godot projects in a directory
• Reads project structure and metadata
• Creates scenes, adds nodes with properties, loads sprites into Sprite2D nodes and saves scenes, including variants
• Exports 3D scenes as MeshLibrary resources for GridMap
• Manages UIDs for Godot 4.4+ projects

Under the hood, simple operations use Godot's built-in command-line interface, while complex ones such as creating scenes or adding nodes go through a single bundled GDScript file, godot_operations.gd, which receives the operation and parameters as JSON.

Godot MCP Server tools

The server exposes 14 tools in four groups:

• Editor and runtime control: launch_editor opens the editor for a project, run_project runs it and captures output, get_debug_output returns the current log and errors, and stop_project ends the run. Together these let an agent change code, run the game and read what went wrong.
• Project discovery: get_godot_version, list_projects and get_project_info tell the agent which engine version is installed and what a project contains.
• Scene editing: create_scene, add_node, load_sprite, save_scene and export_mesh_library build and modify .tscn scenes without opening the editor by hand.
• UID management (Godot 4.4+): get_uid returns the UID of a file and update_project_uids resaves resources to refresh UID references.

Use cases of Godot MCP Server

• Debug loop with an agent: "Run my project, read the debug output and fix the null reference error in player.gd."
• Scene scaffolding: "Create a new scene with a CharacterBody2D root, add a Sprite2D and load res://art/hero.png into it."
• Project inspection: "List the Godot projects in ~/games and tell me the structure of the platformer one."
• 3D level tooling: "Export the tiles scene as a MeshLibrary so I can use it in a GridMap."
• Godot 4.4 upgrades: "Update the UID references across this project after moving files."
• Quick smoke tests: run the game from Claude Code or Cursor after each edit and check the console for errors.

Godot MCP Server vs alternatives

Godot MCP Server is one of several community MCP servers for game engines. If you work in other engines, Unity MCP connects AI assistants to the Unity editor and Blender MCP does the same for Blender 3D scenes. Other independent Godot MCP projects also exist on GitHub with different tool sets, so compare their READMEs before choosing. The Coding-Solo server stands out for its simple npx install and its focus on running projects and capturing debug output.

Troubleshooting Godot MCP Server

• Godot not found: set GODOT_PATH to the full path of your Godot executable.
• Invalid project path: the path must point to a directory that contains a project.godot file.
• Connection issues: make sure the server is running, then restart your AI assistant.
• Build errors from source: run npm install so all dependencies are present.
• Cursor tools missing: confirm the server is listed and enabled under Settings > MCP. The README notes that MCP tools run only in Cursor's Agent chat mode.