Exaro StudioUE 5.8's built-in MCP: setup, limits, and guardrails.
Unreal Engine 5.8 ships an experimental MCP server, so any MCP-aware assistant can drive the editor. That's genuinely useful — and Epic's own docs are clear that it's early. Here's how to turn it on, what it does and doesn't cover, and how Exaro Studio adds the layer it leaves out: previews, approvals, and undo.
Setting it up (2 minutes)
- Enable the Unreal MCP plugin (Edit → Plugins). It pulls in the Toolset Registry dependency automatically.
- Enable the toolsets you want — the server starts empty; without a toolset registry enabled it connects but exposes nothing. Core toolsets: SceneTools, ActorTools, MaterialInstanceTools, ObjectTools.
- Optionally turn on auto-start in Editor Preferences, then generate a client config from the console:
ModelContextProtocol.GenerateClientConfig ClaudeCode - Launch your agent from the project root. The server listens at
127.0.0.1:8000/mcp.
Worth knowing before you rely on it: the feature is marked Experimental, tool calls execute serially on the game thread, and Epic's docs note the APIs and data formats may change. See Epic's official documentation.
The part nobody mentions: it's fire-and-forget
The built-in server executes whatever a connected agent asks, immediately. No preview of what's about to change, no approval step, no transaction wrapping. On a throwaway project that's fine. On the project you've been building for a year, an agent misunderstanding one instruction is a bad afternoon. That safety layer is the product gap Exaro Studio was built around — before 5.8 existed.
| Capability | UE 5.8 built-in (Experimental) | Exaro Studio |
|---|---|---|
| MCP transport (HTTP + SSE, loopback) | ✓Built in, port 8000 | ✓Built in, port 8765 — both run side by side |
| Primitive editor tools (spawn actor, materials, objects) | ✓SceneTools, ActorTools, MaterialInstanceTools, ObjectTools | ✓287 tools across Blueprints, C++, animation, AI, UI, multiplayer |
| Composite tools that finish a whole job | —Not included | ✓Character with camera/movement/input bound, pause & settings menus wired, inventory + save that survives level travel |
| Preview before anything changes | —Not included | ✓Every mutation builds a human-readable summary + diff first |
| Approval queue (approve / reject / allowlist) | —Not included | ✓In-editor panel; nothing mutates until you say so |
| Undo integration | —Not included | ✓Reversible operations wrapped in a single Ctrl+Z transaction |
| In-editor chat client | —Not included | ✓Dockable panel — BYO API keys or your existing Claude/Gemini/Codex CLI |
| Cost controls | —Not included | ✓Billed-vs-free route shown before you click; session spend cap |
| Engine versions | ✓5.8 only (Experimental) | ✓UE 5.7 today; 5.8 support in progress — runs alongside the built-in server |
Built-in capabilities per Epic's UE 5.8 documentation as of July 2026; Experimental features change between releases.
Epic gave agents hands. Exaro Studio gives them judgment.
The built-in server proves the workflow: agents can drive the editor. Exaro Studio is what makes that workflow safe enough for a real project — every mutation previewed and approved before it runs, reversible operations undoable in one Ctrl+Z — and productive enough to finish things, with composite tools that deliver a wired character, a working pause menu, or a save system instead of a pile of primitives. Both servers run side by side; you don't have to choose.