Skip to main content
Glama
daremau

godot-mcp-extended

by daremau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
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
      219 npm
      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
      74 PyPI
      1
      MIT

    • Godot MCP

      LeeSinLiang
      A
      license
      A
      quality
      D
      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
      219 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
      219 npm
      1
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 32 tools

    Disambiguation4/5

    Most tools target clearly distinct resources or actions (scene editing, node ops, scripts, build, test, assets, settings). The main ambiguity is within the run/export families: run_project vs run_project_capture and export_check vs export_mesh_library require reading descriptions to choose correctly.

    Naming Consistency4/5

    29 of 32 tools follow a consistent verb_noun snake_case pattern (create_scene, add_node, run_tests, etc.). The three exceptions (dotnet_build, dotnet_test, hook_exec) use a noun_verb order, but they are internally consistent and readable.

    Tool Count3/5

    At 32 tools this is heavy, and some candidates could be consolidated (e.g. run_project and run_project_capture). However, the server is explicitly 'extended' and spans several broad Godot domains, so most tools earn their place.

    Completeness4/5

    Coverage is strong across scene lifecycle, node editing, scripting, running/debugging, build/test, assets, settings, and export. Minor gaps remain: no delete/rename scene or script tools, no disconnect_signal, and no explicit script content editing beyond creation from template.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources