Skip to main content
Glama

Gear

Made with Godot npm

Gear ermöglicht es KI-Assistenten, deine Godot-Projekte direkt auszuführen, zu untersuchen, zu ändern und zu debuggen.


Schnellstart (3 Minuten)

Systemanforderungen

  • Godot 4.x

  • Node.js 18+

  • Ein MCP-kompatibler Client (Claude Desktop, Cursor, Cline, etc.)

1) Gear starten

npx -y gear

Oder global installieren:

npm install -g gear-godot-mcp
gear

2) MCP-Client konfigurieren

Füge dies zur Konfigurationsdatei deines Clients (z. B. Claude Desktop) hinzu:

{
  "mcpServers": {
    "godot": {
      "command": "npx",
      "args": ["-y", "gear"],
      "env": {
        "GODOT_PATH": "/path/to/godot"
      }
    }
  }
}

3) Probiere diese Befehle aus

  • "Liste alle Godot-Projekte im Verzeichnis /your/projects auf"

  • "Erstelle scenes/Player.tscn mit CharacterBody2D als Wurzelknoten"

  • "Führe das Projekt aus, rufe die Debug-Ausgabe ab und behebe den Fehler"


Related MCP server: Godot MCP Enhanced

Warum Gear?

Kernvorteile

Merkmal

Beschreibung

Echtzeit-Feedback

Spiel ausführen, Logs prüfen, sofort beheben

110+ Tools

Deckt Szenen/Skripte/Ressourcen/Laufzeit/LSP/Debugging/Eingabe/Assets ab

Token-effizient

Standardmäßig nur 33 Kern-Tools, Aktivierung bei Bedarf

Dynamische Tool-Gruppen

Automatische Aktivierung relevanter Gruppen bei der Suche

Tiefe Integration

ClassDB-Abfragen, Laufzeit-Inspektion, Breakpoint-Debugging

Anwendungsfälle

  • ✅ Indie-Entwickler, die KI zur Beschleunigung der Entwicklung nutzen

  • ✅ Teams, die möchten, dass die KI den tatsächlichen Projekt-/Laufzeitstatus versteht

  • ✅ Intensive Debugging-Workflows (Breakpoints, Stack-Traces, Laufzeit-Inspektion)


Tool-Nutzungsmodi

Tool-Expositionsstufen

Gear bietet drei Modi für die Tool-Exposition:

Modus

Anzahl der Tools

Beschreibung

compact (Standard)

33 Kern + 78 bei Bedarf

Token-effizient, Laden bei Bedarf

full

110+

Alle Tools exponiert

legacy

110+

Identisch mit full

Dynamische Tool-Gruppen im compact-Modus

Im compact-Modus sind 78 zusätzliche Tools in 22 dynamischen Tool-Gruppen organisiert:

Tool-Gruppe

Anzahl Tools

Beschreibung

scene_advanced

3

Knoten duplizieren, neu parenten, Sprites laden

runtime

4

Laufzeit-Szeneninspektion, Eigenschaftsänderungen

dap

6

Breakpoints, Einzelschritt-Ausführung, Stack-Traces

lsp

3

Code-Vervollständigung, Hover, Symbolliste

testing

6

Screenshots, Eingabe-Injektion

animation

5

Animationen, Tracks, Zustandsautomaten

resource

4

Materialien, Shader, Ressourcenerstellung

...

...

Und mehr

Verwendung von Tool-Gruppen

1. Automatische Aktivierung (Empfohlen)

Verwende tool.catalog, um nach relevanten Tools zu suchen; passende Gruppen werden automatisch aktiviert.

2. Manuelle Aktivierung

Verwende tool.groups, um spezifische Gruppen manuell zu aktivieren. "Aktiviere die dap-Gruppe zum Debuggen"

3. Deaktivierung

Verwende tool.groups, um aktivierte Gruppen zurückzusetzen.


Installation

Methode A: npx (Empfohlen)

npx -y gear

Methode B: Globale Installation

npm install -g gear-godot-mcp
gear

Methode C: Installation aus dem Quellcode

git clone https://github.com/HaD0Yun/Gear-godot-mcp.git
cd Gear-godot-mcp
npm install
npm run build
node build/index.js

Funktionsübersicht

Szenenbearbeitung

  • Szenen erstellen, Knoten hinzufügen/löschen

  • Knoteneigenschaften ändern

  • Knoten neu parenten

Skript-Workflow

  • Skripte erstellen/ändern

  • Skriptstruktur analysieren

  • Symbole umbenennen

Laufzeit-Debugging

  • Laufzeit-Szenenbaum untersuchen

  • Breakpoints setzen, Einzelschritt-Ausführung

  • Variablenwerte anzeigen

Eingabe & Screenshots

  • Tastatur-/Mauseingaben injizieren

  • Spielbildschirm aufnehmen

  • Viewport-Capture

Asset-Management

  • CC0-Assets suchen (Poly Haven, AmbientCG, Kenney)

  • Ressourcen ins Projekt herunterladen


Umgebungsvariablen

Variable

Zweck

Standardwert

GEAR_TOOL_PROFILE

Tool-Expositionsmodus

compact

GODOT_PATH

Pfad zur Godot-Executable

Automatische Erkennung

GODOT_BRIDGE_PORT

Bridge-Service-Port

6505

GEAR_TOOLS_PAGE_SIZE

Seitengröße der Tool-Liste

33

DEBUG

Debug-Logs

false


Häufig gestellte Fragen

Problem

Lösung

Godot nicht gefunden

GODOT_PATH Umgebungsvariable setzen

Tool-Liste leer

MCP-Client neu starten

Projektpfad ungültig

Sicherstellen, dass project.godot existiert

Laufzeit-Tools funktionieren nicht

Runtime-Addon-Plugin installieren und aktivieren

Tool nicht gefunden

tool.catalog zur Suche und Aktivierung nutzen


Lizenz

MIT — siehe LICENSE für Details.

Danksagungen

Available Tools

33 tools
class-infoA

[compact alias of query_class_info] Get detailed information about a specific Godot class: methods, properties, signals, enums. Use to discover available properties before calling add_node/create_resource/set_node_properties, or to find methods before call_runtime_method.

Inputs: projectPath (required), className (required), includeInherited.

class-queryA

[compact alias of query_classes] Query available Godot classes from ClassDB with filtering. Use to discover node types, resource types, or any class before using add_node/create_resource. Categories: node, node2d, node3d, control, resource, physics, physics2d, audio, visual, animation.

Inputs: projectPath (required), filter, category, instantiableOnly.

dap-outputB

[compact alias of dap_get_output] Get captured Godot DAP console output lines

Inputs: no named parameters.

editor-debug-outputA

[compact alias of get_debug_output] Retrieves console output and errors from the currently running Godot project. Use after run_project to check logs, errors, and print statements. Returns empty if no project is running.

Inputs: reason (required).

editor-launchA

[compact alias of launch_editor] Opens the Godot editor GUI for a project. Use when visual inspection or manual editing of scenes/scripts is needed. Opens a new window on the host system. Requires: project directory with project.godot file.

Inputs: projectPath (required).

editor-runA

[compact alias of run_project] Launches a Godot project in a new window and captures output. Use to test gameplay or verify script behavior. Runs until stop_project is called. Use get_debug_output to retrieve logs.

Inputs: projectPath (required), scene.

editor-statusA

[compact alias of get_editor_status] Returns the connection status of the Godot Editor Plugin bridge. Use to check if the editor is connected before using scene/resource tools that require the editor plugin.

Inputs: no named parameters.

editor-stopA

[compact alias of stop_project] Terminates the currently running Godot project process. Use to stop a project started with run_project. No effect if no project is running.

Inputs: reason (required).

editor-versionA

[compact alias of get_godot_version] Returns the installed Godot engine version string. Use to check compatibility (e.g., Godot 4.4+ features like UID). Returns version like "4.3.stable" or "4.4.dev".

