Quick Information

No ratings yet

playlogic

Godot MCP/CLI

Godot MCP/CLI drives the Godot editor you already have open. The addon hosts a small server inside the running editor, and a command line tool or an AI agent connects to it to build scenes, write GDScript and C#, place geometry, run the game, and read state back out of it.This is not Godot's own batch command line. Running "godot --headless" or "--export-release" starts a fresh engine process with no open scene, no selection, and no undo history. This connects to the live editor session instead, so a command can act on the scene you are looking at, and every editor mutation goes through UndoRedo where Ctrl+Z reverses it.There are 312 commands across 49 groups. They cover scenes and nodes, GDScript and C# authoring, spatial placement with real world bounds and raycast seating, materials, tilemaps, animation and animation trees, physics, navigation, audio, UI, shaders, procedural generation, and project settings. A second family of commands reaches into the running game to inspect live node state, evaluate expressions, inject input, wait for signals, and capture frames, which is the part a text editor cannot do on its own.Discovery is built in. The engine group reads ClassDB from the running build, so an agent can confirm that a class, property, or method actually exists in your version of Godot before writing code against it. Newer engine features stay reachable without waiting for an addon update, because node properties and script execution reflect whatever the running binary exposes.Two ways to connect. Any MCP client that speaks streamable HTTP can talk to the editor directly at POST 127.0.0.1:9100/mcp with no external process running. Everything else uses the godot-mcp command line tool, which doubles as a stdio MCP server and is self describing at the terminal, so shell driven agents need no tool schemas at all. Both paths dispatch through the same command router with the same safety guards.Safety. Both servers bind 127.0.0.1 only and never 0.0.0.0. The HTTP endpoint also validates the Origin header, so a page open in a browser cannot reach the editor. Code execution paths are audited, direct editor write APIs are refused unless explicitly allowed, and file writes are confined to the project.Requires Godot 4.7 or newer. This entry contains the editor addon, which is all an HTTP capable MCP client needs. The command line tool, prebuilt for Windows, Linux, and macOS, and an agent skill that teaches the discover then drive workflow, are separate downloads from the GitHub releases page.

Supported Engine Version

4.7

Version String

0.8.0

Support Level

community

Modified Date

2 days ago

Git URL

Link to Git URL

Issue URL

Link to Issues URL

Download ZIP

Godot MCP/CLI

Name: Godot MCP/CLI
Author: playlogic

Drive the Godot editor you already have open, from an AI agent or from a terminal. The addon hosts two local servers inside the running editor:

a WebSocket server on 127.0.0.1, first free port in 9080 to 9095, which the godot-mcp command line tool connects to;
a streamable-HTTP MCP endpoint at POST /mcp on 127.0.0.1, first free port in 9100 to 9115, which an HTTP-capable MCP client connects to directly with no extra process running.

Both dispatch the same 316 commands across 49 groups: scenes, nodes, GDScript and C#, spatial placement, materials, tilemaps, animation, physics, procedural generation, and live inspection of the running game. Every editor mutation goes through UndoRedo, so Ctrl+Z reverses it.

Setup

Copy addons/godot_mcp/ into your project.
Enable Godot MCP/CLI under Project, then Project Settings, then Plugins.
The Output panel prints the bound port, for example [MCP] Server listening on ws://127.0.0.1:9080.

Enabling the plugin also installs two autoloads, MCPGameInspector and MCPGameInput, which the runtime and input command groups need to reach a running game. Disabling the plugin removes them again.

The bound ports are written to <project>/.godot/godot-mcp.json, so a client can find the editor without configuration. Pin them with the godot_mcp/network/port and godot_mcp/network/http_port project settings, or the GODOT_MCP_PORT and GODOT_MCP_HTTP_PORT environment variables.

Requirements

Godot 4.7 or newer, run against 4.7.1-rc, 4.7.2-rc, and a 4.8-dev build from master. The addon alone is enough for an HTTP-capable MCP client. The command line tool and the agent skill are separate downloads from the repository releases.

Security

Both servers bind 127.0.0.1 only, never 0.0.0.0. The HTTP endpoint also validates the Origin header, so a page open in a browser cannot reach it. The ports carry no authentication by design, which is what makes zero-configuration discovery work, so treat a running editor as reachable by other processes on the same machine and quit it when you are not driving it.

License

MIT. See the LICENSE file beside this one.

Godot MCP/CLI drives the Godot editor you already have open. The addon hosts a small server inside the running editor, and a command line tool or an AI agent connects to it to build scenes, write GDScript and C#, place geometry, run the game, and read state back out of it. This is not Godot's own batch command line. Running "godot --headless" or "--export-release" starts a fresh engine process with no open scene, no selection, and no undo history. This connects to the live editor session instead, so a command can act on the scene you are looking at, and every editor mutation goes through UndoRedo where Ctrl+Z reverses it. There are 312 commands across 49 groups. They cover scenes and nodes, GDScript and C# authoring, spatial placement with real world bounds and raycast seating, materials, tilemaps, animation and animation trees, physics, navigation, audio, UI, shaders, procedural generation, and project settings. A second family of commands reaches into the running game to inspect live node state, evaluate expressions, inject input, wait for signals, and capture frames, which is the part a text editor cannot do on its own. Discovery is built in. The engine group reads ClassDB from the running build, so an agent can confirm that a class, property, or method actually exists in your version of Godot before writing code against it. Newer engine features stay reachable without waiting for an addon update, because node properties and script execution reflect whatever the running binary exposes. Two ways to connect. Any MCP client that speaks streamable HTTP can talk to the editor directly at POST 127.0.0.1:9100/mcp with no external process running. Everything else uses the godot-mcp command line tool, which doubles as a stdio MCP server and is self describing at the terminal, so shell driven agents need no tool schemas at all. Both paths dispatch through the same command router with the same safety guards. Safety. Both servers bind 127.0.0.1 only and never 0.0.0.0. The HTTP endpoint also validates the Origin header, so a page open in a browser cannot reach the editor. Code execution paths are audited, direct editor write APIs are refused unless explicitly allowed, and file writes are confined to the project. Requires Godot 4.7 or newer. This entry contains the editor addon, which is all an HTTP capable MCP client needs. The command line tool, prebuilt for Windows, Linux, and macOS, and an agent skill that teaches the discover then drive workflow, are separate downloads from the GitHub releases page.

Reviews

0 total reviews

No ratings yet

Your Rating

This addon is good

This addon is not good

Headline must be at least 3 characters but not more than 50

Headline (optional)

Review must be at least 5 characters but not more than 500

Review (optional)

Please sign in to add a review

Godot MCP/CLI

Quick Information

Godot MCP/CLI

Setup

Requirements

Security

License

Reviews

Your Rating

Quick Information

Open Source

Plug and Play

Community Driven

Godot MCP/CLI

Quick Information

Asset Description

Godot MCP/CLI

Setup

Requirements

Security

License

Reviews

Your Rating

Quick Information

Related Assets

Related Guides

Open Source

Plug and Play

Community Driven