MCP server for interfacing with Godot game engine. Provides tools for launching the editor, running projects, and capturing debug output.
Godot MCP has 21 tools with basic naming and descriptions, but significant quality gaps. All tools have descriptions (10-50 chars, mostly under the 50-200 char LLM-optimized range), and input schemas are present with parameter types. However, parameter descriptions are minimal or missing context. No output schemas are documented. Error handling is generic. Tool names follow verb_noun convention but lack clarity on distinctions (e.g., create_node vs add_script_to_node both modify scenes). No tool annotations (readOnlyHint, destructiveHint). Schemas lack enums for constrained inputs (e.g., 'platform' in export_project accepts free-form strings instead of enum). Path validation is mentioned in code but not reflected in parameter constraints. Overall, this is a functional but under-documented toolkit typical of early-stage community servers.
Add a script to a node in a Godot scene
Create a new node in a Godot scene
Create a new scene in a Godot project
Create a new GDScript file in a Godot project
Delete a node from a Godot scene
Delete a scene file from a Godot project
Delete a GDScript file from a Godot project
Export a Godot project to a specified platform
No output schemas documented. Tools return unstructured responses; LLMs cannot predict fields for downstream chaining. E.g., get_scene_tree, get_project_settings, list_project_files lack documented return structures.
Parameter descriptions are minimal (10-30 chars) and lack actionable constraints. E.g., 'propertyValue' in set_node_property is described as 'Value to set for the property', no type hint, format, or range. LLMs cannot validate inputs.
No enum constraints for constrained inputs. 'platform' in export_project accepts free-form strings instead of enum ['Windows Desktop', 'Linux/X11', 'macOS', 'HTML5']. Invites hallucinated platform names.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 49 | 2026-07-28+ | v2 |
Get the debug output from the currently running Godot process
Get the version of the installed Godot engine
Get properties of a node in a Godot scene
Get the project settings from a Godot project
Get the scene tree structure of a Godot scene
Launch the Godot editor with an optional project path
List files in a Godot project directory
Read the content of a GDScript file
Run a Godot project with optional scene and debug settings
Set a property of a node in a Godot scene
Set a project setting in a Godot project
Stop the currently running Godot process
Update the content of a GDScript file
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Destructive tools (delete_node, delete_script, delete_scene) lack explicit marking. LLMs cannot distinguish safe reads from irreversible writes.
Error handling is generic. Code shows createErrorResponse() but no evidence of actionable recovery guidance. E.g., if a path is invalid, error should suggest 'Use list_project_files() to find valid paths' rather than bare 'Invalid path'.