Skip to main content
Glama
daskoon

Godot MCP

by daskoon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Godot 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
      44 PyPI
      1
      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
      228 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
      228 npm
      1
      -

    • godot-mcp

      Sovr23
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to launch and control the Godot game engine, run projects, capture debug output, and manage scenes and project configurations.
      14
      228 npm
      MIT

    • Godot MCP

      daskoon
      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
      228 npm
      MIT
    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

    B3.4/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct action (launch, run, stop, get, create, add, load, export, save, update) on a specific resource (editor, project, scene, node, sprite, UID). Minor overlap between run_project and get_debug_output is resolved by descriptions. No two tools appear to do the same thing.

    Naming Consistency5/5

    All 14 tools use snake_case with a clear verb_noun pattern (e.g., launch_editor, get_project_info, create_scene). No mixing of conventions or vague names. The naming is highly predictable.

    Tool Count5/5

    14 tools is well within the typical 3-15 range and each tool covers a distinct functional area (editor control, project management, scene editing, UID handling). No tool feels redundant or out of scope.

    Completeness3/5

    The toolset covers scene creation, node addition, sprite loading, saving, and UID management, but lacks tools for reading scene structure, removing nodes, updating node properties, or deleting scenes. Project creation and settings modification are also absent. These gaps prevent full CRUD lifecycle support for scene editing.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources