Unreal Engine MCP Server
An MCP server for Unreal Engine: control assets, actors, the editor, sequencer and blueprints
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- The execute_python tool and console commands run arbitrary code in the editor
- Changes the contents of your Unreal project
Install
Manual install
claude mcp add unreal-engine --transport http http://localhost:3000/mcpNative HTTP transport from the plugin. Enable Native MCP in the plugin settings first.
This is third-party code. Review the repository files before installing.
What it does
The server connects an agent to Unreal Engine through a native C++ Automation Bridge plugin. The agent manages assets, spawns and transforms actors, works with the editor, camera, levels, lighting, physics and animation, runs the sequencer and rendering, and edits blueprint, Niagara and material graphs. It offers two transports: native HTTP or SSE directly from the plugin without a bridge, or a TypeScript bridge. The server starts even without an active Unreal connection and reconnects with backoff. Dangerous console commands are blocked, and token authentication is on by default.
Who it is for. For Unreal Engine game developers who want to control the editor and scene through an agent.
Good fit when
- You need to place actors and set up a scene from a description
- You need to build or edit a blueprint, material or Niagara effect
- You need to control the sequencer and rendering from an agent
Not a fit when
- You have no Unreal Engine in the 5.0 to 5.8 range
- The project is blueprint-only and you cannot add a code target to build the plugin
Example request
Spawn a cube in the scene, enable physics on it and take a viewport screenshotLimitations
You need Unreal Engine 5.0 to 5.8 and the Automation Bridge plugin, and building from source requires the project to have a code target. The TypeScript bridge option needs Node.js 20.19 or newer and the UE_PROJECT_PATH variable. Some operations require enabling extra Unreal plugins. The execute_python tool and console commands run arbitrary code in the editor, so use it only on your own projects.
How to disable. Remove the server entry from your MCP client config and disable or remove the Automation Bridge plugin in the Unreal editor.
MCP
- Transport
- http, sse, stdio
- Authentication
- not required
| Environment variables | |
|---|---|
| UE_PROJECT_PATH | Path to your Unreal project, needed for the TypeScript bridge option. |
| MCP_AUTOMATION_PORT | Automation bridge port, default 8091. |
Security check
- The execute_python tool and console commands run arbitrary code in the editor
- Changes the contents of your Unreal project
README in short
The README covers a server with a native C++ plugin and two transports: direct HTTP or SSE from the plugin, and a TypeScript stdio bridge. It details server install via npx or from source, plugin install by copy or as an external folder, lists of required and optional Unreal plugins, and client setup. It also documents environment variables, token authentication and blocking of dangerous console commands. MIT licensed.
FAQ
Do I need Node.js?
The native HTTP transport from the plugin needs no Node.js. It is required only for the stdio TypeScript bridge.
Which Unreal versions are supported?
Per the README, all versions from 5.0 to 5.8.
Related
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
Skills for real engineers by Matt Pocock
Skills For Real Engineers
Small composable skills for engineering with agents: plan grilling, TDD, bug diagnosis, code review and architecture
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
Reference MCP servers
Model Context Protocol servers
Official reference MCP servers: Filesystem, Fetch, Git, Memory, Sequential Thinking, Time and Everything