Godot MCP Enhanced
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Set to "true" to enable detailed server-side debug logging | |
| GODOT_PATH | No | Path to the Godot executable (overrides automatic detection) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| launch_editorC | Launch Godot editor for a specific project |
| run_projectC | Run the Godot project and capture output |
| get_debug_outputB | Get the current debug output and errors |
| stop_projectA | Stop the currently running Godot project |
| get_godot_versionA | Get the installed Godot version |
| list_projectsA | List Godot projects in a directory |
| get_project_infoB | Retrieve metadata about a Godot project |
| create_sceneB | Create a new Godot scene file |
| add_nodeB | Add a node to an existing scene |
| load_spriteC | Load a sprite into a Sprite2D node |
| save_sceneC | Save changes to a scene file |
| create_scriptC | Create a new GDScript file |
| attach_scriptB | Attach a script to a node in a scene |
| get_uidB | Get the UID for a specific file in a Godot project (for Godot 4.4+) |
| update_project_uidsB | Update UID references in a Godot project by resaving resources (for Godot 4.4+) |
| export_mesh_libraryB | Export a scene as a MeshLibrary resource |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Most tools target a distinct resource and action, such as creating scenes, attaching scripts, or managing UIDs. A few edge cases like launch_editor vs. run_project and add_node vs. load_sprite could cause some hesitation, but the descriptions sufficiently clarify the boundaries.
All tool names follow a consistent snake_case verb_noun pattern: launch_editor, run_project, get_debug_output, create_scene, attach_script, etc. This makes the toolset highly predictable and easy for an agent to reason about.
With 16 tools, the set is slightly above the ideal 3-15 range, but each tool covers a distinct part of Godot workflows: project control, scene editing, scripting, UID maintenance, and export. It feels reasonably scoped for a domain-specific MCP server.
The set covers many core operations: creating scenes/scripts, adding and saving, attaching scripts, running projects, and managing UIDs. However, it lacks deletion, scene inspection/reading node trees, and script editing/updating, which are notable gaps for a complete Godot development workflow.