io.github.DiegoBr4nd/godot-gut-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GODOT_PATH | Yes | Path to the Godot executable | |
| GODOT_PROJECT_PATH | Yes | Path to the Godot project folder (containing project.godot) |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_all_testsB | Ejecutar todas las pruebas del proyecto Godot y devolver un resumen |
| run_test_fileA | Ejecutar un archivo de pruebas. Ejemplo: res://test_test_player.gd |
| get_failuresB | Devolver solo las pruebas que fallaron. Para corregir rápido. |
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 3 tools
Each tool has a clear, distinct purpose: running all tests, running a specific test file, and retrieving failures from the last run. There is minimal overlap, as get_failures is a targeted diagnostic rather than a duplicate of the test runners.
All tool names follow a consistent verb_noun snake_case pattern: run_all_tests, run_test_file, get_failures. No mixed conventions or vague verbs.
With 3 tools, the server is slightly lean but well-scoped for its purpose of running GUT tests and reporting failures. It sits at the lower edge of the ideal range but does not feel insufficient.
The server covers the core testing lifecycle: run all tests, run a specific file, and inspect failures. A minor gap is the lack of running a single test method or listing available tests, but this does not severely hinder typical usage.