# Flopperam Unreal Engine MCP: a local Python bridge into a live editor

> The repository ships two different servers: a hosted Flop MCP reached by URL and a community Python server you run yourself. This article covers what the open-source half actually does, how the UnrealMCP plugin fits in, and where the boundary sits.

**flopperam/unreal-engine-mcp** — This MCP is now owned by Aura! Please try out the most intelligent AI agent for Unreal Engine at https://www.tryaura.dev/?utm_source=youtube&utm_medium=video&utm_campaign=flop

- Repository: https://github.com/flopperam/unreal-engine-mcp
- Website: https://www.tryaura.dev/?utm_source=youtube&utm_medium=video&utm_campaign=flop
- Stars: 1,088 · Forks: 204
- Language: C++
- License: not declared
- Published: 2026-09-10 · Updated: 2026-09-10 · Language: en
- Canonical page: https://hysenlabs.com/projects/flopperam-unreal-engine-mcp

## Two servers share one repository name

The README opens with an acquisition notice: Flopperam is now part of Aura, and the page points readers to tryaura.dev for what comes next. Under that notice the repository splits into two products with almost nothing in common. The hosted Flop MCP lives at agent.flopperam.com/mcp and is reached with a URL plus an API key. The open-source local MCP lives in the Python/ folder, is cloned and run by the user, and pairs with the UnrealMCP plugin bundled under UnrealMCP/. The README is explicit that the hosted server is "a completely different, much more advanced server that shares no code with the local Python/ server in this repo." That sentence is the most important one on the page, because the long tool table that follows describes the hosted server, not the code you can read here. Anyone who clones the repository expecting 50+ tools across nine domains will be working with the smaller list instead: scene manipulation, actor management, world building, and foundational Blueprint operations such as add_node, connect_nodes, create_variable and create_function across 23+ node types. The last push to the repository was on 2026-06-26, so the code has been static for roughly three months while the hosted product is described as shipping new tools regularly. The repository is not archived, but that gap is the practical signal about where development effort goes.

## What the local server actually controls

Control flows through two pieces that must both be present. The UnrealMCP plugin runs inside the editor and exposes the editor's own object model. The Python server sits outside the editor, speaks MCP to your client, and forwards commands to the plugin. Nothing in the README suggests the Python server manipulates .uasset files on disk directly; the design is a live-editor bridge, which is why the tagline says "Control a live Unreal Editor through natural language." That choice has consequences. The editor has to be open, the plugin has to be loaded, and the project has to be the one the plugin is running inside. A headless build machine or a CI runner that never opens the editor is outside the design. The Blueprint toolset is described as foundational rather than full lifecycle: you can add nodes, wire them, create variables and create functions, but the batched narrow tools that the hosted table lists (bp_create, bp_variable, bp_component, bp_nodes, bp_wire, bp_commit) belong to the other server. For scene work the local server is more complete relative to its scope: actor management and world building are named as first-class capabilities. The Python requirement is 3.12 or newer according to the setup row in the comparison table, and the repository also carries LOCAL_SETUP.md and DEBUGGING.md at the top level, which is where the maintainers put the operational detail that does not fit in the README.

## Installing the local server and running a first prompt

The README's comparison table gives the shape of the local path: clone the repository, install Python 3.12 or newer, and run the server from the Python/ folder. The repository does not print a full command sequence in the README itself; LOCAL_SETUP.md at the top level is the file that carries the setup steps, so read it before running anything. The clone step is the same for either path.

```bash
git clone https://github.com/flopperam/unreal-engine-mcp
cd unreal-engine-mcp
```

After that, the Python/ folder holds the server and UnrealMCP/ holds the plugin. The plugin is what the editor loads; the Python process is what your MCP client talks to. Once both are running and the server is registered in your client, the client should list the local toolset rather than the hosted one. If you instead want the hosted Flop MCP, the README gives an exact client config for Cursor, placed in .cursor/mcp.json for a project or ~/.cursor/mcp.json globally.

```json
{
  "mcpServers": {
    "flopperam-unreal": {
      "url": "https://agent.flopperam.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
```

Claude Code users get a one-line registration instead, with the transport set to http.

```bash
claude mcp add -H "Authorization: Bearer YOUR_API_KEY" --transport http flopperam-unreal https://agent.flopperam.com/mcp
```

Those two snippets point at the hosted endpoint and require an API key from the account page. Do not paste them in if your goal is the open-source server; the README treats them as separate products with separate setup, and the local path has no URL and no key.

## Where the local server is the wrong tool

The clearest failure mode is expecting parity. The README's own table puts materials, VFX, animation, UMG, AI and behavior trees, landscape, cinematics, PCG and data assets in the hosted column. If your task is authoring a Niagara system or retargeting an IK rig, the local server is not the thing to reach for, and the README does not claim otherwise. A second limit is environmental: because the plugin runs inside a live editor, the server is only as available as that editor session. Anything that needs to run without a GUI session has no path here. A third is documentation depth. The README describes the local server's tool descriptions as "Basic tool descriptions" and the hosted server's as "Rich per-tool LLM guidance, cross-tool relationship mapping, error recovery patterns." That difference matters more than it sounds, because an LLM driving an editor will hit ambiguous states, and a tool description that does not explain recovery leaves the model guessing. Finally, the repository carries no licence file, and the licence field is listed as unknown. That is a real gap for anyone who needs to know the terms before the code touches a commercial project.

