Skip to main content
Glama
wgt19861219

Godot MCP Enhanced

by wgt19861219
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Godot MCP Enhanced

No user-submitted related servers found.

    Related Servers

    • Gear

      wvfp
      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
      2
      MIT

    • godot-mcp

      alta01
      A
      license
      C
      quality
      D
      maintenance
      A comprehensive MCP server that gives AI assistants full control over the Godot game engine, providing 149 tools for runtime code execution, scene manipulation, physics, audio, animation, networking, and more.
      154
      92 npm
      MIT

    • Godot MCP

      k0nkupa
      A
      license
      Not graded
      quality
      A
      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

    • godot-mcp-pilot

      Pushks18
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that gives AI assistants direct control over Godot 4 game development projects. It enables launching the editor, running projects, creating and editing scenes, writing GDScript, and inspecting assets through natural language commands.
      44
      10 npm
      4
      MIT

    • godot-mcp

      blentz
      A
      license
      Not graded
      quality
      C
      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.
      229 npm
      AGPL 3.0
    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.1/5.0

    Scored across 26 tools

    Disambiguation2/5

    Direct overlaps exist: `animation` and `animation_track` both expose track/keyframe operations, `screenshot` overlaps with `game`/`qa` capture capabilities, and `workflow` overlaps with `script`, `validation`, and `runtime_assert`. These tools have boundaries but not obvious ownership, so an agent will frequently need to pick between near-equivalent options.

    Naming Consistency3/5

    Names are mostly lowercase snake_case and readable, but the convention is not consistent: noun domains (`scene`, `script`, `game`) are mixed with verb-style names (`confirm_and_execute`, `load_skill`) and abbreviations (`qa`, `cpp`, `animtree`). The `animation`/`animation_track`/`animtree` grouping is especially hard to infer from naming alone.

    Tool Count2/5

    26 tools sits above the already-heavy threshold, and many top-level tools are actually umbrella namespaces containing many subactions, making the real surface much larger. Several tools such as `animation_track`, `workflow`, and `help` could be merged or removed without losing functionality.

    Completeness4/5

    Core Godot workflows are well covered: project, scene, script, runtime, validation, animation, audio, material, particles, profiling, runtime assertions, QA, static analysis, and documentation. The main gaps are dedicated export/build/physics/tilemap tooling and some file lifecycle operations, but these are secondary to the server's primary purpose.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources