Skip to main content
Glama

Gear

Made with Godot npm

Gearを使用すると、AIアシスタントがあなたのGodotプロジェクトを直接実行、検査、修正、デバッグできるようになります。


クイックスタート (3分)

環境要件

  • Godot 4.x

  • Node.js 18+

  • MCP対応クライアント (Claude Desktop, Cursor, Clineなど)

1) Gearの起動

npx -y gear

またはグローバルインストール:

npm install -g gear-godot-mcp
gear

2) MCPクライアントの設定

Claude Desktopなどのクライアントの設定ファイルに以下を追加します:

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

3) 指示を試す

  • 「/your/projects ディレクトリ内のすべてのGodotプロジェクトをリストアップして」

  • 「scenes/Player.tscn を作成して、ルートノードは CharacterBody2D にして」

  • 「プロジェクトを実行してデバッグ出力を取得し、エラーを修正して」


Related MCP server: Godot MCP Enhanced

Gearを選ぶ理由

主な利点

特徴

説明

リアルタイムフィードバック

ゲームの実行、ログの確認、即時の修正

110以上のツール

シーン/スクリプト/リソース/ランタイム/LSP/デバッグ/入力/アセットを網羅

トークン効率

デフォルトでは33個のコアツールのみを公開し、必要に応じてアクティブ化

動的ツールグループ

ツール検索時に、関連するツールグループを自動的にアクティブ化

深い統合

ClassDBクエリ、ランタイム検査、ブレークポイントデバッグ

利用シーン

  • ✅ AIを活用して開発を加速させたい個人開発者

  • ✅ AIに実際のプロジェクトやランタイムの状態を理解させたいチーム

  • ✅ 高度なデバッグワークフロー (ブレークポイント、スタックトレース、ランタイム検査) を必要とする場合


ツールの使用モード

ツールの公開レベル

Gearには3つのツール公開モードがあります:

モード

ツール数

説明

compact (デフォルト)

33コア + 78個のオンデマンドアクティブ化

トークン効率が高く、必要に応じてロード

full

110以上

すべて公開

legacy

110以上

full と同じ

compactモードの動的ツールグループ

compact モードでは、78個の追加ツールが 22個の動的ツールグループ に整理されています:

ツールグループ

ツール数

説明

scene_advanced

3

ノードの複製、再ペアレント、スプライトのロード

runtime

4

ランタイムシーン検査、プロパティ変更

dap

6

ブレークポイント、ステップ実行、スタックトレース

lsp

3

コード補完、ホバー、シンボルリスト

testing

6

スクリーンショット、入力インジェクション

animation

5

アニメーション、トラック、ステートマシン

resource

4

マテリアル、シェーダー、リソース作成

...

...

その他多数

ツールグループの使用方法

1. 自動アクティブ化 (推奨)

tool.catalog を使用して関連ツールを検索すると、一致するツールグループが自動的にアクティブ化されます

2. 手動アクティブ化

tool.groups を使用して特定のツールグループを手動でアクティブ化します 「dap ツールグループをアクティブにしてデバッグを開始して」

3. 無効化

tool.groups を使用して、アクティブ化されたグループをリセットします


インストール方法

方法 A: npx (推奨)

npx -y gear

方法 B: グローバルインストール

npm install -g gear-godot-mcp
gear

方法 C: ソースコードからインストール

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

機能一覧

シーン編集

  • シーンの作成、ノードの追加/削除

  • ノードプロパティの変更

  • ノードの再ペアレント

スクリプトワークフロー

  • スクリプトの作成/変更

  • スクリプト構造の解析

  • シンボルのリネーム

ランタイムデバッグ

  • ランタイムシーンツリーの検査

  • ブレークポイントの設定、ステップ実行

  • 変数値の確認

入力とスクリーンショット

  • キーボード/マウス入力の注入

  • ゲーム画面のキャプチャ

  • ビューポートキャプチャ

アセット管理

  • CC0素材の検索 (Poly Haven, AmbientCG, Kenney)

  • プロジェクトへのリソースダウンロード


環境変数

変数

用途

デフォルト値

GEAR_TOOL_PROFILE

ツール公開モード

compact

GODOT_PATH

Godot実行ファイルのパス

自動検出

GODOT_BRIDGE_PORT

Bridgeサービスのポート

6505

GEAR_TOOLS_PAGE_SIZE

ツールリストのページサイズ

33

DEBUG

デバッグログ

false


よくある質問

問題

解決策

Godotが見つからない

GODOT_PATH 環境変数を設定してください

ツールリストが空

MCPクライアントを再起動してください

プロジェクトパスが無効

project.godot ファイルが存在することを確認してください

ランタイムツールが動作しない

runtime addonプラグインをインストールして有効にしてください

必要なツールが見つからない

tool.catalog を使用して関連ツールグループを検索・アクティブ化してください


関連リンク

ライセンス

MIT — 詳細は LICENSE を参照してください。

謝辞

  • オリジナルのMCPサーバーは Coding-Solo によるものです

  • Gearの拡張機能は HaD0Yun によって開発されました

  • プロジェクトの可視化機能は tomyud1/godot-mcp に触発されています

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