Skip to main content
Glama
zbrkic

godot-mcp

by zbrkic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to godot-mcp

No user-submitted related servers found.

    Related Servers

    • dsh-godot-mcp

      G0aT-Shen
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables full control of the Godot engine from any MCP client through three layers: headless project, scene, script, settings and export operations, live editor edits that remain undoable, and inspection of a running game with input injection, frame-stepped digests and screenshots. Each layer also exposes an arbitrary-GDScript escape hatch so unanticipated tasks can still be performed.
      MIT

    • Godot Universal MCP

      Noa3
      A
      license
      B
      quality
      C
      maintenance
      Connects MCP-capable AI clients to a running Godot 4 editor for scene, node, project, and debug runtime operations via a local-first architecture.
      36
      1
      MIT

    • godot-correctness-mcp

      TMHSDigital
      A
      license
      Not graded
      quality
      C
      maintenance
      Offline static correctness MCP server for Godot 4.x GDScript projects that lints code, looks up API symbols, and validates scenes/resources, all without a running editor.
      3 npm
      Creative Commons Attribution Non Commercial No Derivatives 4.0 International

    • godot-ai-mcp

      morvoso
      A
      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
      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

    C2.5/5.0

    Scored across 20 tools

    Disambiguation4/5

    The tools are mostly distinct in purpose, covering different aspects like testing, scene inspection, resource management, and editor interactions. There is slight potential confusion between `inspect_scene_tree` and `find_nodes`, but they serve different goals (hierarchy vs. search). Overall, an agent can reliably select the right tool based on descriptions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, such as `run_tests`, `get_project_settings`, `validate_script`, and `list_resources`. The verbs are action-oriented and the nouns clearly indicate the target resource. This makes the toolset predictable and easy to navigate.

    Tool Count3/5

    With 20 tools, this exceeds the typical 3-15 range, leaning toward the heavier side. However, each tool addresses a specific need in Godot development (testing, export, scene analysis, resource handling, editor access), so the count is justifiable albeit on the upper end. It feels slightly bloated but not excessive.

    Completeness4/5

    The toolset covers a broad range of Godot workflows, including project configuration, validation, running, formatting, scene/node introspection, resource management, and editor state. Missing features like creating or editing scenes/scripts are not core for an MCP that primarily aids analysis and execution. Minor gaps exist (e.g., no explicit node deletion), but agents can work around them.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources