Unreal Engine MCP server: which versions have one, and how to connect Claude
Epic ships a first-party MCP server, but only on 5.8, and it is experimental and off by default. How to check your own install, what an MCP server actually does in an editor, and how to connect Claude or Cursor on any version.
Loading…
Stop bouncing between AI and Unreal.
Drop the plugin into your project, point your MCP client at it, and let your AI actually build inside the editor.
Yes, but only on Unreal Engine 5.8, where Epic ships a first-party MCP server called Unreal MCP. It is marked experimental and it is off by default, so you have to enable it. On 5.6 and 5.7 there is nothing to enable. The plugin does not exist in the engine, and a third-party bridge is the only route.
Below: how to check your own install in about ten seconds, what an MCP server actually does inside the editor, and how to connect Claude or Cursor either way.
Check your own install
Do not take my word for it. Look for these three folders:
I have 5.6, 5.7 and 5.8 installed side by side. All three folders are present on 5.8 and absent on the other two. Engine features ship with engine versions; they are not backported.
The descriptor tells you the rest:
"FriendlyName": "Unreal MCP",
"Description": "Anthropic MCP (Model Context Protocol) server implementation for Unreal Engine.",
"IsExperimentalVersion": true,
"EnabledByDefault": false
Experimental and off by default
If you are on 5.8 and expected it to just work, that is why. Enable it in Edit → Plugins, search for Unreal MCP, tick it, restart the editor.
What an MCP server does in an editor
If you arrived here without knowing the term: MCP is a protocol that lets an AI assistant call real functions in another program. Inside a game engine that means the assistant is not writing code for you to paste. It is calling editor commands, and the asset appears in your content browser while you watch.
The part that matters more than the command count is that it reads state back. Compile a material, list the resulting errors, inspect a Niagara stack, take a screenshot of the viewport. An assistant that can only write is guessing. One that can check its own work and correct it is doing the job.
That loop is the whole thing. I have watched a run put a velocity module in the wrong stage of a Niagara emitter. It compiled clean and the particles sat still, which is the most annoying category of Niagara bug because there is no error to read. It read the stack back, saw the module in the wrong place, moved it, recompiled. I never told it what was wrong. I said "the sparks are not moving".
If you are on 5.8
Try Epic's first. It is free, first party, and it ships with the engine you already have. Enable the plugin, point your client at it, and spend an hour with it.
The question worth asking after that hour is simply how much of the editor you still cannot reach, because that is the only thing the decision turns on. A tool that covers half the editor sends you back to clicking for the other half, and a workflow with a hole in it is not really a workflow.
If you are on 5.6 or 5.7
There is no plugin to enable and no flag to flip. Third party is the only option.
This matters more than it sounds, because studios mid-production do not upgrade engine versions to try an experimental feature. A project on 5.7 has a build pipeline, a plugin set and a QA baseline pinned to it. "Upgrade to 5.8" is not a suggestion, it is a quarter of work.
Connecting one
This is what I work on full time. It covers 28 categories: Blueprint graphs and components, materials down to Custom HLSL, Niagara including scratch pad modules, Control Rig hierarchies and RigVM solve graphs, PCG, Procedural Vegetation, Mutable, Sequencer with Movie Render Queue, MetaSounds and Sound Cues, Behavior Trees and EQS, UMG widget trees with MVVM viewmodels, and Unreal Insights profiling with trace analysis.
It runs on 5.6, 5.7 and 5.8, built and tested separately against each, because the engine ABI differs between versions and a single universal binary is not a thing that can exist. Three commands and your project is reachable:
Install the CLI:
bash
irm https://codefizz.dev/install.ps1 | iex
Install the plugin into your engine:
bash
cfa install-plugin "E:/Unreal/UE_5.8"
Check the editor is reachable:
bash
cfa health_check
And the step people skip and then regret:
Teach the assistant what the commands actually do:
bash
cfa skill install
Without it the model guesses at parameter names. With it, it looks them up before calling anything. The difference in how often the first attempt works is not subtle.
What it is not good at
Taste. It builds the thing you described, not the thing you imagined, and the gap between those is your job. I have not once had it produce something I would ship untouched.
Where it earns its place is the tedious, well-defined half: the Blueprint graph you have wired forty times, the material you can describe faster than you can build, renaming a hundred assets and fixing the redirectors afterwards. Structural work, not creative work.
Going further
If you would rather read the source before installing anything, there is a smaller MIT-licensed bridge I also maintain on GitHub. It covers a fraction of the surface above and exists mostly so the approach is inspectable.
Works on 5.6, 5.7 and 5.8, built and tested separately against each. 900+ commands across 28 categories, on UE 5.6, 5.7 and 5.8. Drive it from Claude Code, Cursor, VS Code, or any MCP client.
Three day free trial. No card, nothing locked off, and it runs on your real project.
