Skip to content
ShilpBot
Creative AI Tools

Unreal Engine MCP: Epic's Experimental Plugin Explained

Epic's Unreal MCP plugin lets AI assistants build Blueprints, materials and Sequencer content. See setup, supported clients, tools and the security warning.

By ShilpBot Team · Published · 4 min read

Epic Games ships an MCP plugin for Unreal Engine so that AI assistants can work inside the editor. Epic marks it experimental. This guide summarises Epic's documentation, including the security warning you should read. See also our roundup of creative tools with MCP.

What the Unreal MCP plugin is

Epic's documentation calls it Unreal MCP. It embeds an MCP server in the editor process, so the editor must be running. The plugin identifier is ModelContextProtocol. Epic states: Unreal MCP is Experimental, many features are still under development, and APIs and data formats may change at any time.

How to turn it on

  1. In Edit > Plugins, enable "Unreal MCP" (on by default) and "All Toolsets", then restart the editor.
  2. By default the server starts every time the editor launches and binds to http://127.0.0.1:8000/mcp. You can change the port in Editor Preferences, under Agentic Workflows.
  3. A "Generate Client Config" option writes a configuration file for your client.

It supports the Streamable HTTP and Server-Sent Events transports only. The stdio and WebSocket transports are not supported.

Which AI clients work

Epic names Claude Code, Codex, Cursor, Gemini CLI and Visual Studio Code with GitHub Copilot, plus the MCP Inspector. An Unreal Assistant panel supports several coding agents too.

What it can do

Epic lists tools for:

  • Spawning and editing actors.
  • Building Blueprints and Widget Blueprints.
  • Authoring materials, MetaSounds, PCG, Niagara and Sequencer content.
  • Inspecting Slate widgets, profiling and running automation tests.

Tool search is on by default, so the assistant can discover tools instead of loading them all at once.

The security warning

Epic's page says there is no authentication layer, so you should not expose the server beyond the local machine. It listens only on the loopback address by default and uses an allow-list of local origins.

  1. Do not change the host to a public address.
  2. Do not forward the port through a router.
  3. Keep the project in source control, because the assistant can change many assets quickly.

Practical limits

  • Tool calls run one at a time on the game thread.
  • Claude Code times out long calls after about 120 seconds.
  • Live Coding does not add new UFUNCTION declarations, so an editor restart is needed.
  • Cooked builds expose only tools marked as callable at runtime.

What it means for film and virtual production

Sequencer and material tools make this relevant beyond games. An assistant could set up shots or adjust materials while you direct. Treat it as an experiment until Epic removes the experimental label.

Sources

Frequently asked questions

Is Unreal Engine MCP official?

Yes. It is documented by Epic Games as the Unreal MCP plugin, and marked Experimental.

What is the default Unreal MCP address?

Epic says the server binds to http://127.0.0.1:8000/mcp by default, and the port can be changed in Editor Preferences.

Is the Unreal MCP server secure?

Epic says it has no authentication layer and should not be exposed beyond the local machine. It listens on the loopback address by default.

#Unreal Engine MCP#Unreal MCP#Epic Games AI#virtual production AI#Unreal Engine AI