Claude builds your Godot scene, then playtests it

What it does Godot MCP Pro is a Model Context Protocol server that plugs AI assistants — Claude Code, Cursor, VS Code Copilot, Cline and friends — into a live Godot 4 editor. A Node.js middle layer bridges MCP over stdio to a Godot plugin over a local WebSocket, so changes go through the real editor API and UndoRedo system instead of blind file writes. The full build exposes 172 tools (the repo description says 162 — the count drifts depending on where you read) spanning scenes, nodes, scripts, shaders, animations, tilemaps, themes, and project settings, with physics, particles, audio, and navigation also listed in the repo’s blurb. It reaches past the editor too: the assistant can run the game, simulate keyboard and mouse input, capture screenshots, and inspect the running game’s scene tree.

The interesting bit The runtime tools are really an AI-driven QA harness — record and replay input, watch a property’s value over time, click a button by its text, wait for a node to appear — so the assistant can verify its own changes by playing the game. The packaging is just as canny: MCP clients choke on big tool lists (Windsurf caps at 100; the project’s own table warns OpenCode models degrade past ~40), so the server ships in four sizes — 172, 100, 81, or 35 tools — plus a CLI mode where the model discovers commands lazily through help text instead of loading every tool definition upfront. That last trick is a smart answer to a real MCP growing pain.

Key highlights

• Editor-native edits — scene and node CRUD with undo support, signal wiring, script creation and syntax validation, shader editing, animation tracks, tilemap painting, theme overrides, plus an escape hatch that runs arbitrary GDScript inside the editor.
• Runtime testing — live game scene tree, property monitoring over time, multi-frame capture, input record/replay, wait_for_node, click_button_by_text, and move_to to walk a character to a target.
• Real-time link — local WebSocket to the editor, no file polling; JSON-RPC 2.0 with error codes and suggestions.
• Sized for every client — four tool profiles (Full, 3D, Lite, Minimal) plus a terminal CLI for non-MCP clients and small-context local models.
• Wide client support — Claude Code, Cursor, VS Code Copilot, Cline, Roo Code, Windsurf, JetBrains Junie, Gemini CLI, OpenAI Codex CLI, OpenCode.

Caveats

• The repo is half a product. Only the free Godot addon (GDScript) lives on GitHub; the Node.js server that actually connects your AI client ships exclusively in the paid package — $15 one-time, lifetime updates, via itch.io or Buy Me a Coffee.
• The paid server arrives as pre-built JavaScript, so there’s no server source to audit before pointing it at your editor.
• It requires a running Godot editor with the plugin enabled — an interactive pair-programming tool, not a headless CI agent.

Verdict If you build in Godot 4 and live in Claude Code or Cursor, this is one of the more complete editor bridges around, and the playtesting tools are the part worth paying for. If you want open source all the way down, or headless automation, the paywall and the editor tether will stop you early.