Godot MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_project_infoB | Get Godot project information including configuration, autoloads, and metadata |
| list_scenesA | List all scenes in the Godot project |
| list_scriptsB | List all GDScript files in the project |
| analyze_sceneB | Analyze a specific scene file and return its structure |
| analyze_scriptB | Analyze a GDScript file and return its structure |
| generate_script_templateC | Generate a GDScript template for common patterns |
| analyze_game_architectureA | Analyze the overall game architecture including managers, scenes, and design patterns |
| generate_ui_componentB | Generate UI component templates for common game elements |
| optimize_game_performanceA | Analyze project for performance issues and provide optimization recommendations |
| generate_network_systemC | Generate networking system templates for multiplayer games |
| analyze_error_logC | Analyze Godot error logs and provide suggestions for fixes |
| start_debug_sessionB | Start a debug session to monitor errors and warnings |
| stop_debug_sessionA | Stop an active debug session and get results |
| get_debug_sessionB | Get information about an active debug session |
| analyze_crash_dumpC | Analyze crash information and provide debugging guidance |
| diagnose_projectC | Perform comprehensive project health diagnosis |
| suggest_fixC | Get specific fix suggestions for error messages |
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 17 tools
Each tool has a clearly distinct purpose: analyze tools target different aspects (crash, error, architecture, scene, script), generation tools cover different templates, debug session tools are distinct lifecycle functions, and list tools target different resources. No significant overlap.
All tool names follow a consistent verb_noun snake_case pattern (e.g., analyze_crash_dump, generate_script_template), making them predictable and easy to understand.
With 17 tools, the set is well-scoped for a Godot development assistant, covering analysis, generation, debugging, and project information without being overwhelming.
The tool set covers analysis, generation, and debugging comprehensively, but lacks creation/modification tools for scenes and scripts, and there is no tool to apply suggested fixes or modify project configuration, leaving minor gaps.