// the find
youichi-uda/godot-mcp-pro
162 MCP tools for AI-powered Godot 4 development. Scene, animation, 3D, physics, particles, audio, shader, input simulation, runtime analysis, navigation, testing & more. $15 one-time.
A commercial Godot 4 plugin plus Node.js MCP server that exposes the editor and running game to AI assistants like Claude — reading/writing scenes, nodes, animations, shaders, physics, and simulating input, with 150-190 RPC-style tools depending on mode. It's aimed at developers who want an AI agent driving the Godot editor directly instead of just editing script files. The public repo only ships the free Godot-side addon; the actual MCP server is a paid download.
The tiered tool-loading (full/3d/lite/minimal) plus a CLI mode with progressive --help discovery is a genuinely useful answer to MCP clients that choke on 100+ tool schemas, not just a marketing bullet. Splitting 180+ command handlers into per-domain GDScript files (physics_commands.gd, shader_commands.gd, tilemap_commands.gd, etc.) is a sane way to keep a huge RPC surface maintainable instead of one giant router. Routing node/property mutations through Godot's UndoRedo system means AI-driven edits are Ctrl+Z-able, which most competing sockets/CLI tools in the comparison table don't bother with.
The interesting half of this project — the Node.js MCP server that actually implements the protocol and talks to the LLM — isn't in the repo at all; it's a closed-source zip behind a $15 paywall, so you can't audit how execute_editor_script or execute_game_script (arbitrary code execution in your editor/game process) are sandboxed or rate-limited. The tool count is inconsistent between the repo description (162) and the README (187), and the README spends more space on self-authored competitor comparison tables than on protocol or security documentation. Paying for a closed-source layer is an odd model in an ecosystem where every competing MCP server listed is free and inspectable, so the value proposition is 'more tools' rather than 'better or safer architecture.' No test suite is visible for the 24+ command files despite the product itself shipping a whole 'Testing & QA' tool category.