Skip to main content
Glama
ibnutoriq

Godot MCP Extended

by ibnutoriq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Godot MCP Extended

No user-submitted related servers found.

    Related Servers

    • 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
      229 npm
      MIT

    • Godot MCP

      MhrnMhrn
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to create, edit, and run Godot 4.5+ games by providing tools for project scaffolding, scene manipulation, and engine interaction. It supports full game development workflows including node editing, script attachment, and project execution with debugging capabilities.
      24
      5
      MIT

    • 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
      57 PyPI
      1
      MIT

    • Godot MCP Server

      matula
      A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to interact with and manipulate Godot game engine projects, including creating projects, launching editor, managing scenes and nodes.
      12
      379 npm
      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
      229 npm
      11
      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

    A3.6/5.0

    Scored across 50 tools

    Disambiguation5/5

    Each tool has a distinct purpose, with clear differentiation between similar operations like run_project, run_and_capture_errors, and run_scene_test through detailed descriptions. Pairs like add/remove_autoload are obvious complements.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with lowercase and underscores, e.g., add_node, get_scene_tree, set_node_property. No mixed conventions or abbreviations.

    Tool Count4/5

    At 50 tools, the set is large but justified by the breadth of Godot engine features it covers (scenes, scripts, resources, input, testing, etc.). A few tools could potentially be merged, but the granularity aids agent precision.

    Completeness5/5

    The tool surface covers the full Godot development lifecycle: scene editing, scripting, resources, input, autoloads, groups, signals, debugging, testing, and project settings. No major gaps are apparent.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources