Skip to main content
Glama
bebabinlarsson-blip

Godot MCP

by bebabinlarsson-blip
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Godot MCP

No user-submitted related servers found.

    Related Servers

    • godot-omni

      bebabinlarsson-blip
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to automate the Godot Engine editor, including scene authoring, node transforms, tilemap editing, animation, shaders, and live GDScript execution via MCP.
      100
      22
      MIT

    • Godot Forge

      Tann2019
      A
      license
      A
      quality
      C
      maintenance
      Connects AI assistants to the live Godot 4 editor so they can build scenes, scripts, resources and animations, run the game, simulate input, capture screenshots and playtest scenarios, and diagnose runtime errors. Every edit flows through undoable changesets that can be diffed, approved, checkpointed or discarded.
      29
      1
      MIT

    • Godot MCP

      smturtle2
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to build, run, and debug Godot projects by editing scenes and scripts, inspecting live game state, injecting input, capturing viewports, and examining native debugger state through 42 tools.
      European Union Public 1.2

    • Bismuth_MCP_Godot

      QkartBismuth
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to read and edit Godot 4.x scenes and resources, introspect the class API, run the game in a managed headless process with frame stepping, input injection and screenshots, validate scripts, and diagnose code via a built-in GDScript LSP plus a bridge to an already open editor.
      23
      MIT
    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

    A4.1/5.0

    Scored across 46 tools

    Disambiguation4/5

    Most tools target clearly separate Godot subsystems (nodes, scenes, scripts, materials, tilemaps, etc.), so an agent can usually pick correctly. However, there is noticeable overlap: editor_state duplicates editor_manage(op='state'), scene_get_hierarchy overlaps with scene_manage/resource forms, node_get_properties overlaps with node_manage reads, and generic resource_manage overlaps specialized tools like material_manage and theme_manage.

    Naming Consistency4/5

    The names are consistently snake_case with a domain-first pattern, mostly domain_manage for grouped operations and domain_action for single-purpose tools. Minor deviations exist, such as editor_state, logs_read, editor_reload_plugin, scene_get_hierarchy, and project_run, but they remain readable and predictable.

    Tool Count2/5

    With 46 top-level tools, the set is heavy for an MCP server even though Godot is a broad engine. While many tools are multi-op managers that consolidate related actions, the sheer number of top-level entries increases selection burden and exceeds the range where a tool set typically stays well-scoped.

    Completeness4/5

    The surface covers an impressive range of Godot editor workflows: scene/node editing, scripts, resources, materials, animations, UI, tilemaps, gridmaps, CSG, particles, audio, cameras, input, project settings, runtime game inspection, tests, and filesystem access. There are minor gaps such as resource deletion, animation trees/state machines, and some advanced resource workflows, but nothing that blocks typical editor automation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources