Skip to main content
Glama
YasiruRF

godot-mcp

by YasiruRF
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to godot-mcp

No user-submitted related servers found.

    Related Servers

    • Bismuth_MCP_Godot

      QkartBismuth
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to read and edit Godot 4.x scenes and resources, introspect the class API, run the game in a managed headless process with frame stepping, input injection and screenshots, validate scripts, and diagnose code via a built-in GDScript LSP plus a bridge to an already open editor.
      23
      MIT

    • Nexora Godot MCP

      Gh0stDeveloper
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI hosts to work directly on Godot Engine projects through a local, self-hosted gateway that performs structured, permission-aware operations such as creating and editing scenes, nodes, resources and scripts, running and debugging projects, and exporting builds. All actions stay confined to approved project roots, are auditable, and can require confirmation for destructive steps.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 20 tools

    Disambiguation5/5

    File-based and editor-prefixed tools form two clearly separated groups, and parallel operations like add_node vs editor_add_node are distinguished by both naming and explicit live/undo behavior. Even similar returns like read_scene and editor_get_scene_tree are unambiguous because their sources (disk vs open editor tab) are clearly stated.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun or editor_verb_noun pattern, and the editor_ prefix is applied uniformly across live-editor operations. Minor inconsistencies exist in retrieval verbs (list/read/get) and in set_node_properties vs editor_set_properties, but the overall pattern remains predictable.

    Tool Count3/5

    With 20 tools, the set sits at the heavy end of the range, largely because file-based operations and live-editor operations duplicate each other. Each tool does have a distinct purpose, but the count feels borderline for a single MCP server.

    Completeness4/5

    The toolset covers the core Godot workflow well: listing/reading/creating scenes, editing nodes and scripts, headless runs, and live editor control. Minor gaps such as deleting scene files, moving nodes, or deleting/renaming scripts are workable around rather than blocking.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources