Skip to main content
Glama
hi-godot

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
      MIT

    • WazziCode Godot

      robertobendi
      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
      A
      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
      27 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
      F
      license
      A
      quality
      C
      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
      -

    • Funplay MCP for Godot

      FunplayAI
      A
      license
      Not graded
      quality
      A
      maintenance
      The most advanced MCP server for Godot Editor that lets AI assistants operate directly inside your running Godot project for scene creation, script generation, UI authoring, and more.
      37
      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

    A4/5.0

    Scored across 46 tools

    Disambiguation3/5

    Most tools have clear domain prefixes (camera_manage, audio_manage, tilemap_manage), but there is meaningful overlap: editor_state duplicates editor_manage(op='state'), scene_manage overlaps scene_open/scene_save, and animation_create overlaps animation_manage. The op-dispatch pattern also means many tools hide multiple operations behind a single name, complicating selection.

    Naming Consistency4/5

    The dominant pattern is domain_verb or domain_manage in lowercase snake_case, which is fairly consistent across 46 tools. A few exceptions like editor_state and batch_execute deviate from the verb-second pattern, but the overall convention remains readable and predictable.

    Tool Count2/5

    46 tools is well beyond the 25+ threshold and feels heavy even for a full editor-automation server. Many small op-clusters (tileset_manage with 2 ops, csg_manage with 2 ops) could be consolidated into fewer, broader tools without losing clarity.

    Completeness4/5

    The surface covers an impressively broad domain: scene editing, nodes, scripts, resources, input, project settings, animation, UI, materials, particles, audio, tilemaps/gridmaps, testing, and game runtime control. Minor lifecycle gaps exist (no script/resource/file delete, no direct shader authoring), but core workflows have no dead ends.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources