Skip to main content
Glama
masteryee-labs

Open Godot MCP

by masteryee-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Open Godot MCP

No user-submitted related servers found.

    Related Servers

    • Gear

      wvfp
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI assistants to directly run, inspect, modify, and debug Godot game development projects through 110+ tools covering scenes, scripts, resources, runtime debugging, and asset management.
      33
      21 npm
      2
      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
      -

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

    • godot-mcp

      blentz
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets an AI agent work on a Godot 4.x project the way a developer does: read and edit scenes, write scripts, build, test, run, look at the result, and debug what went wrong.
      143 npm
      AGPL 3.0
    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.2/5.0

    Scored across 31 tools

    Disambiguation5/5

    Each tool targets a distinct domain (editor, scene, node, script, etc.) with clear read/edit separations. Overlapping concepts like runtime state vs. profiler are clearly differentiated by purpose.

    Naming Consistency5/5

    All tools follow a consistent 'godot_<domain>_<action>' or 'godot_<domain>' pattern using snake_case. No mixed conventions or unexpected variations.

    Tool Count4/5

    31 tools is above the typical 3-15 range, but given the broad scope of Godot engine functionality (editor, scene, scripting, networking, etc.), the count is reasonable and each tool serves a distinct purpose.

    Completeness5/5

    The tool surface covers nearly all major aspects of Godot development: editor control, scene/node editing, scripting, project settings, input, filesystem, debugging, profiling, testing, animation, tilemap, assets, export, and more. No obvious gaps for a game engine MCP.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive

    Resources