Unreal 5.8 Ships a Local MCP Pipe, Not an LLM

Unreal Engine 5.8 shipped on June 17, 2026 with an experimental MCP server inside the editor. Claude Code, Cursor, and other agents call editor tools over local HTTP at 127.0.0.1:8000. The process holds no language model of its own.

Epic Games still billed the drop as faster content work through integrated LLM workflows, and the last planned major Unreal Engine 5 release is also the one that treats coding agents as editor users. The plugin named Unreal MCP is only the socket. The tools live in AllToolsets and the Toolset Registry.

THE LOCAL SERVER

• Bind: http://127.0.0.1:8000/mcp by default, with port 8000 and path /mcp both editable in Editor Preferences.
• Server name: serverInfo.name is always unreal-mcp, even if you change the port.
• Auth: none. The listener is loopback by default and is not meant for remote use.
• Status: Experimental. Epic says features are incomplete and that APIs can change as the work matures.

That split is the whole product. Studios that chase a chat box inside Unreal will miss the thing Epic actually shipped: a typed catalog of editor calls that any MCP client can invoke.

The Editor Now Speaks MCP Over Loopback

The experimental Unreal MCP editor documentation is blunt about the shape of the feature. Unreal MCP embeds a server in the editor process so an MCP-compatible agent can drive the editor over a local HTTP connection. The identifier in source,.uplugin files, and console commands is ModelContextProtocol. Unreal MCP is only the friendly name in the Plugin Browser.

MCP itself is an open spec for how an AI client talks to a server with a small set of JSON-RPC messages such as initialize, tools/list, and tools/call. A server advertises MCP tools, resources, and prompts. Tools are named functions with typed parameters. Resources are read-only data fetched by URI. Prompts are reusable templates. Unreal MCP is the server. The model, if any, lives in Claude Code, Cursor, VS Code, Gemini, Codex, or whatever else you pointed at the port.

The server’s other job is threading. Tool calls run on the Unreal game thread, one after another, so clients are told not to overlap them. The HTTP server is ticked from the core ticker. That is why a hung tool feels like a hung editor: the call is sitting on the same thread that paints the viewport.

Default transport is HTTP with Server-Sent Events. Stdio and WebSocket are out. Most desktop MCP servers still spawn as child processes on stdio; this one is already running inside Unreal, so the client opens http://127.0.0.1:8000/mcp and speaks HTTP. First-run failures cluster on that port. If something else owns 8000, the docs tell you to pass a port to ModelContextProtocol.StartServer or to change it under Editor Preferences > General > Model Context Protocol.

AllToolsets Must Stay Enabled or the Server Is Empty

Turn on Unreal MCP alone and you get a listening socket with almost nothing to call. Toolsets and tools are not implemented by Unreal MCP. The AllToolsets plugin has to be enabled, and it pulls in the Toolset Registry, which is enabled automatically. Restart when the editor asks.

AllToolsets is an editor-only aggregator with EnabledByDefault off, so it must be flipped on in the Plugin Browser or in the.uproject file. Epic’s Claude Code companion spells out the two plugin entries by name, ModelContextProtocol and AllToolsets, and says the server starts but exposes no tools if only the first one is on. If you want a smaller surface, skip AllToolsets and enable individual toolset plugins instead.

Setup after that is short. Enable Auto Start Server so the listener comes up with the editor, or run ModelContextProtocol.StartServer from the console. Then run ModelContextProtocol.GenerateClientConfig with a client name. The command writes the config the agent expects, including.mcp.json at the project root for Claude Code, and points it at the running URL. JSON configs merge with whatever is already there. The TOML file used by the Codex CLI is write-once, so a stale copy has to be deleted by hand.

An optional Terminal plugin can keep the agent CLI inside the editor window. The docs warn you to set TERM=xterm-256color and to cd into the folder that actually holds.mcp.json, because the Terminal panel’s working directory is the workspace root in source builds and the engine install directory in installed builds.

Hundreds of Tools Sit Behind Three Calls

The Toolset Registry is the product hiding behind the socket. It is an Unreal subsystem that collects every class derived from UToolsetDefinition, or unreal.ToolsetDefinition in Python, at startup. Unreal MCP wraps each marked function as an MCP Tool. Epic’s own companion plugin describes the result as hundreds of tools across 30+ toolsets, covering actors, Blueprints, materials, Niagara, Control Rigs, Sequencer, State Trees, widgets, the Gameplay Ability System, and automation tests.

