Mount on UE 5.8's official MCP server

UE 5.8 ships its own MCP server (Epic’s ModelContextProtocol plugin). Instead of running ClaudeUnreal’s standalone server, you can mount ClaudeUnreal’s tools onto Epic’s server — your agent then talks to a single unreal-mcp server that hosts both Epic’s tools and ClaudeUnreal’s.

Note

UE 5.8 only. On UE 5.7, stay on the default Standalone mode — see Architecture & tools.

Try the panel first

Everything below can be driven from the Claude MCP panel — open it from the Claude button in the level-editor toolbar: click its arrow, then Panels → Claude MCP panel. This is a live replica — switch the mode, apply the restart, start the server:

Claude UnrealMCP INTEGRATION

Idle

Waiting for an agentBridge is ready — connect with the cu CLI

MODE

StandaloneMount on official

CONNECTION

Official MCP serverStandalone mode

Available tools3 tools · local

Editor bridgeListening · :55557

Copy cu connect command

Interactive demo · mirrors the in-editor toolbar panel

The real panel does the same things against your editor: the MODE switch writes the project setting, ⟳ RESTART restarts the editor to apply it, and Start official server runs Epic’s ModelContextProtocol.StartServer for you.

Set it up

1. Enable the plugins — in Edit → Plugins: Epic’s Model Context Protocol and Claude Unreal. Don’t restart yet.

2. Switch the mode — in the Claude MCP panel, pick Mount on official and hit ⟳ RESTART. (Equivalent setting: Project Settings → Plugins → Claude Unreal → MCP Mode.)

   On restart, ClaudeUnreal registers its toolset and removes its own claude-unreal entry from .mcp.json, so your agent never sees duplicate tools.

3. Start the server — press Start official server in the panel, or run in the ~ console:

   ModelContextProtocol.StartServer
   ModelContextProtocol.GenerateClientConfig ClaudeCode

   StartServer binds http://127.0.0.1:8000/mcp; GenerateClientConfig ClaudeCode writes a .mcp.json with one unreal-mcp entry pointing at it.

   Tip

   Turn on Editor Preferences → General → Model Context Protocol → Auto Start Server and you never need StartServer again.

4. Verify — reconnect your MCP client (it must re-read .mcp.json), then run /cu/verify-official-mcp for a one-shot check. If the toolset is missing, run ModelContextProtocol.RefreshTools and reconnect — or press Refresh tools in the panel.

What’s mounted

Mounting registers one toolset (ClaudeUnreal.ClaudeUnrealOfficialToolset) onto Epic’s Toolset Registry. The server exposes it through a gateway: the agent calls list_toolsets → describe_toolset → call_tool, and the toolset provides SpawnActor, GetActorsInLevel, and TakeScreenshot.

For the complete ClaudeUnreal surface (27 typed MCP tools + a ~463-command cu CLI), use the default Standalone mode — see Architecture & tools. The cu CLI works in either mode; it talks to the editor’s TCP bridge directly, not through .mcp.json.