Godot MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GODOT_PATH | No | Path to the Godot executable. If not set, the server will auto-detect. | |
| MCP_TRANSPORT | No | Transport protocol for MCP (default: stdio) |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| godot_versionD | – |
| launch_editorD | – |
| list_projectsD | – |
| create_projectD | – |
| run_projectD | – |
| stop_projectD | – |
| get_debug_outputD | – |
| get_scene_treeD | – |
| create_sceneD | – |
| add_nodeD | – |
| write_fileD | – |
| read_fileD | – |
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 12 tools
Each tool targets a distinct action (e.g., project management, scene editing, file I/O) with unique names, making confusion unlikely despite missing descriptions.
All tool names follow a consistent verb_noun snake_case pattern (e.g., list_projects, create_scene, write_file), ensuring predictability.
12 tools cover a broad range of Godot interactions (project, editor, scene, debug, file) without being excessive or trivial.
Core workflows are covered, but missing operations like remove_node or update project limit some lifecycle completeness.