Minimal Godot MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GODOT_LSP_PORT | No | Override default port selection. Default: tries ports 6007, 6005, 6008 in order | |
| GODOT_WORKSPACE_PATH | No | Set Godot project path for LSP initialization. Default: uses workspace from Godot's notification |
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 |
|---|---|
| get_diagnosticsA | Check GDScript files for errors after editing or when analyzing code. Returns syntax errors, type errors, undefined variables, missing functions, and code quality issues from Godot LSP (<1s). Use this tool when: user references .gd files, requests GDScript modifications, or reports code errors. For workspace-wide validation, use scan_workspace_diagnostics instead. |
| scan_workspace_diagnosticsA | Scan entire workspace for GDScript errors across all .gd files (~1-2s for 100+ files). Returns errors from all .gd files excluding addons/ and .godot/. Use to find all errors/warnings in the project. For single-file checks, use get_diagnostics instead (<1s). |
| get_console_outputA | Get console output from Godot debug session. Returns print() statements, errors, and warnings captured during scene execution. Requires an active debug session (run a scene with F5 in Godot). Use to debug runtime behavior, check print output, or monitor warnings. |
| clear_console_outputA | Clear the console output buffer. Use to reset output collection before running a specific test or action. |
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 4 tools
Each tool has a clearly distinct scope: single-file diagnostics, workspace-wide diagnostics, console retrieval, and console clearing. The two diagnostics tools are explicitly differentiated by their descriptions.
All tool names follow a consistent verb_noun snake_case pattern: get_diagnostics, scan_workspace_diagnostics, get_console_output, clear_console_output. The naming convention is uniform and predictable.
Four tools is a well-scoped size for a minimal Godot-focused server. Each tool serves a necessary function without redundant bloat.
The diagnostics side is complete with both single-file and workspace coverage, and the console side covers retrieval and clearing. The only minor gap is that starting a debug session is not provided, so console output depends on an external action in the Godot editor.