godot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Set to "true" for detailed server-side logging | |
| GODOT_PATH | No | Path to the Godot executable (overrides auto-detection) | |
| GODOT_MCP_ALLOWED_DIRS | No | Optional. Restrict run_project to projects under these roots (separated by ;, ,, or :). When unset, any project path is allowed. |
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 |
|---|---|
| godot_catalogA | Browse the Godot MCP operation tree before choosing a domain tool |
| core_manageC | Godot core operations. Call godot_catalog for the operation tree. |
| project_manageB | Godot project operations. Call godot_catalog for the operation tree. |
| scene_manageD | Godot scene operations. Call godot_catalog for the operation tree. |
| filesystem_manageC | Godot filesystem operations. Call godot_catalog for the operation tree. |
| validation_manageC | Godot validation operations. Call godot_catalog for the operation tree. |
| runtime_manageC | Godot runtime operations. Call godot_catalog for the operation tree. |
| node_manageD | Godot node operations. Call godot_catalog for the operation tree. |
| input_manageD | Godot input operations. Call godot_catalog for the operation tree. |
| signal_manageD | Godot signal operations. Call godot_catalog for the operation tree. |
| animation_manageC | Godot animation operations. Call godot_catalog for the operation tree. |
| camera_manageC | Godot camera operations. Call godot_catalog for the operation tree. |
| physics_manageD | Godot physics operations. Call godot_catalog for the operation tree. |
| render_2d_manageD | Godot render_2d operations. Call godot_catalog for the operation tree. |
| render_3d_manageD | Godot render_3d operations. Call godot_catalog for the operation tree. |
| audio_manageC | Godot audio operations. Call godot_catalog for the operation tree. |
| ui_manageC | Godot ui operations. Call godot_catalog for the operation tree. |
| network_manageC | Godot network operations. Call godot_catalog for the operation tree. |
| system_manageC | Godot system operations. Call godot_catalog for the operation tree. |
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 19 tools
Each tool has a distinct domain prefix (e.g., animation, audio, camera) making them clearly distinguishable by name, despite identical descriptions.
All operation tools follow a consistent <domain>_manage pattern, except for godot_catalog which breaks the pattern.
19 tools is a reasonable number, but many of them are redundant wrappers that delegate to a single catalog tool, making the surface feel inflated.
The tool set lacks direct operations; all manage tools merely redirect to godot_catalog, which is a single point of entry, leaving the actual functionality hidden and incomplete for direct agent use.