Inputs: reason (required).

export-presetsA

[compact alias of list_export_presets] Lists all export presets defined in export_presets.cfg. Use before export_project to see available targets (Windows, Linux, Android, etc.).

Inputs: projectPath (required), includeTemplateStatus.

export-runA

[compact alias of export_project] Exports the project to a distributable format. Use to build final game executables. Requires export templates installed.

Inputs: projectPath (required), preset (required), outputPath (required), debug.

lsp-diagnosticsC

[compact alias of lsp_get_diagnostics] Get GDScript diagnostics from Godot Language Server for a script file.

Inputs: projectPath (required), scriptPath (required).

project-infoA

[compact alias of get_project_info] Returns metadata about a Godot project including name, version, main scene, autoloads, and directory structure. Use to understand project before modifying. Requires valid project.godot.

Inputs: projectPath (required).

project-listA

[compact alias of list_projects] Scans a directory for Godot projects (folders containing project.godot). Use to discover projects before using other tools. Returns array of {path, name}.

Inputs: directory (required), recursive.

project-setting-getA

[compact alias of get_project_setting] Reads a value from project.godot settings. Use to check game name, window size, physics settings, etc.

Inputs: projectPath (required), setting (required).

project-setting-setA

[compact alias of set_project_setting] Writes a value to project.godot settings. Use to configure game name, window size, physics, etc.

Inputs: projectPath (required), setting (required), value (required).

resource-dependenciesA

[compact alias of get_dependencies] Analyzes resource dependencies and detects circular references. Use to understand what a scene/script depends on before refactoring.

Inputs: projectPath (required), resourcePath (required), depth, includeBuiltin.

runtime-statusA

[compact alias of get_runtime_status] Checks if a Godot game instance is running and connected for live debugging. Use before other runtime tools.

Inputs: projectPath (required).

scene-createA

[compact alias of create_scene] Creates a new Godot scene file (.tscn) with a specified root node type. Use to start building new game levels, UI screens, or reusable components. The scene is saved automatically after creation.

Inputs: projectPath (required), scenePath (required), rootNodeType.

scene-node-addA

[compact alias of add_node] Adds ANY node type to an existing scene. This is the universal node creation tool — replaces all specialized create_* node tools. Supports ALL ClassDB node types (Camera3D, DirectionalLight3D, AudioStreamPlayer, HTTPRequest, RayCast3D, etc.). Set any property via the properties parameter with type conversion support (Vector2, Vector3, Color, etc.). Use query_classes to discover available node types. Use query_class_info to discover available properties for a type.

Inputs: projectPath (required), scenePath (required), nodeType (required), nodeName (required), +2 more.

scene-node-deleteA

[compact alias of delete_node] Removes a node and all its children from a scene. Use to clean up unused nodes. Cannot delete root node. Scene is saved automatically unless saveScene=false.

Inputs: projectPath (required), scenePath (required), nodePath (required), saveScene.

scene-node-propertiesA

[compact alias of get_node_properties] Returns all properties of a specific node in a scene. Use to inspect current values before modifying. Returns property names, values, and types.

Inputs: projectPath (required), scenePath (required), nodePath (required), includeDefaults.

scene-nodesA

[compact alias of list_scene_nodes] Returns complete scene tree structure with all nodes, types, and hierarchy. Use to understand scene organization before modifying. Returns nested tree with node paths.

Inputs: projectPath (required), scenePath (required), depth, includeProperties.

scene-node-setA

[compact alias of set_node_properties] Sets multiple properties on a node in a scene. Prerequisite: scene and node must exist (use create_scene and add_node first). Use to modify position, scale, rotation, or any node-specific properties. Scene is saved automatically unless saveScene=false.

Inputs: projectPath (required), scenePath (required), nodePath (required), properties (required), +1 more.

scene-saveA

[compact alias of save_scene] Saves changes to a scene file or creates a variant at a new path. Most scene modification tools save automatically, but use this for explicit saves or creating variants.

Inputs: projectPath (required), scenePath (required), newPath.

