Godot MCP Toolkit
An addon makes the Godot 4.2 and newer editor an MCP server with over 150 operations and a tool set that grows on request.
- 131 ★ on the repository
- Last commit
Extended access
Why this level
- The agent edits scenes, scripts and project settings and runs the game in your editor.
- The bridge is fetched from npm through `npx` on first connect.
Install
- Works in
Manual install
Godot Asset Store: Godot MCP Toolkit, Download, Install; затем Project Settings, Plugins, ActiveManually: download the archive from GitHub releases and extract into `addons/`. The Write .mcp.json menu item creates the client config.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent edits scenes, scripts and project settings and runs the game in your editor.
- The bridge is fetched from npm through `npx` on first connect.
This is third-party code. Review the repository files before installing.
What it does
Godot MCP Toolkit runs inside the editor and hands an agent scenes, scripts, nodes and game runs. The agent creates nodes, edits GDScript, paints TileMap cells, keys animation tracks and reads a live node during a playtest while you watch the editor. Operations are packed into up to 113 tools: an always-on core plus 28 on-demand groups, so the set starts at about 8,800 tokens. Your own GDScript or C# tools register through an extension API with hot reload. Traffic goes over WebSocket on `127.0.0.1` from port 6550, and the npm package `@npgamedev/godot-mcp-server` is the bridge.
Who it is for. Godot game developers who hand an agent work inside the open editor and want to see results immediately.
Good fit when
- A scene must be assembled from a description without using the inspector by hand.
- The agent must run the game and read node state during play.
- A C# and GDScript project needs its own tools for the agent.
- Context is limited and the tool list should grow gradually.
Not a fit when
- Godot is older than 4.2 or the project uses a mobile or web editor.
- Node.js 22 for the bridge is missing.
- A running editor window is unavailable, for example headless CI.
Example request
Create a level scene with a player and a tilemap, run the game and show the player's position after five seconds.MCP
- Transport
- stdio
- Authentication
- not required
Limitations
Requires Godot 4.2 or newer and Node.js 22 or newer, desktop only. Some operations are unavailable on older Godot versions. The editor must be open with the plugin enabled. This is an independent community project. Once a day the addon checks GitHub for updates; turn it off with `mcp_toolkit/updates/check_for_updates`. License: MIT per README, NOASSERTION on GitHub. The bridge launches through `npx` and downloads on first connect; pin the version for reproducible runs.
How to disable. Clear the Active checkbox for the plugin in Project Settings, Plugins, then delete `addons/godot_mcp_toolkit/` and the `godot-mcp-toolkit` entry in `.mcp.json`.
FAQ
How does the plugin write the client config?
Through Project, Tools, MCP Toolkit, Write .mcp.json. The file starts the bridge with `npx -y @npgamedev/godot-mcp-server`.
Why up to 113 tools but over 150 operations?
Related actions share one tool. The core is always on and 28 groups load on the agent's request.
What if `npx` fails on Windows?
Wrap the call as `cmd /c npx -y @npgamedev/godot-mcp-server` or update the client.
Does project data leave the machine?
No, apart from a daily update check, which carries no project data and can be turned off.
How do I pin the bridge version?
Add `@<version>` to the package name in `.mcp.json`. The plugin dock also has pin modes.
Discussion
No questions or reviews yet.
Related
MCP serversAn MCP server for Godot 4 that runs inside the editor: the agent edits scenes, nodes and scripts, runs the project and reads the debugger, no Node.js
An MCP server with 157 tools for Godot 4: the agent edits scenes and projects, runs the game, changes live nodes and writes GDScript and .NET scripts
MCP for the Godot editor: an agent edits scenes, runs the game, freezes time and verifies its own work by playtest
An MCP server and plugin for Godot 4.4+: the agent edits scenes and scripts in the editor, runs the game and reads errors
An MCP server for the Godot engine: launch the editor, run projects and edit scenes from an agent
Godot MCP Enhanced reads, edits, runs and verifies Godot 4.5 to 4.7 projects: scenes, scripts, UI and tests with path protection.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Godot MCP Toolkit (this card) | no | not required | 131 | |
| Godot MCP Full Control | no | not required | 513 | 157 tools in a single list; here a core plus 28 on-demand groups and an extension API in GDScript and C# |
| Godot AI | yes | API key | 3,509 | connects agents to a running editor; here the focus is a bounded context and custom tools |
README in short
The README walks through addon install, enabling, writing `.mcp.json` and a first prompt. Architecture and validation sit in separate documents.