GDMaestro
An AI-native MCP server that drives the Godot engine — create and edit projects, scenes, scripts, and settings headlessly; run the game; and inspect or manipulate the live scene tree, all through standard Model Context Protocol tools, resources, and prompts.
What you get
🧩 Full tool surface
52 typed godot_<op> tools with strict JSON schemas and MCP annotations, plus 18 grouped <domain>_manage tools covering all 157 operations, plus a godot_catalog browser.
📡 Live project resources
godot://project/* URIs expose settings, the file tree, the main scene, and any project file — readable without a tool call while the game runs.
🧭 Guided prompts
Five reusable workflows — create-godot-project, setup-input-action, create-character-scene, debug-running-game, validate-and-fix-scripts — script the right tool sequence for you.
⌨️ Argument completion
completion/complete fills in prompt arguments and resource URIs, including project file paths, cutting invalid calls and round-trips.
⛔ Cancellation
notifications/cancelled aborts a hung live-game command or a long headless validation instead of blocking the session for the full timeout.
🪶 Zero dependencies
The protocol layer and all Godot integration are implemented against the Go standard library only — nothing to audit, nothing to keep patched.
What sets it apart
GDMaestro doesn't just let an agent edit a game — it lets the agent play the game it's building. It boots the real engine, then drives it: forcing any scenario, advancing time frame by frame, asserting what should be true, and reading the results straight back — all inside the running game, in a single loop.
That turns QA into an agent-owned loop, not a human chore: the agent catches its own regressions before handing the build back, so the "here, run it and tell me what happens" back-and-forth disappears. You stay on the design decisions — the loop that verifies them runs itself.
Who it's for
Teams and solo developers using an AI coding assistant to build in Godot — anyone who wants their assistant to read and edit real project files, drive the running game, and follow consistent multi-tool workflows instead of improvising shell commands against the editor.
How it compares
Sources: checked directly against each project's server source/READMEs (2025-08). Only Unity MCP ships a comparable resources surface; no other surveyed engine MCP server ships prompts, completion, or cancellation.
| Capability | GDMaestro | Unity MCP | Unreal MCP | Godot MCP (TS, origin) |
|---|---|---|---|---|
| Tools | 71 (52 typed + 18 grouped + catalog) | ~48 grouped | ~30–40 | 19 grouped / 157 ops |
| Resources | ✅ godot://project/* | ✅ 25 editor-state URIs | ❌ | ❌ |
| Prompts | ✅ 5 guided workflows | ❌ | ⚠️ 1 doc-string | ❌ |
| Completion | ✅ args + resource URIs | ❌ | ❌ | ❌ |
| Cancellation | ✅ notifications/cancelled | ❌ | ❌ | ❌ |
| Conformance suite | ✅ validated | n/a | n/a | tools-only |
FAQ
What is GDMaestro?
GDMaestro is an AI-native Model Context Protocol (MCP) server that drives the Godot game engine. It exposes 71 tools covering 157 operations, live project resources, and guided prompts, so an AI agent can create and edit Godot projects, scenes, scripts, and settings, run the game, and inspect the live scene tree.
What MCP server works with the Godot engine?
GDMaestro. It is a purpose-built, zero-dependency MCP server for Godot, compatible with any MCP client such as Claude, Cursor, and other AI coding agents.
Is GDMaestro free or open source?
No. GDMaestro is proprietary, commercial software distributed under a paid license. It is not open source.
Pricing & licensing
- Full 71-tool MCP server binary
- All 157 operations, resources, prompts, completion, cancellation
- Updates within your licensed major version
GDMaestro is proprietary, commercial software — all rights reserved. It is not open source. The license grants a limited, non-exclusive, non-transferable right to use the compiled binary for your own internal purposes; it does not permit redistribution, reverse engineering, or building a competing product. Third-party components incorporated into the binary remain under their own upstream licenses.
This summary is for convenience only — the full LICENSE governs, and its terms (like any commercial license) should be reviewed by your own counsel before you rely on them.