Skip to main content
Glama

Related Servers

Alternatives to GoPeak

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI assistants to directly run, inspect, modify, and debug Godot game development projects through 110+ tools covering scenes, scripts, resources, runtime debugging, and asset management.
      33
      21 npm
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with tools to launch the Godot editor, run projects, manipulate scenes, manage scripts, and control node properties through a standardized MCP interface.
      21
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to automate the Godot Engine editor, including scene authoring, node transforms, tilemap editing, animation, shaders, and live GDScript execution via MCP.
      100
      27
      MIT
    • F
      license
      A
      quality
      A
      maintenance
      MCP server that connects AI coding assistants to a live Godot editor, enabling scene, node, script, resource, runtime, debugger, and test workflows through natural language.
      45
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to launch and control the Godot editor, run projects, capture debug output, inspect project structure, and manage scenes, nodes, and UIDs through MCP tools. It provides a direct feedback loop for debugging and code generation in Godot projects.
      14
      194 npm
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      Enables AI-driven game development by providing MCP tools to interact with the Godot editor, including scene editing, node manipulation, script attachment, and scene execution.
      28
      8 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 33 tools

    Disambiguation4/5

    Tools are largely distinguished by domain prefix and action, but a few pairs overlap: editor-status vs runtime-status, editor-debug-output vs dap-output, and tool-catalog vs tool-groups. Descriptions help resolve most ambiguity, but an agent could still hesitate between editor/runtime status and debug output sources.

    Naming Consistency4/5

    Names follow a consistent kebab-case, domain-prefixed convention (e.g., scene-node-add, project-setting-get, script-modify). Minor deviation: some entries are noun phrases (scene-nodes, runtime-status) while others are verb phrases (scene-create, script-create), but the pattern remains predictable.

    Tool Count2/5

    33 visible core tools exceed the typical 3–15 well-scoped range, and the server also advertises 78 dynamic tools. The grouping mechanism mitigates this, but the visible set alone is still heavy and risks overwhelming an agent.

    Completeness4/5

    Core workflows for project, scene, script, class, signal, export, and editor are covered, but notable gaps remain: no resource creation/deletion, no signal disconnect, and no scene/script deletion in the visible set. The dynamic tool groups and tool-catalog provide a workaround, but the core surface is not fully self-contained.

    Maintenance

    ActivityInactive
    ResponsivenessWithin a week