Product · v1.0.0 · live surface evidence 2026-06-18

MCP4Unreal

The professional MCP bridge for Unreal Editor. 1170 registered tools, 1162 callable public contracts across 146 domains, enforced security posture, packaged-plugin distribution, and a validated 1.0 release baseline.

Get a license Download

New to MCP?

What is MCP?

MCP (Model Context Protocol) is a standard way for AI systems to connect to real tools and applications. Instead of only generating text, an AI can use MCP to trigger actions in software like Unreal Engine — and MCP4Unreal is the bridge that makes that connection practical for Unreal Editor.

AI assistant MCP Unreal Engine

In simple terms

It lets an AI assistant operate Unreal through safe, specific actions.

MCP4Unreal is for developers, technical artists, and studios that want AI-assisted Unreal workflows without dumping the whole project into a chat window.

What it is

A bridge between an MCP-compatible AI client and Unreal Editor. The assistant can request editor actions through documented tool contracts instead of guessing from plain text.

Why it matters

Generic setups load too much Unreal context, cost more tokens, respond slower, and leave more room for the wrong tool. MCP4Unreal narrows each request to the domain that matters.

What you can ask for

Create or adjust actors, inspect Blueprints, work with materials, trigger Sequencer tasks, query diagnostics, or route other editor operations through validated commands.

Current release

v1.0.0

Initial 1.0 release for Unreal Engine 5.7 on Windows x64.

Full validation baseline

v1.0.0

Live /health evidence captured on 2026-06-18 from plugin 1.0.0 and engine 5.7.0.

Callable contracts

1162/1162

1162/1162 callable public non-alias contracts across 146 domains; 1170 registered tools including 8 compatibility aliases.

Default catalog

1158 tools / 145 domains

Default discovery excludes compatibility aliases and experimental-only entries unless requested.

1170

registered tools

146

public domains

1162/1162

direct + route coverage

certified

release baseline

Overview

An editor bridge, not a demo.

Verified surface

Public contracts are checked through direct and route validation. The current 1.0.0 evidence records 1162/1162 callable coverage with 1534 fixtures, 1078 typed input contracts, and 0 undeclared required parameters.

Transaction modes

Every response declares execution_scoped, handler_owned, or not_applicable — so you always know if a call can undo.

Issues & roadmap

Issues and the roadmap are public on GitHub. Feature suggestions and bug reports are welcome. The plugin is distributed as a packaged build — no source delivery.

How it works

Scoped context, not the whole editor.

A generic MCP setup loads broad Unreal context before the model can act. MCP4Unreal routes only the context a task needs, so far fewer tokens reach the model before execution.

Generic MCP

~65k

MCP4Unreal

~1.1k

~90% less token overhead estimated tokens per request

Broad context first

Water, Physics, UI, Audio, Animation, PCG, assets — loaded before execution. Higher cost, slower results, more room for the wrong tool.

Only what the task needs

A water request loads water context; a UI request loads UI context. Lower cost, faster execution, cleaner Unreal actions.

Estimated token impact per request, compared with broad tools/list loading. The scoped-context routing is validated; the exact reduction depends on the task and client.

Execution flow

From natural language to Unreal action.

MCP4Unreal sits between the MCP client and Unreal Editor. Its job is to keep the model focused before a request becomes an editor operation.

User request

A developer asks for a change in natural language from a terminal, chat client, or IDE.

MCP client

The client sends the request through the MCP protocol instead of treating Unreal as plain text context.

AI processing

The model interprets the instruction and selects the relevant Unreal intent.

MCP4Unreal routing

The bridge loads task-specific context and calls the validated Unreal tool contract.

Editor result

Unreal receives a cleaner, narrower action that can be audited and validated.

Generic MCP workflow

~65k

Broad Unreal context reaches the model before the action is selected.

> Loads Water, Physics, UI, Audio, Animation, PCG, assets, and more up front.
> Burns a large token budget before execution reaches the editor.
> Leaves more room for slow responses and wrong tool selection.

MCP4Unreal optimized workflow

~1.1k

Only the required Unreal context reaches the model before execution.

> Routes intent to a narrow domain such as water, UI, materials, Sequencer, or source control.
> Keeps the token budget small before the bridge calls Unreal APIs.
> Produces faster, cleaner, task-specific editor actions.

Clients

Built for real MCP clients.

Current claims are scoped to clients we have actually validated.

Claude

validated

Validated live against the running editor on 2026-06-18 over Streamable HTTP with custom headers.

Codex

validated

Streamable HTTP and local STDIO validated on 2026-04-28.

Any MCP client (HTTP/STDIO)

supported

Connects directly over Streamable HTTP with custom headers, or through the bundled STDIO bridge. No per-client gateway and no dotted-name rewriting.

Cursor

unsupported

Unsupported today: it filters standard dotted MCP tool names such as actors.spawn.

Coverage

What you get.

A verified surface across the entire editor.

domain

Actors / Levels / World Partition

Spawn, transform, stream, partition, query.

domain

Blueprints / UMG / Animation

Graph edits, widget trees, skeletal rigs.

domain

Materials / Textures / Material Graph

Parameter collections, master materials, MI.

domain

Sequencer / MRQ / Cinematics

Tracks, sections, render queue submissions.

domain

Niagara / Audio / Physics

Systems, emitters, cues, chaos simulations.

domain

Source Control / Build / Diagnostics

Git, Git LFS, cook, package, profile.