# Godot MCP Pro: 175 MCP Tools for Godot 4, With the Server Behind a Paywall

> Godot MCP Pro is a paid MCP server plus free Godot editor addon that lets AI assistants drive a running Godot 4 editor over WebSocket. The public repository ships only the addon; the Node.js server that clients actually connect to comes with the one-time purchase.

**youichi-uda/godot-mcp-pro** — 162 MCP tools for AI-powered Godot 4 development. Scene, animation, 3D, physics, particles, audio, shader, input simulation, runtime analysis, navigation, testing & more. $15 one-time.

- Repository: https://github.com/youichi-uda/godot-mcp-pro
- Website: https://godot-mcp.abyo.net/
- Stars: 615 · Forks: 77
- Language: GDScript
- License: NOASSERTION
- Published: 2026-09-10 · Updated: 2026-09-10 · Language: en
- Canonical page: https://hysenlabs.com/projects/youichi-uda-godot-mcp-pro

## The gap Godot MCP Pro fills between an AI chat window and a running editor

An AI assistant writing GDScript for you still cannot see the scene tree, cannot read the editor's error panel, and cannot press play. Godot MCP Pro exists to close that gap by exposing the Godot editor's own API to a model through the Model Context Protocol. The README describes it as a premium MCP server for AI-powered Godot game development, and the repository topics list godot4, mcp, gdscript and game-development.

The intended user is a Godot 4 developer who already works inside an MCP-capable client such as Claude Code, Cursor, Cline or Windsurf. The README's compatibility table names those clients directly and pairs each with a recommended mode. This is not a library you import into a game. It is an editor-side tool, so it does nothing for a shipped build, a headless CI job, or anyone working in Godot 3.

## How the WebSocket bridge and four tool modes actually work

The architecture is a three-part chain. The README shows it as AI Assistant to Node.js Server over stdio/MCP, then Node.js Server to Godot Editor Plugin over WebSocket on port 6505. Because the transport is a socket rather than file polling, the README claims instant feedback and describes the protocol as JSON-RPC 2.0 with error codes and suggestions.

The editor half is a Godot addon that reaches into the editor API, the UndoRedo system and the scene tree. That is why node deletion is documented as supporting undo and why tools such as get_editor_selection and select_nodes can read and change what is selected in the editor. The server half is a Node.js process that translates MCP calls into WebSocket messages.

Tool count is the design constraint that shapes everything else. The full mode exposes 175 tools, which the README says suits Claude Code, Cline, VS Code Copilot and Cursor. Three reduced modes exist for clients with lower ceilings: --3d with 103 tools, --lite with 84, and --minimal with 35. The README's own reasoning is that OpenCode and local models degrade past roughly 40 tools, so minimal mode exists for them. That is a real admission that the full tool surface is too large for some clients, not a marketing footnote.

## Installing Godot MCP Pro: addon first, then the paid server

The public repository contains the addon only. The README states this plainly: if you cloned the repo and do not see a server folder, that is expected. The server directory with pre-built JavaScript, INSTALL.md and AI-client instructions ships in the paid zip from Buy Me a Coffee or itch.io.

Start by copying the addon into your project and enabling it. The README gives the path as addons/godot_mcp/ and the toggle under Project, then Project Settings, then Plugins.

```bash
cd server
npm install
npm run build
```

After the build, register the server with your MCP client. The README's Claude Code example points at the built index.js and sets the port through an environment variable.

```json
{
  "mcpServers": {
    "godot-mcp-pro": {
      "command": "node",
      "args": ["/path/to/server/build/index.js"],
      "env": {
        "GODOT_MCP_PORT": "6505"
      }
    }
  }
}
```

To cap the tool surface, append a mode flag to args. The README shows --lite and says to replace it with --minimal for the smallest footprint.

```json
{
  "mcpServers": {
    "godot-mcp-pro": {
      "command": "node",
      "args": ["/path/to/server/build/index.js", "--lite"]
    }
  }
}
```

Finally, open your Godot project with the plugin enabled and talk to the editor through your client. There is also a CLI path for clients without MCP support. The README shows progressive discovery through help flags and a few direct commands.

```bash
node /path/to/server/build/cli.js --help
node /path/to/server/build/cli.js node add --help
node /path/to/server/build/cli.js project info
node /path/to/server/build/cli.js node add --type CharacterBody3D --name Player
```

The CLI needs the editor running with the plugin enabled, the server already built, and a free port in the 6510-6514 range, which is separate from the 6505 port used by the MCP transport.

## Where Godot MCP Pro stops being the right tool

