io.github.DiegoBr4nd/godot-gut-mcp
Related Servers
Alternatives to io.github.DiegoBr4nd/godot-gut-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to inspect, edit, and run Godot 4 projects — scenes, nodes, signals, resources, animations, tile maps, audio buses, visual shaders, project settings, input actions, and exports — with GDScript language-server diagnostics, offline class reference, live in-game debugging, and GUT/GdUnit4 test runs. It works through a live editor bridge so every edit can be undone with Ctrl+Z, and falls back to headless execution when the editor is closed.1MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to interact with the Godot game engine, including launching the editor, running projects, capturing debug output, and managing scenes.8475 PyPI1MIT
- AlicenseBqualityBmaintenanceEnables AI agents to inspect, modify, run, and debug Godot projects, including scene and script analysis, editor and project management, and visual verification through screenshots.2215 npm14MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to automate Godot 4 projects via headless tooling, live editor control, and runtime remote control, including scene building, testing, and observation.431MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Godot game projects through real-time error detection, automated testing, code analysis, and safe git-based patching. Provides comprehensive project context and development workflow automation for Godot developers.MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with the Godot game engine by launching the editor, running projects, capturing debug output, managing scenes and nodes, and controlling project execution through a standardized interface.18166 npm11MIT
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.