Skip to main content
Glama

Related Servers

Alternatives to godot-assistant

No user-submitted related servers found.

    Related Servers

    • 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
    • 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
      13 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to control and interact with Godot 4 editor, allowing scene manipulation, file editing, and project inspection through natural language.
      MIT
    • 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
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that gives AI assistants full control over the Godot game engine, enabling scene building, script writing, game running, and more through natural language.
      75
      229 npm
      3
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      An enhanced MCP server for interacting with the Godot game engine, enabling AI assistants to launch the editor, run projects, manage scenes and nodes, and handle scripts.
      16
      MIT

    TDQS

    A3.7/5.0

    Scored across 25 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., script_create vs. resource_manage, node_add vs. node_modify, scene_tree vs. node_inspect). Some overlap exists between run_project and editor_control's play/stop, and between get_output and stop_project, but descriptions clarify the boundaries.

    Naming Consistency4/5

    Tool names follow a mostly readable noun_verb or verb_noun pattern with underscores. Groups like scene_* and node_* are consistently prefixed, though overall conventions vary (e.g., stop_project vs. project_info, import_assets vs. resource_manage).

    Tool Count3/5

    25 tools is on the heavy side, near the upper limit of the borderline range. The count is justified by Godot's complexity, but some tools could potentially be consolidated (e.g., node_add and node_modify, or run_project and editor_control).

    Completeness4/5

    The tool set covers project info, file/file management, scripting, resources, scenes, nodes, signals, running/debugging, editor control, and export. Minor gaps include no scene deletion tool and no project settings modification, but core workflows are well supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues