Skip to main content
Glama
gurolayanlar

Godot MCP Flash

by gurolayanlar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Godot MCP Flash

No user-submitted related servers found.

    Related Servers

    • godot-mcp-server

      Fulviuus
      A
      license
      C
      quality
      C
      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
      474 npm
      3
      MIT

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

    • Godot MCP

      MhrnMhrn
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to create, edit, and run Godot 4.5+ games by providing tools for project scaffolding, scene manipulation, and engine interaction. It supports full game development workflows including node editing, script attachment, and project execution with debugging capabilities.
      24
      5
      MIT

    • 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
      221 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
      44 PyPI
      1
      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.3/5.0

    Scored across 22 tools

    Disambiguation3/5

    Several near-overlapping pairs exist: get_debug_output/view_log both retrieve process output, run_project/run_scene and capture_screenshot/capture_scene_screenshot are similar paired operations, though descriptions mostly clarify the differences. get_node_insights is also misleading since it analyzes .gd script files, not scene-tree nodes, even though the description does clarify this.

    Naming Consistency5/5

    All 22 tools follow a consistent snake_case verb_noun pattern (launch_editor, run_project, list_projects, capture_scene_screenshot) with no mixed conventions, vague single-word verbs, or stylistic deviations. Compound forms like update_project_uids and get_godot_version remain within the same predictable pattern.

    Tool Count3/5

    At 22 tools, this sits in the heavy range, and several are ultra-specific (export_mesh_library, load_sprite, update_project_uids) that feel like edge-case additions rather than core workflow tools. However, the server does span project management, scene editing, debugging, and screenshot capture, so most tools have a legitimate place.

    Completeness3/5

    Project discovery, launching, running, debugging, and screenshot verification are well covered, but scene editing has dead ends: create_scene/add_node/save_scene exist with no remove_node or delete_scene counterpart. There is also no script creation or editing despite get_node_insights providing deep GDScript analysis, leaving the authoring surface one-directional.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources