Godot MCP Pro

What youichi-uda/godot-mcp-pro MCP server does

The youichi-uda/godot-mcp-pro MCP server gives AI clients an interface to a Godot editor through a local MCP process. The repository itself contains the free Godot addon, while the Node.js MCP server is distributed in the paid package. The package is sold as a one-time purchase with lifetime updates, according to the README.

The server is intended for editor-aware development tasks. It can inspect project metadata and files, create and modify scenes, manipulate nodes and properties, work with GDScript, read editor output, simulate user input, and inspect or control a running game. Operations that use the editor API can work with the scene tree and Godot's UndoRedo system.

How it works

The architecture has three parts: an AI client communicates with the Node.js process using MCP over standard input and output; the Node.js process communicates with the Godot addon over WebSocket; and the addon performs operations inside the running editor. The default WebSocket port is 6505, and the configuration example passes that value through GODOT_MCP_PORT.

The Godot project must be open with the addon enabled before the MCP tools can interact with it. The README also describes a separate CLI that connects to the same plugin over WebSocket. That CLI is useful for clients with terminal access but no MCP support, and lets users discover command groups and options incrementally with --help.

Setup and configuration

First copy addons/godot_mcp/ into the Godot project's addons/ directory. Enable the plugin from Project Settings, under Plugins. The MCP server itself is only included in the full paid archive; a clone of the public repository may not contain the server/ directory.

After extracting the paid package, the documented build steps are to enter server/, run npm install, and then run npm run build. Configure an MCP client to execute the built server/build/index.js with Node. The example sets GODOT_MCP_PORT to 6505; its path is a placeholder that must be replaced with the extracted server's actual path.

The server can be started with the default full tool set or with --3d, --lite, or --minimal. The README recommends full mode for clients such as Cursor and Cline, lite mode for Windsurf, and minimal mode for OpenCode or local models with smaller context limits.

Tools and capabilities

The full package documents 175 tools, grouped broadly as follows:

• Project and filesystem inspection, project settings, and UID/path conversion
• Scene creation, opening, saving, deletion, instancing, and playback
• Node creation, deletion, duplication, reparenting, property updates, signals, groups, and selection
• Script listing, reading, creation, editing, attachment, and syntax validation
• Editor errors, screenshots, output logs, reload operations, and editor-script execution
• Keyboard, mouse, action, and recorded input simulation
• Runtime scene inspection, property changes, screenshots, frame capture, monitoring, and replay

Lite mode contains 84 tools covering project, scene, node, script, editor, input, runtime, and input-map operations. Minimal mode contains 35 essential tools. The README also lists a 103-tool 3D mode for clients with a 100-tool limit, although the exact 3D tool breakdown is not provided.

Limitations and notes

The public repository alone is not sufficient to run the MCP server: the paid package is required for the Node.js server and its build files. The Godot editor must be running with the plugin enabled, and the MCP connection depends on the local WebSocket link.

Client tool limits affect which mode is appropriate. Full mode is documented for Claude Code, Cline, Cursor, and other clients without a restrictive limit; Windsurf and similar clients should use lite mode. The CLI requires a built server and an available port in the 6510–6514 range, which differs from the MCP configuration's documented port 6505.

The material does not state a software license for the repository, and it does not document Claude Desktop compatibility.