Godot MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| QT_QPA_PLATFORM | No | The Qt platform abstraction plugin to use (e.g., 'xcb'). | |
| __GLX_VENDOR_LIBRARY_NAME | No | The name of the GLX vendor library (e.g., 'mesa'). |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| godot_run_testsA | Run GUT (Godot Unit Test) tests for a Godot project. Returns test results including pass/fail counts and any failures. |
| godot_check_errorsA | Check a Godot project for parse errors and syntax issues without running the game. |
| godot_importA | Import/reimport assets in a Godot project. Useful after adding new files. |
| godot_run_sceneA | Run a specific scene in the Godot project (non-headless, will open a window). |
| godot_exportC | Export a Godot project to a specific platform. |
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 5 tools
Each tool has a clearly distinct purpose with no overlap: checking errors, exporting projects, importing assets, running scenes, and running tests. The descriptions specify unique actions (e.g., parse errors vs. export vs. import), making it easy for an agent to select the correct tool without confusion.
All tool names follow a consistent 'godot_verb_noun' pattern (e.g., godot_check_errors, godot_export, godot_import), using snake_case throughout. This predictability enhances readability and reduces cognitive load for agents when scanning the toolset.
With 5 tools, the count is well-scoped for a Godot project management server, covering key development tasks. It's slightly lean but reasonable, as each tool earns its place without feeling bloated or insufficient for common workflows like testing and deployment.
The toolset covers essential Godot project operations: error checking, exporting, importing, running scenes, and running tests. Minor gaps exist, such as no project creation or build management tools, but agents can work around these for core development tasks without significant failures.