Unreal Model Context Protocol (MCP) provides an official, Epic-supported way to connect your favorite agentic LLM tools directly to Unreal Engine🤝 Built on the open MCP standard, it enables agents to take action in your projects using the capabilities exposed by each editor—so you can use compatible agentic coding... tools or build your own integrations, skills, and workflows around how you create:show more

⚫Learn how to connect MCP in UE: ⚫Learn how to connect MCP in UEFN: ⚫Explore PCG and MCP workflows with the UE City Sample:

I love unreal.. Can we make a CLI too?

You guys have a lot of work to do to catch up to the rest of the industry with AI integration and world models. You’re falling behind rapidly.

Why is your MCP a single instance? This makes it hard to handle multiple agents

AI got so good it doesn’t need MCPs anymore.

You're behind

Probably the worst "MCP" implementation. LLMs spend so much time exploring the tools, search/find commands, in fact, it spends more time doing that instead of the actual task.

game devs who skip AI tooling will lose to those who use it

pointless cause ai doesnt have blueprint access with this trash mcp. update it and give real access

YES YES YES

Been using this and the videos always make it seem like the agent flies through building high quality at insane speeds. I can tell you this is not the case. It’s slow and it’s painful, even with bringing in premade assets.

Used it. My AI agent just gave up half way trough and was like "there is no tool to do that" and was like "do it manually in the UI". He did the C++ part super well, but when it came to the MCP part, he couldn't create most components and had issues re-parenting etc.

the demo i want to see: change 50 actors, inspect the result, undo the whole batch. agent workflows need a good ctrl+z story.

Wow, this is EPIC. I mean UNREAL.

Its good to see Unreal moving in this direction. I think they can see which way the tide is going. Excited to see how they keep improving Unreal to be SI agent focused. Its the future.

Let’s at least not recycle the demo from 6 months ago

Isn’t this just the experimental mcp you’ve had released for months now?

Don't run ai models inside the editor window. If the editor crashes or gets closed - your session will end.

mcp itself is just json-rpc plus tool schemas, so the useful part is which editor operations get exposed. undo is the hard bit. only edits wrapped in the editor's transaction system can be rolled back, and plenty of asset operations aren't

this is epic.

@bot remind me to set this up on my pc when i get home

MCP is so last year, make a cli like unity it's much better

Can someone please explain to me why anyone would run a CLI inside unreal engine instead of running a CLI outside of it? Why wouldn’t you just have Claude write c++?

Step 1 finished. Time for step 2

Two design choices in the docs stand out 🎮 Tool search is on by default, so agents see a few meta-tools instead of every schema, and tool calls run serially on the game thread. The first saves context, the second means one agent at a time in the editor.

Move to cli, this is better and more powerful.

melee in UE5 here we come

Most of the UE tooling I built was bridge code, so official support is welcome.

😎

super interesting, I am going to give a try and will see the result

❤️😍