What an MCP server for Unreal does

MCP, the Model Context Protocol, is how AI apps call tools. An MCP server for Unreal Engine gives an assistant tools that act on your open editor: create a Blueprint, wire its nodes and compile it, place actors, build materials, sequences and widgets.

The MifBridge server talks to the Unreal plugin over a local HTTP API, and to Blender through the free MifBlender add-on. Your client connects to one server. How the MCP server fits together

The numbers, and where they come from

535 typed Unreal Engine endpoints, every one listed in the API reference.
782 MCP tools in all, Blender included.
Unreal Engine 5.3 to 5.8, each swept live on a stock editor (5.3.2, 5.4.4, 5.5.4, 5.6.1, 5.7.4, 5.8.2): 322 to 333 test suites per version. The results for each version are on Engine support.
479 test suites in version 1.1.0.

The verification record explains how each number is counted.

It starts at Unreal Engine 5.3

Epic's own Unreal MCP is an experimental feature that arrived with Unreal Engine 5.8. MifBridge runs on every version from 5.3 to 5.8, so a project that cannot move to the newest engine can still work with an AI assistant.

It also works on cooked projects, games shipped as paks without their editor data. When something is cooked, the answer says so and names what can still be done. Cooked projects

Every change is read back

A write returns what the editor holds afterwards, read from the asset or actor. When a Blueprint fails to compile, the assistant is told which node and which pin caused it.

Every call is written to a journal before it runs, so if the editor ever crashes, the journal names the call that was running. The Unreal plugin

You decide what it may change

Write modes. The default, scratch, lets the assistant read and edit but refuses saves, Play In Editor, cooks and console commands. full allows everything.
A person sets the mode, in the editor. It is not an endpoint, a console variable or a command, so the assistant has no way to raise it.
Deleting or renaming needs an explicit confirm.
Ctrl+Z undoes transacted edits. Saves, cooks, Play In Editor, compiles and console commands are not transactions, which is one reason they are gated.
It only listens on your own machine, at 127.0.0.1, and every request carries a token.

Safety and write modes

Set it up with Claude Code

In the MifBridge panel, SETUP ▸ Set up Claude Code installs the server's dependencies and registers it with your editor's port and token. Any other MCP client can use the same server through a .mcp.json entry.

The server loads a few tools at first and finds the rest when they are needed, so the assistant does not read hundreds of tool descriptions on every request. Tool packs

Requirements: Windows 64-bit, Unreal Engine 5.3 to 5.8, and Python 3.10 or newer for the MCP server. Installation

Blender comes with it

The same server drives Blender through MifBlender, a free add-on, so an assistant can model in Blender and bring the result into Unreal in the same session. Blender MCP with MifBlender

What it has built

Every clip on the showcase was built in Unreal Engine or Blender by typed MifBridge calls, and each one says how many calls built it.

Questions

Is MifBridge an MCP server? Yes. It is an Unreal Engine plugin with an MCP server for Claude Code and other MCP clients, and it also serves a plain local HTTP API.

Does it generate 3D models or textures? The Unreal side does not: the assistant chooses editor commands, and Unreal builds every asset from their parameters. One optional Blender path makes 3D models from text or images through a ComfyUI install you run yourself. Where the line is

Which AI clients work? Any MCP client. Setup is one button for Claude Code; other clients use the .mcp.json entry in the docs.

What does it cost? A one-time payment, with Personal and Professional licenses, on the store or on Fab. More answers are in the FAQ.

An MCP server for Unreal Engine that checks its own work.