Skip to main content
Glama
DC925928496

AI-godot-mcp

by DC925928496
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to AI-godot-mcp

No user-submitted related servers found.

    Related Servers

    • godot-ai-mcp

      morvoso
      F
      license
      A
      quality
      C
      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
      -

    • godot-mcp

      SrDarkoll
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to inspect, author, debug, simulate, and visually verify Godot 4.x projects through standard MCP tools, including scene editing, runtime control, and viewport capture.
      229 npm
      1
      MIT

    • GoPeak

      HaD0Yun
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to edit, run, inspect, and fix Godot 4 projects through an MCP server with dynamic tool groups and setup-gated capabilities.
      191 npm
      255
      MIT

    • godot-mcp-bridge

      rezaahmadn
      A
      license
      B
      quality
      B
      maintenance
      This MCP server allows AI assistants to control the Godot editor and running games, enabling scene creation, script editing, input simulation, and gameplay testing through 174 tools.
      100
      287 npm
      MIT

    • Godot MCP

      KeeVeeG
      A
      license
      C
      quality
      A
      maintenance
      Godot MCP connects AI assistants directly to the Godot editor, exposing 300+ tools for scene construction, node manipulation, runtime inspection, input recording, physics setup, animation authoring, and more.
      100
      90 npm
      24
      MIT
    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

    C2.9/5.0

    Scored across 28 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose. Opposing operations (add/remove, connect/disconnect) are paired, and context-specific tools like editor logs and scene tree are separate from node manipulation tools. No two tools overlap in function.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., add_node, play_current_scene). The verb choice is precise and shows a uniform style throughout the set.

    Tool Count4/5

    With 28 tools covering scene editing, node operations, signals, input, autoloads, and editor utilities, the count is on the higher side but justified by the breadth of Godot functionality. It remains manageable and well-scoped.

    Completeness3/5

    The toolset covers many core operations (CRUD for nodes, scenes, signals, autoloads) but lacks tools for creating scripts or resources directly. Missing rename_node and explicit resource creation are gaps that agents may need to work around.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources