Skip to main content
Glama
beremaran

Godot Agent Loop

by beremaran
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Godot Agent Loop

No user-submitted related servers found.

    Related Servers

    • godot-mcp

      SrDarkoll
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to inspect, author, debug, simulate, and visually verify Godot 4.x projects through standard MCP tools, including scene editing, runtime control, and viewport capture.
      201 npm
      3
      MIT

    • AutoGodot

      lucas-r-manoguerra
      A
      license
      Not graded
      quality
      D
      maintenance
      Autonomous game development framework that lets AI agents program, design scenes, and run visual QA on Godot 4.x projects — all through the Model Context Protocol (MCP).
      MIT

    • Open Godot MCP

      masteryee-labs
      A
      license
      B
      quality
      D
      maintenance
      MCP server for Godot Engine enabling AI to autonomously develop, test, and debug games with deterministic playtesting, multiplayer testing, DAP debugging, LSP integration, and token efficiency.
      31
      14
      MIT

    • Godot MCP

      k0nkupa
      A
      license
      Not graded
      quality
      C
      maintenance
      A security-first MCP server and Godot editor addon enabling AI agents to observe and control Godot games through bounded, permission-gated tools for debugging, input automation, and project editing.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    C2.5/5.0

    Scored across 20 tools

    Disambiguation3/5

    Most tools are clearly distinct by domain (editor vs running game vs inspect), but get_debug_output, game_get_errors, game_get_logs, and game_get_debug_output-type overlap in capturing output, creating ambiguity. game_scenario and game_wait_until have identical placeholder descriptions ('Property waits need reflection'), making them indistinguishable.

    Naming Consistency2/5

    The naming is mixed: most use verb_noun snake_case (get_godot_version, run_project), but several 'game_*', 'godot_*', and 'editor_*' prefixes follow different conventions, and 'verify_project' vs 'run_project_tests' use similar verb phrases for different actions. The game_* group is consistent internally but the prefixes across the server are arbitrary.

    Tool Count4/5

    20 tools is on the high end but defensible for the apparent scope of controlling a Godot editor session, running tests, and inspecting a live game. It's slightly heavy, likely bordering the 16-25 range, but each tool maps to a plausible action in the workflow.

    Completeness4/5

    The surface covers the full lifecycle well: editor control (session, transaction) is paired with run/stop project, and inspection tools (scene tree, UI, node info, screenshot) cover runtime diagnosis. Minor gaps exist—there's no explicit save/closing_session tool, and debug/log/error retrieval is spread awkwardly across get_debug_output, game_get_errors, and game_get_logs—but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources