Godot Mcp Pro

The interesting thing about Godot MCP Pro isn't the tool count — it's the architecture. The plugin starts a WebSocket server inside the Godot editor, the Node.js MCP server bridges to it over stdio, and the vendor explicitly contrasts this with file polling and CLI subprocess spawning. That design choice is what makes the play-testing category possible at all: you can call play_scene, simulate_key, capture_frames, assert_node_state, and run_stress_test against a game that is actually running, not a static representation of one. The published tutorial for that flow is the "walk right for 2 seconds, jump, verify the player reached the platform" example, and it holds together. Strength one is breadth within a single engine rather than across many. 187 tools across 26 categories, with the vendor claiming 16 categories no competitor covers. You get project metadata and autoload management, scene creation and instancing, node manipulation with type parsing, GDScript editing with syntax validation, AnimationTree state machines with transitions and blend parameters, physics bodies and raycasts and collision layers, GPUParticles2D/3D presets (fire, smoke, rain, snow, sparks), signal flow analysis, and TileMap editing including legacy multi-layer scenes. Strength two is safety, which is unusual for this category. All mutating operations support undo/redo, and the v1.14.0 overhaul (May 18, 2026) routed save_scene through the editor API so writes no longer trigger the "modified outside the editor" dialog that could wipe in-memory work. Open scene tabs return a structured conflict instead of being silently overwritten, and execute_editor_script blocks unsafe direct file-write APIs unless explicitly allowed. v1.17.1's patch export never destroys an existing pack. For an AI agent issuing dozens of mutations a minute, that matters more than another ten tools. Strength three is the recent engineering velocity, and it cuts both ways. In the five months between v1.12.0 and v1.17.1, the project shipped Android remote deploy, editor selection tools, Godot 4.6/4.7 support, and a parallel-session port-race fix (sessions now bind-retry across ports 6505–6509 rather than silently failing). Weaknesses. First, the vendor's own numbers disagree: the changelog page header reads "Now 175 tools" on the same site whose homepage and pricing pages say 187 and whose own v1.17.1 entry records the jump from 178 to 187. The 175 in that header is the v1.15.0 figure that was never updated, but a buyer reading the changelog sees two different products. Second, you cannot try before you buy. Third, the setup assumes a real toolchain — a TypeScript build via npm and an MCP client config file. Windows, macOS, and Linux are all covered, but this is not a double-click installer, and the changelog documents bugs like a project name containing a period (#39) that suggest an early-stage codebase still finding edges. Fourth, the editor-closed case is unaddressed in everything published: