Skip to main content
Glama
Noa3

Godot Universal MCP

by Noa3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Godot Universal MCP

No user-submitted related servers found.

    Related Servers

    • Godot AI

      hi-godot
      A
      license
      A
      quality
      A
      maintenance
      Connects MCP clients directly to a live Godot editor, enabling AI assistants to build scenes, edit nodes, and control the editor through over 120 operations.
      47
      17,600 PyPI
      3,202
      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
      -

    • MCP for Godot

      Dev-Encrypted
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible AI clients to inspect Godot project and editor state, observe opted-in running scenes, manage processes, and apply permission-scoped guarded edits. It starts read-only and exposes additional capabilities only through explicit command-line flags.
      Apache 2.0

    • 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.
      45
      MIT

    • GDMCP

      theLegend35
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to control and interact with Godot 4 editor, allowing scene manipulation, file editing, and project inspection through natural language.
      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/5.0

    Scored across 36 tools

    Disambiguation4/5

    Tools are well-separated by domain prefixes (scene, script, file, project, runtime, editor). Within each domain the purpose is distinct. Minor potential confusion exists between godot_project_search (plain text) and godot_project_grep (regex), which overlap heavily, and between godot_scene_get_tree and godot_runtime_tree (both trees but different targets).

    Naming Consistency4/5

    Most tools follow a consistent godot_<domain>_<verb> pattern (godot_scene_get_node, godot_script_read, godot_file_write, godot_project_info). A few deviate or use awkward phrasing like godot_scene_find_broken_references and godot_script_todo_index which are noun-heavy rather than verb_action. Overall recognizable but not perfectly uniform.

    Tool Count2/5

    36 tools is a very large surface for a single server. Many tools could be consolidated (e.g. file operations and project operations), and the count makes it heavy. This is near the top end of the scale and risks overwhelming agents.

    Completeness5/5

    The coverage is remarkably thorough for the Godot ecosystem: file CRUD, script lifecycle (create/read/patch/list), scene parsing and validation, runtime control, editor integration, and project health/analysis. The scan, doctor, and grep/search tools add useful discovery capabilities. No obvious dead ends in the core workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources