Epic publishes its walkthrough for Unreal MCP in UEFN

Epic has posted the full replay of its Creating in Fortnite livestream on the Model Context Protocol, presented by Verse evangelist Magnus Enebakk. It is the first end-to-end demonstration Epic has published of an AI agent driving one of its editors, and it lands two weeks after the plugin itself reached Unreal Editor for Fortnite.

Unreal MCP shipped with UE 5.8 and arrived in UEFN on 20 August. The mechanic is the same in both: the editor runs an MCP server inside its own process, and any tool that speaks the protocol — Claude Code, Codex, Cursor — connects to it over a local HTTP port. In UEFN that exposes four toolsets: Verse, for reading, writing and compiling source files; Verse Scene Graph, for creating entities and editing components and transforms; Creative Devices, for browsing the catalogue and configuring device properties; and Sessions, for starting, stopping and inspecting play sessions. What the agent produces is ordinary project data — Verse files you open, devices you tune in the Details panel, entities you select in the outliner.

The standard editor build is further along. Epic's UE 5.8 documentation marks the plugin Experimental and lists spawning actors, configuring lighting, creating material instances, inspecting Slate widgets and running automation tests, with room to register tools of your own. Setup is two plugins — Unreal MCP and All Toolsets — an auto-start toggle in Editor Preferences, and a console command, ModelContextProtocol.GenerateClientConfig ClaudeCode, which writes an .mcp.json into the project root pointing at http://127.0.0.1:8000/mcp.

Two constraints are worth reading before you build a working day around this. Tool invocations run on the game thread, serially, and Epic tells clients not to issue overlapping calls. And there is no authentication layer whatsoever — the documentation states the plugin is "not safe to expose beyond the local machine". Loopback only, HTTP and Server-Sent Events, no stdio or WebSocket transport.

The interesting line for anyone building editor tooling rather than levels is the Slate inspection paired with automation tests. An agent that can read your own panel's widget tree and then run a test against it closes a loop that has always needed a person clicking. The game-thread constraint is the catch, and it is a familiar one: any plugin doing heavy work on the game thread — a mesh import, a morph bake — is exactly what will leave an agent's call sitting in a queue until it gives up. Tooling that already yields properly will behave well here; tooling that blocks will expose itself immediately.

The UEFN implementation is in beta and Epic is direct about the rough edges. Its UEFN documentation flags confusion between XYZ and Left-Up-Forward coordinate ordering, and tool calls that hitch or hang the editor. Not every UE 5.8 toolset works in UEFN yet; Epic ties closing that gap to the wider merge of the two editors on the way to UE6.