By default the plugin runs in tool-search mode (bEnableToolSearch true). tools/list does not dump the whole catalog. It returns three meta-tools, list_toolsets, describe_toolset, and call_tool, and the agent walks that path on demand. Epic’s reason is practical: a giant initial schema blows the prompt cache. Authors are told not to assume their Tool will be advertised eagerly, because the search path is what a connecting agent will see.

The registry is also shared. A toolset written for MCP works for other AI surfaces in the engine without a rewrite. That is the second-order shift. Plugin authors are no longer writing only for a human clicking menus. They are writing functions whose names, type hints, and Google-style docstrings become the schema an agent reads.

Most Shipped Toolsets Are Python Classes

Most of the toolsets that ship with the registry, including SceneTools, ActorTools, MaterialInstanceTools, and ObjectTools, are Python. They live as.py modules under a plugin’s Content/Python/ folder and are discovered at startup. A class uses @unreal.uclass(), inherits from unreal.ToolsetDefinition, and marks each advertised function with @toolset_registry.tool_call as a static method. Parameter and return hints drive the JSON Schema. Docstrings become the text the model sees, so they have to be written like a public API, not like a comment to yourself.

C++ Is for Types Python Cannot Express

C++ toolsets derive from UToolsetDefinition, mark the class UCLASS(BlueprintType, Hidden), and expose static UFUNCTION methods with meta = (AICallable). Epic points at UAttributeSetToolset in the GASToolsets plugin as a complete shipped example, two AICallable functions with plain USTRUCT returns. GASToolsets itself ships disabled and trips an experimental warning the first time you enable it. Reach for C++ when the Tool needs engine APIs Python cannot see, when the signature uses reflected types that do not map cleanly, or when the Python-to-engine hop is too slow.

PYTHON VERSUS C++ TOOLSETS

After a new toolset lands, ModelContextProtocol.RefreshTools forces a re-poll. Live Coding updates existing C++ bodies; a new UFUNCTION still needs an editor restart. Omit @toolset_registry.tool_call, or add meta = (AIIgnore), to keep a helper function off the wire.

How Do You Connect Claude Code or Cursor?

From the editor console, run ModelContextProtocol.GenerateClientConfig with one of the supported names and launch the agent from the folder that holds the file it wrote. Claude Code gets.mcp.json pointing at http://127.0.0.1:8000/mcp with type http. Cursor, VS Code, Gemini, and Codex are first-class targets in the same command, and All writes every format at once. Launch the editor first, confirm the MCP server started, then start the agent, or you will reconnect by hand.

GENERATECLIENTCONFIG NAMES

• ClaudeCode: Writes.mcp.json at the project root for Claude Code.
• Cursor, VSCode, Gemini: JSON configs that merge with existing server entries.
• Codex: TOML for the Codex CLI, refused if a file is already there.
• All: Emits every supported client config in one pass.

Epic also published Unreal Engine Skills for Claude Code, an official companion on GitHub with 305 stars and 43 forks on the page we opened. Thomas Mansencal, Pipeline Engineering Director at Epic Games, posted on June 24, 2026 that the company had open sourced the plugin so Claude Code and Desktop users could get rolling with Unreal MCP. Install is /plugin install unreal-engine-skills-for-claude-code@claude-plugins-official. A SessionStart hook injects Unreal conventions, and the skill tells Claude to save before bulk edits, wait on compiles, and avoid overlapping calls that deadlock the game thread.

The hook is a bash script. It runs on macOS and Linux as-is. On Windows it wants Git Bash or WSL. Native PowerShell without bash still gets the MCP tools and loses only the short project-context note. The plugin does not ship a static.mcp.json; you still generate that from the editor so the port and path stay honest.

Localhost Is Not a Trust Boundary

Epic’s docs say the server only accepts connections from the same machine, has no authentication layer, and is not designed for remote use. The HTTP listener follows HTTPServer.Listeners DefaultBindAddress, which defaults to localhost, and it rejects non-loopback Origin headers. That Origin check is for browser tabs. It does not stop another process running as you.

Installing this plugin gives Claude broad, live access to the running Unreal Editor. Treat that access the same way you would treat running arbitrary code from an assistant, because in practice it is.

Epic Games, Unreal Engine Skills for Claude Code README

The same README is the sharper document. Its Claude Code plugin security notes say localhost is not a trust boundary, and that any process running as the same user on the same machine can connect. Do not run the server on a shared box. Do not expose the port past loopback. ProgrammaticToolset.execute_tool_script runs arbitrary Python inside the editor, with access to every toolset API, the project on disk, and editor-privileged functions. Pair that with Claude Code’s –dangerously-skip-permissions flag and there is no per-tool approval gate left.

FToolsetRegistry still gives you some brakes. The API exposes allow-list and block-list controls on tool names, plus RegisterToolset, Find, and ExecuteTool. That is how a project can keep a dangerous script tool off the catalog without taking the whole server down. Source control is the other brake. MCP tools edit live UObject state and can move or delete tracked assets in one call, so Epic’s own guidance is to commit or shelve before a long session and read the diff before you submit.

Epic’s City Sample Already Runs This Way

On August 27, 2026, the Unreal Engine account posted that a new City Sample level was built entirely in Unreal, using PCG for procedural world-building, with help from an LLM through the Unreal MCP server. The pitch was “fully editable,” no black boxes. That is Epic using its own pipe on a shipping sample, not a third-party demo reel.

City Sample just got a major update🏙️

The new level was built entirely in Unreal Engine, using PCG for procedural world-building, with assistance from an LLM through the new Unreal MCP server.

Fully editable. No black boxes: https://t.co/ZbYK33aQf1 pic.twitter.com/S268aBgRwr

— Unreal Engine (@UnrealEngine) August 27, 2026

A week earlier, on August 20, 2026, community manager Flak wrote that Unreal MCP was available in Unreal Editor for Fortnite. UEFN gets toolsets built for that editor, delivered through the same Toolset Registry, and not every UE 5.8 toolset works there. Flak framed the work as part of unifying streams on the road to UE6, and called the UEFN side beta.

HOW MCP LANDED IN UNREAL

1. November 25, 2024: Anthropic publishes the Model Context Protocol as an open spec for tools, resources, and prompts.
2. June 17, 2026: Unreal Engine 5.8 ships with the experimental Unreal MCP plugin and the Toolset Registry.
3. June 24, 2026: Epic open sources Unreal Engine Skills for Claude Code so the official client can find the server.
4. August 20, 2026: Unreal MCP opens in UEFN as beta, on the same registry, with a narrower toolset list.
5. August 27, 2026: Epic posts the City Sample update built with PCG and the Unreal MCP server.
6. September 17, 2026: The Claude companion plugin lands a commit to permit safe concurrent tool calls on the client side, while the editor still runs tools on the game thread.

The June launch wave sold a simpler story, that you talk and a game appears. The clips that travelled were locomotion setups, spawned heroes, and toy cities. Pushback in those threads was specific: a jukebox pick is not composing, and a demo that never shows two mechanics talking to each other is fuel for people who already hate the pitch. Late September testing is more useful than those clips. People who already know Unreal are getting playable pinball tables and combat toys out of the pipe, and they are still opening the generated Blueprints to find hard-coded logic that only works if the person prompting can name the next node.

What Unreal MCP Still Will Not Do

Unreal MCP will not run a model, will not speak stdio or WebSocket, will not advertise Resources or Prompts from any shipping toolset, and will not auto-discover registry tools in a cooked build. The feature is editor-first, loopback-only by default, and labeled Experimental, with APIs that Epic says can change as it matures. Cooked hosts can still listen, but only for tools registered by hand through IModelContextProtocolModule::AddTool().

SPEC VERSUS WHAT SHIPS

The runtime split matches that table. ModelContextProtocol and ModelContextProtocolEngine are runtime modules. They own the server, the settings, and the console commands. ModelContextProtocolEditor is editor-only, and it is the piece that adapts registry toolsets into MCP Tools. Live Coding will not pick up a new UFUNCTION. Adding a Tool still means restarting the editor.

UE 5.8 is the last planned major Unreal Engine 5 drop as Epic ramps work on UE6. The MCP server is experimental on purpose: a local pipe, a registry of typed calls, and a warning that the schema will move. The studios that get something out of it will be the ones writing toolsets for their own pipelines, then pointing an agent they already pay for at 127.0.0.1.