The paid server is the first limitation, and it is structural. The public repository is not a working installation. Anyone who clones it, copies the addon, and expects an MCP endpoint will find nothing listening, because the Node.js half is not there. That is a deliberate split, but it means the free repository cannot be evaluated end to end on its own.

The second limitation is client tool limits. The README's own table shows that Windsurf, JetBrains Junie and Gemini CLI are pushed to Lite because of roughly 100-tool ceilings, and that OpenCode and local models should use Minimal or the CLI. If your client cannot run a local Node process at all, none of the MCP modes work and you are left with the CLI through a terminal tool.

Third, this is editor-bound. Everything runs against a live Godot editor session over WebSocket. The README does not document a headless or CI mode, so automated build pipelines are outside what it describes. Fourth, the README does not document rollback for editor operations beyond the note that node deletion supports undo, so anyone planning bulk scene edits should treat undo coverage as unverified for the rest of the tool set.

## Godot MCP Pro against a plain editor-plugin or file-based MCP setup

The obvious alternative is a lighter MCP integration that reads and writes .tscn and .gd files on disk without a socket to the editor. The difference is not cosmetic. A file-based approach can inspect scene files with get_scene_file_content and edit scripts, but it cannot read the live scene tree, cannot read the editor's error output, cannot simulate input, and cannot press play. Godot MCP Pro's runtime and input tools depend on the editor actually running, which is exactly what a file-only integration gives up.

The second alternative is the CLI mode that ships with the same paid package. It is not a competitor so much as a different consumption path: instead of loading tool definitions into the model's context, the model discovers capabilities through --help and invokes commands directly. The README frames this as working with any client that has terminal access, regardless of tool count limits. For a client capped at 40 tools, that is the difference between usable and unusable, at the cost of the model having to explore the command tree itself.

## Maintenance, licence and what a one-time purchase commits you to

The last push to the repository was on 2026-08-01, and the most recent release, v1.16.0, is dated the same day. Earlier releases are v1.15.1 on 2026-07-19 and v1.15.0 on 2026-06-24, which the release list labels as editor selection tools plus legacy TileMap support. The repository is not archived. The cadence across those three releases is roughly monthly.

Upgrade cost is mostly your own time. The addon is a folder you copy into addons/, so updating means replacing it. The server is pre-built JavaScript in the paid zip, so a server update means re-downloading the package and repeating the build step. The README states that the one-time purchase includes lifetime updates, which removes recurring licence fees but leaves you responsible for re-extracting and rebuilding.

On licensing, the repository has a LICENSE file at the top level, but the metadata reports the licence as NOASSERTION, meaning GitHub could not map it to a known identifier. The README does not spell out terms for the addon or the paid server in the text available. Read the LICENSE file and the purchase page before you ship anything that depends on it; this is a commercial product with a free component, and the two may not carry the same terms.

## Conclusion

Adopt Godot MCP Pro if you already drive Godot 4 through an AI client that can run a local Node process and you are willing to pay once for the server. Skip it if you need a permissively licensed server you can vendor, or if your client caps tools below 35 and cannot use the CLI. Before buying, confirm the tool count your client allows, decide between Full, --3d, --lite and --minimal, and check the LICENSE file in the repository, which GitHub reports as NOASSERTION rather than a named licence.

## FAQ

### What is MCP Godot?

MCP here refers to the Model Context Protocol, and Godot MCP Pro is an MCP server that connects AI assistants to a running Godot 4 editor. The README describes it as a premium MCP server for AI-powered Godot game development, with the assistant talking to a Node.js server over stdio and that server talking to the editor plugin over WebSocket on port 6505.

### Can Claude Code be used with Godot MCP Pro?

Yes. The README's compatibility table lists Claude Code with the Full mode of 175 tools and notes deferred tool loading, and its configuration example is written for Claude Code's .mcp.json file. It also states that the server directory is only included in the paid package, so the server must be obtained before that configuration will work.

### How do you install Godot MCP Pro?

Copy the addons/godot_mcp/ folder into your Godot project's addons/ directory and enable the plugin under Project Settings, then Plugins. From the paid package, run npm install and npm run build inside the server directory, then register the built index.js with your MCP client and set GODOT_MCP_PORT to 6505.

## Sources

- [Issues](https://github.com/youichi-uda/godot-mcp-pro/issues)
- [Project website](https://godot-mcp.abyo.net/)
- [README](https://github.com/youichi-uda/godot-mcp-pro/blob/master/README.md)
- [Releases](https://github.com/youichi-uda/godot-mcp-pro/releases)
- [youichi-uda/godot-mcp-pro on GitHub](https://github.com/youichi-uda/godot-mcp-pro)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/youichi-uda-godot-mcp-pro