Skip to main content
Glama
LeeSinLiang

Godot MCP

by LeeSinLiang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Godot MCP

No user-submitted related servers found.

    Related Servers

    • Godot MCP

      Zycroft
      A
      license
      B
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with the Godot game engine by launching the editor, running projects, capturing debug output, managing scenes and nodes, and controlling project execution through a standardized interface.
      14
      159 npm
      1
      -

    • godot-mcp

      ChanceFlow
      A
      license
      B
      quality
      C
      maintenance
      Enables AI assistants to interact with the Godot game engine, including launching the editor, running projects, capturing debug output, and managing scenes.
      84
      1
      MIT

    • godot-mcp

      Sovr23
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to launch and control the Godot game engine, run projects, capture debug output, and manage scenes and project configurations.
      14
      159 npm
      MIT

    • Godot MCP Server

      matula
      A
      license
      C
      quality
      D
      maintenance
      Enables AI assistants to interact with and manipulate Godot game engine projects, including creating projects, launching editor, managing scenes and nodes.
      12
      343 npm
      1
      MIT

    • godot-ai-mcp

      morvoso
      F
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with tools to launch the Godot editor, run projects, manipulate scenes, manage scripts, and control node properties through a standardized MCP interface.
      21
      -
    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

    A3.5/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is some overlap between get_debug_output and get_remote_debug_output, which could cause confusion as both relate to debug output. Additionally, tools like launch_editor and run_project might be ambiguous in their execution context, but descriptions help clarify their roles.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern throughout, such as add_node, capture_screenshot, and connect_remote_debugger. There are no deviations in naming conventions, making the set predictable and easy to understand.

    Tool Count4/5

    With 18 tools, the count is slightly high but reasonable for a Godot MCP server covering project management, debugging, and scene operations. It feels comprehensive without being overwhelmingly heavy, though it could be trimmed for tighter focus.

    Completeness4/5

    The tool surface covers key areas like project handling, debugging, and scene manipulation with minor gaps, such as missing tools for editing node properties or managing resources beyond UIDs. However, core workflows are well-supported, allowing agents to perform essential tasks effectively.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources