godot-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GODOT_PATH | No | Godot executable. | godot |
| GODOT_PROJECTS_DIR | No | Folder that holds every project. All writes stay inside it. | ~/godot-projects |
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 |
|---|---|
| create_projectB | Create a Godot 4 project with a scenes/ and scripts/ folder and a main scene (scenes/main.tscn, Node2D root). Creates the project under the projects directory. |
| create_sceneB | Create a new .tscn scene with a single root node. |
| add_nodeA | Add a node to an existing scene. Property values are Godot literal expressions, e.g. position: "Vector2(10, 20)", text: '"Hello"'. A script_path attaches a script to the node. |
| create_scriptA | Create a GDScript file. Without content, writes a template with the given extends type and an empty _ready(). |
| set_main_sceneC | Set the scene that runs when the game starts. |
| validate_projectA | Check every script for parse errors and run the project headless to catch scene and load errors. Returns ok: true only when Godot reports no errors. |
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 6 tools
Each tool targets a distinct object (project, scene, node, script) or a distinct action (set main scene, validate), so misselection is unlikely. The only mild overlap is between create_project (which auto-creates a main scene) and set_main_scene, but the descriptions make the boundary clear.
All six tools follow a consistent snake_case verb_noun pattern (create_project, create_scene, add_node, create_script, set_main_scene, validate_project). No mixed conventions or vague verbs.
Six tools is a well-scoped set for Godot project scaffolding: each tool covers a distinct lifecycle step (project, scene, node, script, main scene, validation). Nothing feels redundant or missing at the count level.
Creation is well covered, but the surface is write-only: there is no way to read/list existing scenes or scripts, remove nodes/scenes/scripts, or edit an existing script's content. An agent cannot inspect project state, which will cause dead ends in any non-trivial workflow.