Skip to main content
Glama
yanhuifair

Godot MCP

by yanhuifair
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Godot MCP

No user-submitted related servers found.

    Related Servers

    • Godot MCP Server

      Rizzpect
      A
      license
      D
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to manage and interact with Godot Engine projects, including project management, script editing, scene manipulation, asset management, and export.
      46
      462 npm
      1
      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

      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
      148 npm
      89
      MIT

    • Godot MCP

      vberai
      F
      license
      Not graded
      quality
      D
      maintenance
      An out-of-the-box, zero-dependency Model Context Protocol (MCP) server integration designed specifically for the Godot Engine (4.x).Once connected, your AI agents (Claude, Cursor, Trae, ChatGPT) gain access to a powerful set of tools to interact with your active Godot project directory.
      2
      -

    • 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
      148 npm
      5,699
      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

    C2.6/5.0

    Scored across 358 tools

    Disambiguation1/5

    Several near-duplicates exist, such as capture_screenshot and runtime_screenshot, plus multiple status/health-check tools with overlapping purposes. With 358 tools and repeated add_/create_/write_, read_/list_/editor_get_, and set_/editor_set_ namespaces, an agent cannot reliably distinguish intent without searching, which the included search_tools tool implicitly acknowledges.

    Naming Consistency4/5

    Tool names are almost entirely lowercase snake_case with a verb_noun shape, and editor_/runtime_ prefixes create recognizable namespaces. However, related operations use inconsistent verbs (add_input_binding vs write_input_action, create_scene vs editor_create_scene, read_ vs list_ vs editor_get_), and a few oddities like get_status and launch_editor break the strict pattern.

    Tool Count1/5

    358 tools is an extreme mismatch for an MCP server surface; even with good categorization, it is far beyond what an agent can hold or reliably route between. The included search_tools tool is a workaround for tool discovery, not a solution to over-scoping.

    Completeness4/5

    The coverage is encyclopedic: editor automation, runtime debugging, scenes, resources, shaders, audio, navigation, physics, UI, project configuration, and exports all have read/list/create/set support. A few lifecycle gaps exist, such as some entity types having readers but no writers or removers, but these are minor relative to the enormous surface.

    Maintenance

    ActivitySlowing
    ResponsivenessWithin a week

    Resources