tugcantopaloglu/godot-mcp

git clone https://github.com/tugcantopaloglu/godot-mcp.git && cd godot-mcp && npm install && npm run build
Add to your MCP client: {"mcpServers":{"godot":{"command":"node","args":["/absolute/path/to/godot-mcp/build/index.js"],"env":{"GODOT_PATH":"/path/to/godot"}}}

Usage

• •For runtime game_* tools, copy build/scripts/mcp_interaction_server.gd into your Godot project and register it as an autoload named McpInteractionServer (listens on 127.0.0.1:9090 over TCP)
• •Ask the agent: "Run my Godot project and check for errors", "Eval this in my running game: return get_tree().current_scene.name", "Set the player's health to 100"
• •Headless scene ops need no running game: read_scene, modify_scene_node, attach_script, validate_script

Key features

• ✓157 tools: runtime GDScript eval (game_eval with await support, works when paused), runtime node inspection/manipulation, signals, animation/tweening, input simulation (keys, scroll, gamepad, touch)
• ✓Headless scene operations, project management, GDScript diagnostics (validate_script / validate_scripts), and .NET/C# project scaffolding
• ✓Networking: HTTP, WebSocket, ENet multiplayer, RPC; 3D rendering/geometry, 2D systems, advanced audio and animation
• ✓Robustness: reentrancy guard, full type conversion (Vector2/3, Color, Quaternion, Basis, packed arrays), smart property type detection
• ✓Fork of godot-mcp by Coding-Solo, extended from 20 to 157 tools

Best for

AI-assisted Godot game development — agent-driven project creation, scene building, runtime debugging, and automated play-testing.

Caveats

• ⚠Requires Godot 4.4+ (tested with Godot 4.7) and Node.js >= 18; optional .NET SDK 8.0+ for C# features
• ⚠Runtime tools require the mcp_interaction_server.gd autoload running over TCP port 9090
• ⚠GODOT_MCP_ALLOWED_DIRS can restrict run_project to allowed roots; DEBUG env enables logging