npgamedev/godot-mcp-server

このページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。原文を見る

15 stars 8 forks 品質 81 トレンド 41NOASSERTION

The npm bridge connecting AI coding assistants to the Godot 4.2+ editor over the Model Context Protocol. Runs locally as a stdio-to-WebSocket bridge.

概要

The npm bridge that connects AI coding assistants to the Godot 4.2+ editor over the Model Context Protocol. Your assistant can create scenes, edit scripts, inspect nodes, run playtests, and read the results back, directly inside the editor while you watch. It pairs with the Godot MCP Toolkit editor plugin, which hosts the WebSocket servers this bridge talks to. Runs fully locally. No telemetry, no cloud services, no account. Nothing leaves your machine. This is an independent community project, not affiliated with or endorsed by the Godot Foundation or Anthropic. Desktop only: Windows, macOS, and Linux. Requires Node.js 22 or newer. 📐 covers how the server is built: the entrypoint and startup, the WebSocket bridge, the catalogue and dispatch pipeline, discover_tools, the GDScript LSP client, and the registry consumer. Also rendered at npgamedev.github.io/godot-mcp-server/architecture. Built to fit your workflow, not the other way around. The number that says the most is .

README

以下は原文 README の抜粋です。原文を見る。

Godot MCP Server

Runs fully locally. No telemetry, no cloud services, no account. Nothing leaves your machine.

This is an independent community project, not affiliated with or endorsed by the Godot Foundation or Anthropic.

Desktop only: Windows, macOS, and Linux. Requires Node.js 22 or newer.

📐 Architecture → covers how the server is built: the entrypoint and startup, the WebSocket bridge, the catalogue and dispatch pipeline, discover_tools, the GDScript LSP client, and the registry consumer. Also rendered at npgamedev.github.io/godot-mcp-server/architecture.

Why this one?

Built to fit your workflow, not the other way around.

The number that says the most is 150+ operations. That is the real work on offer: create a node, paint a tilemap cell, key an animation track, read a live node mid-playtest, and roughly a hundred and fifty more. Those operations are packaged into up to 113 tools (an always-on core plus 28 on-demand groups), because a tool is a slot in your client’s tool budget and an operation is a thing you can actually do. Related actions sit behind one tool, which keeps the list short while the operation count tells the honest story of breadth. Some operations are version-gated, so older Godot versions (down to 4.2) expose fewer. “Up to” is literal.

Two things drive the design, and they carry equal weight:

GitHub で README 全文を見る

インストール

npx -y @npgamedev/godot-mcp-server

MCP 初心者？mcpskill.org のガイドから始めましょう →

設定

{
  "mcpServers": {
    "godot-mcp-toolkit": {
      "command": "npx",
      "args": ["-y", "@npgamedev/godot-mcp-server"]
    }
  }
}