Godot MCP Toolkit

A community editor plugin (NPGameDev, MIT, v1.0.0, Godot 4.2+, listed on the Godot Asset Library 2026-07-27) that connects an AI coding assistant to the Godot editor over the Model Context Protocol. The agent can create scenes, edit nodes and scripts, query ClassDB, and drive playtests from plain-language instructions.

Godot’s answer to the AI front arrives the way its vision statement says things should: not in the engine, but as a plugin from the community.

What it exposes

112 built-in MCP tools, 150+ operations, covering scenes, nodes, scripts, resources, editor state, ClassDB and playtest control. Two design choices are worth recording because they are the same problems Unity and Unreal hit:

• Progressive tool disclosure. The startup tool surface is deliberately small and expands on demand through a discover_tools call, explicitly to keep the agent’s context budget low. That’s the same progressive-disclosure discipline ../agentic-tooling-wiki tracks for agent skills, applied to an engine’s API surface.
• An extension API. You write your own MCP tools in GDScript; they hot-reload and the agent sees them exactly like built-ins (C#/.NET projects extend the same way). Functionally identical to Unity’s [CliCommand] attribute making the editor self-describing — different mechanism, same requirement that an agent discover what it can call at runtime.

Security posture

The editor server binds 127.0.0.1 only, every client presents a session token as its first message, filesystem tools are boundary-checked (res:// for project files, user:// for saves, with path traversal and absolute OS paths rejected), and an optional read-only mode (GODOT_MCP_READ_ONLY=1) hides every mutating tool. That posture matches Unity’s token-gated, localhost-only, off-by-default eval almost line for line — two unrelated projects reaching the same conclusion about what handing an agent write access to a live editor requires.

Practical shape

Desktop only (Windows, macOS, Linux). Needs a companion Node 22+ server bridge (@npgamedev/godot-mcp-server) alongside the plugin. Works with any MCP-compatible assistant, tested primarily with Claude Code. The listing states plainly that it is an independent community add-on, not affiliated with or endorsed by the Godot Foundation — which, given the Foundation’s stance on AI, is a more loaded disclaimer than the usual trademark boilerplate.

Tier

T3 — an Asset Library listing plus the author’s own feature description, from a v1.0.0 release by a solo developer with a rating of 0 (no community reviews yet). Every capability claim here is self-reported and nothing has been exercised. The tool counts and the security design are what the author says they are.

Related

engine-agent-surface · godot-engine · godot-contribution-policy-2026 · godot-vision-statement · unity-cli · unreal-engine-5-8 · godot-best-plugins-2025 · synthesis