script-createA

[compact alias of create_script] Creates a new GDScript (.gd) file with optional templates. Use to generate scripts for game logic. Templates: "singleton" (autoload), "state_machine" (FSM), "component" (modular), "resource" (custom Resource).

Inputs: projectPath (required), scriptPath (required), className, extends, +3 more.

script-infoA

[compact alias of get_script_info] Analyzes a GDScript and returns its structure: functions, variables, signals, class_name, extends. Use before modify_script to understand existing code.

Inputs: projectPath (required), scriptPath (required), includeInherited.

script-modifyA

[compact alias of modify_script] Adds functions, variables, or signals to an existing GDScript. Use to extend scripts without manual editing. Supports @export, @onready annotations and type hints.

Inputs: projectPath (required), scriptPath (required), modifications (required), reason.

signal-connectA

[compact alias of connect_signal] Creates a signal connection between nodes in a scene. Prerequisite: source and target nodes must exist. Use to wire up button clicks, collision events, custom signals. Saved to scene file.

Inputs: projectPath (required), scenePath (required), sourceNodePath (required), signalName (required), +3 more.

tool-catalogA

[compact alias of tool_catalog] Discover available tools including hidden legacy tools. Use query to search by capability keywords. Results include group categorization (core/dynamic). Matching dynamic groups are auto-activated and become available immediately. Core groups (always visible): core_meta, core_project, core_editor, core_scene, core_script, core_class, core_signal, core_resource, core_export, core_runtime, core_visualizer, core_diagnostics. Dynamic groups (on-demand): scene_advanced, uid, import_export, autoload, signal, runtime, resource, animation, plugin, input, tilemap, audio, navigation, theme_ui, asset_store, testing, dx_tools, intent_tracking, class_advanced, lsp, dap, version_gate.

Inputs: query, limit.

tool-groupsA

[compact alias of manage_tool_groups] Manage tool groups. Actions: list (show all core + dynamic groups), activate (enable a dynamic group), deactivate (disable a dynamic group), reset (disable all dynamic), status (show current state). Core groups (always visible, 33 tools): core_meta, core_project, core_editor, core_scene, core_script, core_class, core_signal, core_resource, core_export, core_runtime, core_visualizer, core_diagnostics. Dynamic groups (on-demand, 78 tools): scene_advanced, uid, import_export, autoload, signal, runtime, resource, animation, plugin, input, tilemap, audio, navigation, theme_ui, asset_store, testing, dx_tools, intent_tracking, class_advanced, lsp, dap, version_gate.

Inputs: action (required), group.

visualizer-mapA

[compact alias of map_project] Crawl the entire Godot project and build an interactive visual map of all scripts showing their structure (variables, functions, signals), connections (extends, preloads, signal connections), and descriptions. Opens an interactive browser-based visualization at localhost:6505.

Inputs: projectPath (required), root, include_addons.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 33 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, especially with descriptive aliases. However, the large number of tools (33) and some overlap between output-related tools (dap-output, editor-debug-output, lsp-diagnostics) could cause minor confusion, though descriptions clarify the sources.

    Naming Consistency5/5

    All tool names follow a consistent lowercase-with-hyphens pattern (e.g., class-info, editor-run). No mixed conventions or irregular formats, making it predictable for an agent.

    Tool Count3/5

    33 tools is above the typical well-scoped range (3-15). While the breadth of Godot development justifies many tools, the count is borderline high and may overwhelm agents, despite the management tools (tool-catalog, tool-groups).

    Completeness4/5

    The toolset covers core Godot workflows: project, scene, script, class, export, runtime, debugging, and diagnostics. Minor gaps exist (e.g., no explicit file delete or node rename), but essential CRUD and lifecycle operations are present.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      C
      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
      4
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      An enhanced MCP server for interacting with the Godot game engine, enabling AI assistants to launch the editor, run projects, manage scenes and nodes, and handle scripts.
      16
      MIT
    • A
      license
      B
      quality
      D
      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
      443 npm
      1
      MIT