If you use Claude Code, it can install MifBridge for you. Open Claude Code in your Unreal project's folder and paste the prompt below. It follows the same steps as Installation, checks each one before moving on, and asks you before anything that changes your system.

Before you paste it

Claude Code, opened in your project's folder: the one that contains your .uproject file.
The MifBridge files, unpacked somewhere on your machine. Claude will ask you where.
The Unreal editor closed for that project, because the plugin is built with the editor shut.
Python 3.10 or newer on your machine.

Plugin already built and the editor open? You do not need the prompt: press SETUP ▸ Set up Claude Code in the MifBridge panel, and it connects Claude Code to that editor. See Installation.

The prompt

Copy all of it:

You are setting up MifBridge for me. MifBridge is an editor-only Unreal Engine plugin that serves a
local HTTP API on 127.0.0.1:8791, plus an MCP server that exposes it to you, plus an optional Blender
add-on. The MCP server's folder is Content\Python\MifBridge\mcp-server inside the plugin, or
tools\mcp-server in a copy from GitHub; below, <server folder> means whichever one exists, and
<scripts folder> means the folder that contains it. Work through the steps below in order. Check each step before moving on,
tell me what you found, and stop and ask me if anything is unclear or unexpected. Never overwrite a
file without showing me what is there first, never delete anything, and ask me before you change any
system or environment setting.

1. Find my project: the .uproject in the current folder. Read its "EngineAssociation" to find which
   engine it uses. A version such as "5.4" is a launcher install, usually at
   "C:\Program Files\Epic Games\UE_5.4". Anything else, usually a GUID, is a source build: look it up
   in the registry under HKEY_CURRENT_USER\Software\Epic Games\Unreal Engine\Builds. Confirm the engine
   folder exists and contains Engine\Build\BatchFiles\Build.bat. MifBridge supports Unreal Engine 5.3
   to 5.8 on Windows; if the project uses anything else, stop and tell me.

2. Ask me where the MifBridge files are. Copy that folder to <project>\Plugins\MifBridge. It must
   contain Source and the .uplugin file. Do not copy Binaries or Intermediate folders from anywhere
   else. If <project>\Plugins\MifBridge already exists, stop and ask me what to do.

3. Make sure the Unreal editor is not running for this project. Then build the editor target:
   "<engine>\Engine\Build\BatchFiles\Build.bat" <ProjectName>Editor Win64 Development
   -Project="<full path to the .uproject>" -WaitMutex
   Read the output for errors and the final result line; do not trust the exit code alone. If the
   build fails, show me the first error and stop.

4. Install the MCP server's dependencies with the same Python you will launch it with:
   python -m pip install -r "<project>\Plugins\MifBridge\<server folder>\requirements.txt"

5. Choose a token. Generate a random secret of 32 hex characters. Ask me before storing it as my
   user environment variable MIF_BRIDGE_TOKEN (setx MIF_BRIDGE_TOKEN <secret>); the editor reads it
   when it starts. If I say no, the default token "dev" is used. Tell me that is only acceptable on a
   machine nobody else can reach.

6. Register the MCP server for this project in .mcp.json in the project folder, with a server named
   "mif-bridge": command "python", args [the full path to <server folder>\server.py], and env
   MIF_BRIDGE_URL "http://127.0.0.1:8791/api" and MIF_BRIDGE_TOKEN set to the same token. If
   .mcp.json already exists, add this entry and keep everything else, then show me the result. If
   the project is a git repository, tell me whether .mcp.json is tracked, because it will hold the
   token.

7. Ask me whether I use Blender. If I do, tell me to download the free add-on from
   https://mifshowcase.store/downloads/MifBlender-1.2.0.zip (it is not inside the Fab package), then
   install that zip from Blender's Edit > Preferences > Add-ons > Install, enable
   "MifBlender (MifBridge backend)", and set its Token preference to the same token. You cannot
   click inside Blender for me, so give me the steps.

8. Ask me to open the project in the Unreal editor, and wait until I tell you it is open. Then run
   python "<project>\Plugins\MifBridge\<scripts folder>\verify_install.py" and read its result back to me. It
   tells a wrong token apart from a stopped bridge and from another program on the port. If it
   reports a problem, explain what it means and what to do.

9. Finally, tell me to restart this Claude Code session so it loads the new MCP server, and that the
   first call worth making is self_audit, which reports the engine, the endpoint count and the
   safety state.

What it will and will not do

It asks first before storing the token as an environment variable, and before replacing anything that already exists.
It never deletes anything, and it never overwrites a file without showing you what is there.
It cannot click for you. Opening the Unreal editor and installing the zip in Blender are yours to do; it tells you when.
It checks rather than assumes. The build output is read for errors, not trusted on its exit code, and the final step runs verify_install.py against the running editor.

When it is done

Restart Claude Code, and the MifBridge tools appear. The first call worth making is self_audit, which reports the engine version, how many endpoints are live, and the current write mode.

If a step fails, Troubleshooting covers the common causes, and Installation walks through the same steps by hand.

Install with Claude

Before you paste it

The prompt

What it will and will not do

When it is done