MCP server for interfacing with Godot game engine. Provides tools for launching the editor, running projects, and capturing debug output.
15 tools with basic schemas and descriptions, but significant quality gaps. All tools have descriptions (10-50 chars, mostly generic), and input schemas are present with parameter types. However, descriptions lack actionable context, they state WHAT but rarely WHEN or WHY. No output schemas documented. Parameter descriptions are minimal (e.g., 'Path to the Godot project' repeated 12 times). No enums for constrained inputs (e.g., rootNodeType, nodeType accept free-form strings). Error handling is minimal, no recovery guidance or categorization. No tool annotations (readOnlyHint, destructiveHint). Naming is verb-first and clear (launch_, run_, create_, delete_), which is good. However, many tools operate on overlapping resources (scene, node, file operations) without clear composition guidance. Missing: output schema documentation, parameter constraints, error recovery paths, and LLM-optimized descriptions.
Add a node to an existing scene in a Godot project
Attach a GDScript script to a node in a Godot scene
Create a new directory in a Godot project
Create a new GDScript file in a Godot project
Create a new scene in a Godot project with a root node
Delete a directory from a Godot project
Delete a file from a Godot project
Retrieve captured debug output from the running Godot process
No output schemas documented. LLMs cannot infer what fields to expect from tool responses, forcing them to guess at downstream tool inputs and risking broken chains.
Parameter descriptions are generic and repetitive (e.g., 'Path to the Godot project' appears 12 times). Descriptions lack actionable context, no guidance on format, constraints, or when to use each tool variant.
No enums for constrained inputs. 'rootNodeType' and 'nodeType' accept free-form strings (e.g., 'Node2D', 'Node3D', 'Control') but are not declared as enums. LLMs will hallucinate invalid node types.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 44 | 2026-07-28+ | v2 |
Get the directory structure of a Godot project
Launch the Godot editor with an optional project path
Read the contents of a file in a Godot project
Run a Godot project with optional debug mode and scene selection
Set a property on a node in a Godot scene
Stop the currently running Godot process
Write content to a file in a Godot project
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Agents cannot distinguish safe reads from destructive writes without parsing descriptions. delete_file and delete_directory should be marked destructive.
Error handling is minimal. No recovery guidance, error categorization, or actionable messages. Errors like 'file not found' or 'invalid node path' do not suggest next steps or alternatives.