Skip to main content
Glama
ChanceFlow

godot-mcp

by ChanceFlow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to godot-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      131 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
      131 npm
      1
      -

    • 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
      396 npm
      1
      MIT

    • godot-mcp-server

      Fulviuus
      A
      license
      C
      quality
      A
      maintenance
      Enables AI agents to interact with the Godot game engine, including project inspection, scene/script parsing, headless exports, runtime control with live scene-tree inspection and evaluation, and API documentation search.
      100
      396 npm
      2
      MIT

    • godot-ai-mcp

      morvoso
      F
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with tools to launch the Godot editor, run projects, manipulate scenes, manage scripts, and control node properties through a standardized MCP interface.
      21
      -
    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.4/5.0

    Scored across 84 tools

    Disambiguation5/5

    Tools are grouped by categories (Animation, Audio, Node, etc.) with clear, distinct actions. Within each category, each tool has a unique purpose (e.g., animation_create vs animation_add_track), minimizing confusion.

    Naming Consistency4/5

    The naming pattern is predominantly 'category_action' in snake_case, which is consistent. Minor deviations like 'configure' vs 'set' (timer_configure vs node_set_property) and some longer names slightly break uniformity.

    Tool Count3/5

    At 84 tools, the server is very comprehensive. While each tool feels justified by Godot's breadth, the count is high and could be overwhelming or excessive for simpler use cases.

    Completeness4/5

    The tool set covers a wide range of Godot subsystems (animation, audio, physics, UI, etc.). Missing some actions like removing animation tracks or audio players, but core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing

    Resources