Skip to main content
Glama
rezaahmadn

godot-mcp-bridge

by rezaahmadn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to godot-mcp-bridge

No user-submitted related servers found.

    Related Servers

    • godot-mcp

      alta01
      A
      license
      C
      quality
      D
      maintenance
      A comprehensive MCP server that gives AI assistants full control over the Godot game engine, providing 149 tools for runtime code execution, scene manipulation, physics, audio, animation, networking, and more.
      154
      87 npm
      MIT

    • Gear

      wvfp
      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

    • godot-mcp-pilot

      Pushks18
      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

    • Godot MCP Enhanced

      xinyuzjj
      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
    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.1/5.0

    Scored across 174 tools

    Disambiguation2/5

    Several tools overlap heavily: find_node_references, find_script_references, and search_in_files all grep project files for substrings, and move_to/navigate_to both walk the player character. Multiple property-reading tools (get_node_properties, get_game_node_properties, batch_get_properties, monitor_properties) add further ambiguity, making misselection likely despite detailed descriptions.

    Naming Consistency5/5

    All 174 tool names follow a strict lowercase snake_case verb_noun pattern (e.g., add_node, get_scene_tree, set_shader_param, find_unused_resources). There is no camelCase, no mixed conventions, and the pattern is highly predictable across the entire set.

    Tool Count1/5

    At 174 tools, this is an extreme count that far exceeds even a generous interpretation of the domain's scope. The sheer number overwhelms agents and violates the typical 3-15 tool guideline, even for a game-engine bridge.

    Completeness3/5

    The tool set covers a wide range of Godot workflows (scene editing, animation, audio, physics, UI, navigation, particles, testing, export), but notable lifecycle gaps exist: no delete_resource, no remove_audio_bus, no rename_animation or duplicate_animation. Arbitrary code execution via execute_editor_script can patch some gaps, but the surface is not fully complete for its stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources