Skip to main content
Glama
DiegoBr4nd

io.github.DiegoBr4nd/godot-gut-mcp

by DiegoBr4nd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to io.github.DiegoBr4nd/godot-gut-mcp

No user-submitted related servers found.

    Related Servers

    • godot-mcp

      ChanceFlow
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to interact with the Godot game engine, including launching the editor, running projects, capturing debug output, and managing scenes.
      84
      47 PyPI
      1
      MIT

    • Godot Sentinel MCP

      AustinMander
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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

    • Godot MCP

      LeeSinLiang
      A
      license
      A
      quality
      F
      maintenance
      Enables 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.
      18
      159 npm
      11
      MIT

    • Godot MCP

      Zycroft
      A
      license
      B
      quality
      Not graded
      maintenance
      Enables 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.
      14
      159 npm
      1
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources