Skip to main content
Glama
alta01

godot-mcp

by alta01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to godot-mcp

No user-submitted related servers found.

    Related Servers

    • Gear

      wvfp
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI assistants to directly run, inspect, modify, and debug Godot game development projects through 110+ tools covering scenes, scripts, resources, runtime debugging, and asset management.
      33
      21 npm
      2
      MIT

    • godot-mcp-bridge

      rezaahmadn
      A
      license
      B
      quality
      B
      maintenance
      This MCP server allows AI assistants to control the Godot editor and running games, enabling scene creation, script editing, input simulation, and gameplay testing through 174 tools.
      100
      287 npm
      MIT

    • Godot MCP

      Vollkorn-Games
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that gives AI assistants full control over the Godot game engine, enabling scene building, script writing, game running, and more through natural language.
      75
      148 npm
      3
      MIT

    • godot-mcp-pilot

      Pushks18
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that gives AI assistants direct control over Godot 4 game development projects. It enables launching the editor, running projects, creating and editing scenes, writing GDScript, and inspecting assets through natural language commands.
      44
      13 npm
      4
      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.7/5.0

    Scored across 154 tools

    Disambiguation2/5

    With 154 tools, many have highly overlapping scopes: game_spawn_node vs add_node vs game_instantiate_scene, modify_scene_node vs manage_scene_structure, and a dense cluster of game_audio_* and game_ui_* tools. While individual descriptions clarify some boundaries, the sheer number of similar runtime manipulation tools makes misselection likely.

    Naming Consistency3/5

    Tool names follow three recognizable conventions: game_* for runtime actions, manage_* for project/config operations, and bare verb_noun for scene/file editing. Although consistently snake_case, the mixing of prefixes and standalone verbs like export_mesh_library or update_project_uids prevents a single predictable pattern.

    Tool Count1/5

    154 tools is far beyond typical MCP server scope and will overwhelm agents with too many options. Even a comprehensive Godot toolkit does not justify this extreme count, as many features could be consolidated or exposed through fewer, broader tools.

    Completeness5/5

    The tool surface is exceptionally broad, covering project management, scene editing, runtime game control, input simulation, UI interaction, physics, audio, rendering, animation, and export. There are no obvious dead ends or missing operations for the implied Godot development workflow.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources