MCP server for interfacing with Godot game engine. Provides tools for launching the editor, running projects, and capturing debug output.
Server has 10 tools with complete schemas and descriptions. Naming follows verb_noun pattern (launch_editor, run_project, get_godot_output). Descriptions are present (avg ~80 chars) but lack LLM-optimized guidance on WHEN to use each tool vs alternatives. Parameters have types and descriptions, but lack constraints (enums, ranges, patterns). No output schemas documented. Error handling exists but lacks recovery guidance. Missing tool annotations (readOnlyHint, destructiveHint). Composition is reasonable, tools are single-purpose, but some overlap (run_project vs run_scene, capture_screenshot vs capture_scene_screenshot) without clear differentiation.
Load a specific scene file, instance it in the viewport, and capture a screenshot
Capture a screenshot from a running Godot scene
Get the captured output from the last Godot process execution
Launch the Godot editor for a project
List files in a Godot project by type (scenes, scripts, resources)
Terminate the currently running Godot process
Run a Godot project and capture its output
No output schemas documented. LLMs cannot infer what fields to expect from tool responses, forcing them to guess at downstream field names and types.
Descriptions lack WHEN-to-use guidance. E.g., run_project vs run_scene both run Godot code but descriptions don't explain when to choose one over the other. LLMs waste reasoning cycles deciding between similar tools.
Numeric parameters (timeoutMs, waitFrames, maxFiles, maxOutputBytes) lack explicit min/max constraints in descriptions. LLMs can pass absurd values (negative timeouts, 1M files) that break execution.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 60 | 2026-07-28+ | v2 |
Run a specific scene in the Godot editor with optional timeout
Validate a single GDScript file for syntax errors and warnings
Validate multiple GDScript files in a project for syntax errors and warnings
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot determine which tools are safe to retry, which modify state, and which are read-only without parsing descriptions.
Error responses lack recovery guidance. When a tool fails (e.g., 'Project not found'), the response should suggest next steps (e.g., 'Try list_project_files() to see available projects'). Current error handling is silent.