## The alternative: the hosted Flop MCP on the same page

The obvious alternative is not a different project; it is the other half of this one. The hosted Flop MCP replaces the local Python process with a remote endpoint at agent.flopperam.com/mcp, replaces the bundled UnrealMCP plugin with the FlopAI plugin installed separately from flopperam.com/unreal-agent, and replaces the foundational Blueprint toolset with a batched set organised around bp_create, bp_variable, bp_component, bp_nodes, bp_wire and bp_commit, plus inspection tools such as bp_brief, bp_inspect and bp_export. Setup shrinks to one URL and one API key, and the README lists Cursor, Claude Code, Windsurf, VS Code Copilot and Cline as supported clients. The trade is control and dependency: the hosted path requires an account, a key, and a network round trip to a third party for every editor action, and it shares no code with the repository you can read. Outside this repository, the general alternative is building your own bridge between an MCP client and the editor's scripting interface, which gives you exactly the tools you define and none of the maintenance, at the cost of writing and keeping all of it. The README does not discuss either option, so treat that as a design decision you make, not one the project makes for you.

## Maintenance, upgrade cost and the licence question

The last push was on 2026-06-26, which is more than six months before today. The repository is not archived, but on the evidence available it is not being actively developed, and the README's own framing supports that: the hosted server is the one described as receiving new tools regularly, and the acquisition notice directs readers to tryaura.dev for "the latest updates to the MCP and what we're building next." Practically, that means upgrade cost on the local half is mostly the cost of tracking Unreal Engine releases yourself. The README badge claims Unreal Engine 5.5+, and the repository text does not say which specific engine versions the bundled UnrealMCP plugin has been built against. If you move to a newer engine, you are testing that yourself. The Python side pins a floor of 3.12 or newer, so a project stuck on an older interpreter cannot run the server without an upgrade. On licensing: the repository does not state a licence, and the licence field is unknown. That is not a legal opinion, but it is a practical blocker. Before you ship anything that includes this code, confirm the terms with the maintainers or the current owner, because a repository with no stated licence leaves you without a clear grant.

## Conclusion

Adopt the local Python server if you want to read and drive a running Unreal Editor from an MCP client without sending a project to a hosted endpoint, and if foundational Blueprint work is enough for the task. Do not adopt it expecting the tool surface described in the hosted table: the README states the hosted Flop MCP shares no code with the Python folder and is a different, more advanced server. Before committing, open Python/ and UnrealMCP/ and confirm which engine versions the bundled plugin targets, because the README badge claims 5.5+ while a related search phrase asks about 5.8 and the repository text does not answer it.

## FAQ

### Is there an Unreal Engine MCP server?

Yes. This repository ships a local MCP server in the Python/ folder that pairs with the bundled UnrealMCP plugin, and its README also points to a separate hosted Flop MCP at agent.flopperam.com/mcp. The two share no code.

### How to set up Unreal MCP?

For the local server the README says to clone the repository, install Python 3.12 or newer, and run the server from the Python/ folder alongside the UnrealMCP plugin; LOCAL_SETUP.md carries the detailed steps. For the hosted server you need an API key and one client config entry pointing at the hosted URL.

### What is the best Unreal Engine MCP server?

The README describes the hosted Flop MCP as the more advanced of the two, listing 50+ tools across nine domains, and states it shares no code with the local Python server. Whether that makes it best for you depends on whether you can accept a hosted endpoint and an API key.

### Is unreal engine mcp free?

The README does not state pricing for either server, and the repository does not include a licence file. The hosted path requires an API key from an account page, so check the current terms there before assuming either option is free.

### How to use unreal engine mcp?

Run the Python server from the Python/ folder with the UnrealMCP plugin loaded in an open editor, then register the server in an MCP client such as Cursor, Claude Code, Windsurf, VS Code Copilot or Cline. The client then drives the live editor through the tools the local server exposes.

### What is unreal engine mcp?

It is an MCP server that lets an MCP client control a live Unreal Editor. This repository contains the open-source local version in Python/ plus the UnrealMCP plugin, and its README also describes a separate hosted Flop MCP reached at agent.flopperam.com/mcp.

## Sources

- [flopperam/unreal-engine-mcp on GitHub](https://github.com/flopperam/unreal-engine-mcp)
- [Issues](https://github.com/flopperam/unreal-engine-mcp/issues)
- [Project website](https://www.tryaura.dev/?utm_source=youtube&utm_medium=video&utm_campaign=flop)
- [README](https://github.com/flopperam/unreal-engine-mcp/blob/main/README.md)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/flopperam-unreal-engine-mcp