Skip to main content
Glama
Rizzpect

Godot MCP Server

by Rizzpect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Godot MCP Server

No user-submitted related servers found.

    Related Servers

    • Godot MCP

      bradypp
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to manage Godot projects, scenes, and editor operations through natural language commands.
      16
      159 npm
      89
      MIT

    • Godot MCP

      Coding-Solo
      A
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol server that enables AI assistants to interact with the Godot game engine, allowing them to launch the editor, run projects, capture debug output, and control project execution.
      14
      159 npm
      5,787
      MIT

    • godot-mcp

      emojiiii
      A
      license
      Not graded
      quality
      C
      maintenance
      A safe, standards-compliant Model Context Protocol server for the Godot Engine editor. It lets an AI client read a Godot project, author scenes/nodes/scripts, run the game and read diagnostics.
      Apache 2.0

    • Godot MCP

      yanhuifair
      A
      license
      C
      quality
      B
      maintenance
      Model Context Protocol server for Godot Engine providing 279 tools across 26 categories for AI assistants to read, inspect, and modify Godot projects via stdio transport.
      100
      342 npm
      34
      AGPL 3.0

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

    D1.6/5.0

    Scored across 46 tools

    Disambiguation2/5

    With 46 tools and no descriptions, many tools overlap in purpose (e.g., read_script vs analyze_script, list_resources vs list_assets, run_script vs run_code). An agent would struggle to select the correct tool confidently. Some tools are clearly distinct, but the overall surface is highly ambiguous.

    Naming Consistency5/5

    All tools consistently use a `godot_` prefix with lowercase snake_case and a verb_noun structure (launch_editor, list_scenes, create_resource). This creates a predictable pattern despite the high number of tools. No mixed conventions or irregular naming appear.

    Tool Count2/5

    46 tools is far beyond the 3-15 ideal range and exceeds the 25+ threshold for over-scoping. While Godot is a complex engine, the sheer number of near-synonymous tools suggests poor curation. Many tools could likely be consolidated.

    Completeness3/5

    The surface covers many domains—scripting, scenes, resources, settings, export—but lacks clear delete/removal operations for scripts, scenes, or resources, leaving lifecycle gaps. Creation and reading exist, but update/delete are inconsistent. Overall broad but not fully complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources