Skip to main content
Glama
Godot MCP - Full Control
by cxb2523

Related Servers

Alternatives to Godot MCP - Full Control

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      B
      maintenance
      Enables AI assistants to drive the Godot game engine through 157 tools covering project creation, scene and resource editing, runtime GDScript execution, node and property inspection, signals, physics, audio, UI, animation, networking, and error/log capture. It works both headlessly on project files and live against a running game for debugging and testing.
      157
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Provides AI assistants with full control over the Godot game engine through 157 operations including scene manipulation, runtime code execution, input simulation, and project management.
      19
      98 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to build, run, and debug Godot projects by editing scenes and scripts, inspecting live game state, injecting input, capturing viewports, and examining native debugger state through 42 tools.
      European Union Public 1.2
    • F
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to control Godot game engine projects through a WebSocket bridge. Supports scene editing, node manipulation, script management, and project introspection via 163 registered tools.
      100
      1
      -
    • 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

    TDQS

    C2.6/5.0

    Scored across 157 tools

    Disambiguation2/5

    The 157-tool surface contains many overlapping runtime helpers: game_get_property vs game_get_node_info, game_script vs attach_script, game_audio_play vs game_audio_effect, and multiple scene/UI/light/path operations blur boundaries. Descriptions help somewhat, but an agent faces real misselection risk across similarly named game_* tools.

    Naming Consistency3/5

    All names use snake_case, which is good, but the set mixes several prefix conventions: plain verbs (create_scene), game_* runtime tools, manage_* editor tools, and ad hoc prefixes like validate_* and set_*. The pattern is readable but not fully predictable.

    Tool Count1/5

    157 tools is a severe overreach for practical agent use, far beyond the 3-15 sweet spot. Even with a broad 'full control' domain, this surface is too large to be navigated reliably and should be split into focused servers or grouped tools.

    Completeness4/5

    Coverage is extensive across editor, project files, runtime manipulation, UI, audio, 3D, networking, and export workflows. Minor gaps remain, such as full asset-import or project-deletion lifecycle, but the surface is broadly complete.