MifBridge

Lets Claude or any MCP client work inside Unreal Engine 5.3 to 5.8 and Blender 3.6 to 5.2, and reads the editor back after every change.

View on mifshowcase.storeTry this MCPSponsored

Documentation

VERSION 1.0.0 • UE 5.3 TO 5.8 • BLENDER 3.6 TO 5.2

AI for Unreal and Blender.

Every change is checked.

MifBridge lets Claude and other AI assistants work inside Unreal Engine and Blender. After every change, it looks at the editor to confirm the change really happened, and tells the AI exactly what it found.

Get on Fab · Buy here · Read the docs

See how it is tested →

Behind this page: all 161 showcase videos, made with 332,023 commands

BY THE NUMBERS COUNTED FROM THE CODE · 2026-09-17

  • 458 Unreal Engine commands (each one registered in the plugin's code)
  • 189 Blender commands (each one registered in the add-on's code)
  • 669 MCP tools (the commands as Claude and other AI apps see them)
  • 346 automated tests (test scripts in the repository)
  • 6 Unreal versions tested (5.3 to 5.8, none failed, 2026-09-16)

HOW IT WORKS

It checks the editor

after every change.

When the AI asks for a change, MifBridge makes it, then looks at the editor to see what actually happened and reports that, including anything that came out different. When the AI asks for something it is not allowed to do, MifBridge refuses and says why. These are real refusals from recorded sessions.

  1. set_cvar 2026-09-13 16:52:12 UTC · UE 5.7

    REFUSED no console variable named 'mif.BridgeWriteMode'

    The AI tried to raise its own permission level through a console variable. There is no such switch: only a person can change the level, in the MifBridge panel or when starting the editor.

  2. import_asset 2026-09-13 16:52:11 UTC · UE 5.7

    BLOCKED 'import_asset' is refused: the MifBridge safety gate is in 'scratch' mode. This endpoint either persists to disk, takes the editor loop, or executes outside the

    Importing writes new files to disk, which the current level, scratch, does not allow. The rest of the message tells a person how to allow it.

  3. set_render_settings colorDepth=32, fileFormat=PNG 2026-09-21 15:29:18 UTC · Blender 5.2.1 LTS

    REFUSED colorDepth '32' is not one the PNG format accepts: bpy_struct: item.attr = val: enum "32" not found in ('8', '16'). The enum's own item list reports 8, 10, 1...

    PNG images cannot be 32-bit. The reply names the bad value and the values that work, so the AI can fix its next try.

Copied word for word from the recorded sessions the panel above replays. Each message is its first line, shortened where the panel shortens it.

WHY IT’S CALLED MIFBRIDGE

The bridge of a ship.

A ship’s bridge is where the crew sees what is really going on and steers from. MifBridge does that job for an AI working in Unreal Engine or Blender.

  1. THE PROGRAMS

    Unreal and Blender are huge

    They can do almost anything, and they do exactly what they are told, mistakes included.

  2. THE AI

    An AI cannot see your screen

    It has read every manual, but it can only send commands and read the replies. It knows only what the replies tell it.

  3. MIFBRIDGE

    MifBridge tells it what really happened

    Every reply is read from the editor itself. Each command does one clear thing, every command is logged, and anything you have not allowed is refused.

Connecting an AI to Unreal is the easy part. The hard part is making sure it is told the truth, so every success report comes with what the editor actually shows.

WHAT YOU GET

What it does for you.

Four things that keep an AI from quietly breaking your project.

01

It checks every change

After each change, MifBridge reads the result back from the editor and reports exactly what it finds, including anything that came out different.

02

It rejects bad commands

A misspelled or impossible setting is refused with the values that work and the most likely fix, so the AI can correct itself.

03

You decide what it may do

Three levels: read (look only), scratch (it can make changes but cannot save them or run risky commands) and full. Only a person can change the level, in the editor.

04

Unreal and Blender, one setup

The MifBridge plugin works in Unreal Engine and the free MifBlender add-on works in Blender. The same MCP server drives both.

IN THE EDITOR

Real work, built this way.

See the showcase →

[The oil rig part-way through assembling itself in Blender

BLENDER

Built one part at a time, then checked.

MifBlender built the rig in the order an engineer would, then checked the scene it left behind.

](https://mifshowcase.store/showcase) · [The Small Oil Rig FPS Map on open sea

UNREAL ENGINE

A whole game level, built through MifBridge.

Geometry, materials, collision, lighting and navigation. The finished level is the proof.

](https://mifshowcase.store/oilrig)

Unreal Engine environment created with MifBridge

UNREAL ENGINE

Change a project without guesswork.

Assets, levels, Blueprints, materials and sequences each have their own commands, and each command reports exactly what it changed.

Blender scene created with MifBlender

BLENDER

Blender works the same way.

Modeling, rigging, lighting, nodes, physics and rendering, each with its own commands.

WHAT IT COVERS

What it can do in each program.

Browse every command →

UNREAL ENGINE 458 commands

Blueprints · Materials · Landscape · Niagara · UMG · Sequencer · Rigging · Animation · PCG · DataTables · Collections · GAS · World Partition · Navigation · Water · Physics · Cooked projects

BLENDER 189 commands

Modeling · Materials · UV · Rigging · Constraints · Lights · Cameras · Animation · Geometry Nodes · Physics · Particles · Rendering · World · Compositing · Scene · Import · Export

COMPATIBILITY

Tested on each Unreal version.

All versions, Unreal and Blender →

VersionStatusTests
UE 5.3Tested249 test suites, none failedDetails →
UE 5.4Tested252 test suites, none failedDetails →
UE 5.5Tested252 test suites, none failedDetails →
UE 5.6Tested252 test suites, none failedDetails →
UE 5.7Tested249 test suites, none failedDetails →
UE 5.8Tested252 test suites, none failedDetails →

THE LOG

Where each number comes from.

Each number on this page, with the date it was measured and the file that records it. How each one is tested is on the verification page.

See how it is tested →

  1. 2026-09-21

    The Blender panel above, recorded

    21 commands in Blender 5.2.1 LTS, shown as they happened.

    content/blender_session.json

  2. 2026-09-17

    Counts taken from the code

    458 Unreal Engine commands, 189 Blender commands, 669 MCP tools, 346 automated tests.

    the version line in the README, checked before every release

  3. 2026-09-17

    Blender tested on 5 versions

    3.6.23, 4.2.17 LTS, 4.4.0, 5.0.1, 5.2.1 LTS: all 96 test suites on each, none failed.

    tools/suite_results.json

  4. 2026-09-16

    Unreal Engine 5.3 to 5.8 tested

    6 versions as Epic ships them, 249 to 252 test suites each, none failed.

    tools/ue_engine_sweep_results.json

  5. 2026-09-13

    The Unreal panel above, recorded

    36 commands on a UE 5.7 test project, shown as they happened.

    content/panel_session.json

This is the Markdown version of https://mifshowcase.store/, made from the page itself when the site is built. A map of the whole site for AI assistants: https://mifshowcase.store/llms.txt