Skip to main content
Glama
KeeVeeG

Godot MCP

by KeeVeeG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to Godot MCP

No user-submitted related servers found.

    Related Servers

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

    • godot-mcp-bridge

      TomasLucasUTN
      A
      license
      Not graded
      quality
      A
      maintenance
      Let Claude, Cursor, or any MCP-compatible AI work inside your Godot project: read and edit scenes, write and validate scripts, run the game, drive it, and read the errors — without copy-pasting anything.
      5
      MIT

    • godot-mcp

      WindSeries83
      A
      license
      A
      quality
      B
      maintenance
      MCP bridge between an AI assistant and the Godot editor, enabling control via 6 tools (call methods, run GDScript, screenshots, etc.) over WebSocket.
      10
      7 npm
      1
      MIT

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

    C2.7/5.0

    Scored across 321 tools

    Disambiguation2/5

    Many tool groups have near-identical purposes, e.g. get_project_settings/get_all_project_settings, set_project_setting/set_project_setting_config, add_autoload/add_autoload_config, export_project/export_for_platform, and validate_export/validate_platform_export/validate_export_for_platform. With 321 tools, these overlapping clusters make it very hard for an agent to reliably select the intended tool.

    Naming Consistency2/5

    Although the names are snake_case, the semantic pattern is inconsistent: add/create/setup are used for similar node/resource creation, delete/remove for destruction, get/list for reads, and several near-duplicate suffixes like _config and _platform fragment the vocabulary. Duplicate pairs such as add_autoload vs add_autoload_config and get_project_settings vs get_all_project_settings further undermine predictability.

    Tool Count1/5

    321 tools is an extreme over-fragmentation for an MCP surface. It far exceeds any practical selection budget and contains dozens of redundant variants that could be merged into parameterized tools. This count will overwhelm agent context and degrade tool-selection accuracy.

    Completeness4/5

    The set is remarkably comprehensive, covering scenes, scripts, resources, animation, physics, audio, navigation, rendering, export, debugging, testing, and project settings. A few lifecycle gaps exist, such as no remove_animation_track or remove state machine state, but most gaps can be worked around with generic node/property/script tools.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources