Skip to main content
Glama
Sign In
Godot AI

Godot AI

by hi-godot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Godot AI

No user-submitted related servers found.

    Related Servers

    • 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-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
      28
      MIT

    • WazziCode Godot

      Labyrica
      F
      license
      A
      quality
      A
      maintenance
      MCP server that connects AI coding assistants to a live Godot editor, enabling scene, node, script, resource, runtime, debugger, and test workflows through natural language.
      45
      -

    • AI-godot-mcp

      DC925928496
      A
      license
      C
      quality
      C
      maintenance
      Enables AI-driven game development by providing MCP tools to interact with the Godot editor, including scene editing, node manipulation, script attachment, and scene execution.
      28
      7 npm
      MIT

    • godot-mcp-lite

      baitang-bt
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a secure, authenticated MCP bridge to control a local Godot editor from Cursor, enabling scene/node management, script validation, editor diagnostics, and runtime inspection through a whitelisted set of tools.
      MIT

    • 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
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.6/5.0

    Scored across 47 tools

    Disambiguation3/5

    Many tools target clearly distinct Godot domains, but several paired tools blur boundaries: editor_state duplicates editor_manage(op="state"), scene_get_hierarchy overlaps node_manage get_children and game_manage get_scene_tree across editor/runtime, animation_create overlaps animation_manage clip creation, and test_run/test_manage are two halves of the same workflow. Descriptions help, but the 47-tool surface creates real misselection risk.

    Naming Consistency3/5

    All names are snake_case and readable, but they mix several conventions: many domain_manage wrappers (audio_manage, node_manage, resource_manage) alongside dedicated verb_noun tools (node_create, script_patch, scene_open) and noun-only tools (editor_state, test_run, batch_execute). The pattern is understandable but not a single predictable convention.

    Tool Count2/5

    47 tools is well beyond the typical 3-15 range and past the 25+ threshold where the surface becomes heavy. Godot is a broad domain and the *_manage wrappers consolidate many operations, but the overall tool count still imposes a high selection cost.

    Completeness4/5

    The surface covers an unusually broad Godot editor workflow: scenes, nodes, scripts, resources, filesystem, animation, audio, tilemap/gridmap, materials/shaders, particles, cameras, UI/theme, runtime game inspection and input, tests, logs, sessions, and batch execution. Minor gaps remain, such as broader TileSet terrain/collision/animation configuration and project export, but core CRUD and lifecycle paths are largely present.

    Maintenance

    ActivityActive
    ResponsivenessSyncing

    Resources