Skip to main content
Glama

Related Servers

Alternatives to Godot-MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      The most advanced MCP server for Godot Editor that lets AI assistants operate directly inside your running Godot project for scene creation, script generation, UI authoring, and more.
      49
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets an AI agent work on a Godot 4.x project the way a developer does: read and edit scenes, write scripts, build, test, run, look at the result, and debug what went wrong.
      171 npm
      2
      AGPL 3.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Open-source MCP server connecting AI agents (Claude, Cursor, GitHub Copilot, Gemini, and more) to Unreal Engine 5.7, editor and runtime (C++ plugin + .NET sidecar). Additionally you can use AI Game Dev app (https://ai-game.dev) to generate images, video, audio, 3D, rig, animation and much more.
      57
      Apache 2.0
    • 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
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that lets AI coding agents work on Godot 4 projects, including reading and editing scenes, writing and validating GDScript, running the game, and capturing screenshots.
      25
      24 npm
      MIT

    TDQS

    A4.4/5.0

    Scored across 14 tools

    Disambiguation4/5

    The set splits cleanly along purpose lines: rql-query reads, rql-mutate writes, rql-schema documents, screenshot-* capture images, script-* manage files. Minor overlaps remain — rql-mutate with dry_run=true is effectively a read that duplicates rql-query territory, and screenshot-viewport vs screenshot-camera both return rendered imagery — but descriptions make the boundaries clear enough that an agent should pick correctly.

    Naming Consistency4/5

    All names are kebab-case with a resource prefix (script-, rql-, screenshot-), which is predictable. The suffix convention drifts, however: script-* uses verbs (create/read/update/delete/validate/build/execute), rql-* uses verbs too but in noun-verb order, while screenshot-* uses target nouns (camera/isolated/viewport), and script-attach-to-node is an outlier in length and shape.

    Tool Count5/5

    14 tools is comfortably in the well-scoped range, and each covers a distinct capability (query, mutate, schema lookup, three capture modes, script CRUD plus build/validate/execute/attach). Nothing looks like filler; the segmentation of script operations mirrors familiar file-tool conventions.

    Completeness5/5

    The domain is live Godot editor automation, and the surface covers it end to end: inspection via RQL sources (nodes, files, project settings, console, game log), mutation of scenes, resources, settings, input actions and autoloads via rql-mutate, plus script authoring, validation, build, execution and three screenshot modes. Only marginal gaps exist (e.g. detach is folded into script-attach-to-node with an empty path rather than being its own operation).

    Maintenance

    ActivityActive
    ResponsivenessUsually handled