godot-mcp
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 |
|---|---|
| godot_project_infoC | Inspect the configured Godot project. |
| godot_scene_inspectC | Inspect structured nodes, resources, scripts, and signals in a project scene. |
| godot_scene_patchB | Preview or apply one controlled scene property change; dry-run defaults to true. |
| godot_resource_inspectC | Inspect a project resource without modifying it. |
| godot_script_diagnosticsC | Return bounded static diagnostics for a GDScript or C# file. |
| godot_runtime_snapshotC | Read one bounded page of runtime nodes and selected performance monitors. |
| godot_runtime_propertyC | Read one runtime Node property from the read-only bridge. |
| godot_runtime_logsC | Read the bounded observer log ring buffer. |
| godot_runtime_screenshotA | Capture a runtime viewport PNG as base64. |
| godot_run_checkC | Run a command from the explicit project allowlist. |
| godot_stagehand_scenarioC | Run a configured Stagehand scenario and parse JUnit/visual diff outputs. |
| godot_runtime_errorsB | Return warning and error entries from the observer. |
| godot_resource_leaksB | Find RID, ObjectDB, and resource teardown warnings. |
| godot_validate_sceneC | Validate a project scene. |
| godot_validate_autoloadB | Validate project autoload paths. |
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 15 tools
Most tools target clearly distinct scopes: project info, scene/resource inspection, runtime reads, diagnostics, validation, and controlled patching. There is some overlap among runtime diagnostics tools (logs, errors, leaks) and between scene inspection and scene validation, but the descriptions provide enough distinction for selection.
All names use snake_case and a consistent godot_ domain prefix, making them easy to scan. Most follow a scope_action or scope_noun pattern, though a few variants like godot_run_check and godot_stagehand_scenario are slightly less predictable.
Fifteen tools is well-scoped for a Godot project inspection, validation, and runtime debugging server. Each tool appears to cover a distinct operational area without obvious padding.
The surface covers project inspection, scene/resource inspection, validation, runtime observation, diagnostics, screenshots, allowlisted execution, and scenario testing. Minor gaps exist around broader scene/resource editing or creation, since scene_patch only previews/applies one controlled property change.