UnrealClaude: Claude Code Inside the UE 5.7 Editor, and the MCP Bridge Behind It
Claude Code CLI integration for Unreal Engine 5.7 - Get AI coding assistance with built-in UE5.7 documentation context directly in the editor.
At a glance
- What is it?
- UnrealClaude is a source-built Unreal Engine 5.7 editor plugin that docks a Claude Code chat panel in the editor and exposes 20+ MCP tools for actor, Blueprint and level work. The interesting part is the bridge; the part to check before adopting is the Blueprint tooling the README itself flags as buggy.
- Who is it for?
- Adopt UnrealClaude if you already pay for Claude Pro or Max, work on Win64, Linux or Apple Silicon, and want editor-side chat plus scripted actor and asset operations without wiring your own MCP server. Do not adopt it if you need a signed binary drop-in, if Blueprint authoring is the core of your workflow, or if you cannot accept an unresolved licence question in a shipped product.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 81 days ago.
- What is it written in?
- Mainly C++, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
The gap UnrealClaude fills: editor context that a terminal Claude session does not have
A Claude Code session started in a terminal sees your source tree and nothing else. It cannot list the actors in the open level, cannot read a Blueprint graph, and has no reliable way to know which UE 5.7 API signatures apply to the engine build you actually compiled against. UnrealClaude targets that gap on two fronts. Inside the editor it adds a docked chat panel with streaming responses, tool call grouping and code block rendering. Outside the editor it runs an MCP server so other coding agents can reach the same operations. The README frames the second piece as a dynamic context loader that supplies UE 5.7 API documentation on demand, which is the claim worth scrutinising most, because stale engine documentation is the usual failure mode of AI assistance on Unreal projects. The intended user is a gameplay or tools programmer already comfortable building C++ plugins from source. This is not a marketplace drop-in, and the install instructions make that explicit: no prebuilt binaries are included.
How the plugin, the MCP bridge and the context loader fit together
The repository is two cooperating pieces. The first is the UnrealClaude.uplugin editor module, written in C++20, which supplies the chat panel and gathers project context automatically: modules, plugins and assets, plus the ability to see editor viewports. The second is a Node.js MCP bridge living under Resources/mcp-bridge, pulled in as a git submodule. The README lists 20+ Model Context Protocol tools covering actor manipulation, Blueprint editing, level management, materials and input. That bridge is a hard dependency for the Blueprint tools and the editor integration, which is why the install steps include a separate npm install inside the bridge directory. Long-running operations are routed through an async task queue so they do not hit a timeout, and conversation history persists across editor sessions. Authentication is deliberately not the plugin's problem: it reuses your existing Claude Code credentials, so there is no API key stored in the project. The README states Claude Opus 4.7 and its Claude Code release are supported, which pins the integration to a specific model generation rather than to the CLI in general.
Building from source: the commands and the config keys that matter
Prerequisites come first. Install the CLI with npm install -g @anthropic-ai/claude-code, then run claude auth login, which opens a browser to authenticate against a Claude Pro or Max subscription or to set up API access. Confirm with claude --version and claude -p "Hello, can you see me?". Clone with git clone --recurse-submodules, or fix an existing clone with git submodule update --init, otherwise the MCP bridge will be missing. The build is a standard Unreal Automation Tool invocation. On Windows: Engine\Build\BatchFiles\RunUAT.bat BuildPlugin -Plugin="PATH\TO\UnrealClaude\UnrealClaude\UnrealClaude.uplugin" -Package="OUTPUT\PATH" -TargetPlatforms=Win64. Linux and macOS use the equivalent RunUAT.sh with -TargetPlatforms=Linux or -TargetPlatforms=Mac. Copy the packaged output into YourProject/Plugins/UnrealClaude/ so the folder holds Binaries, Source, Resources, Config and the .uplugin file, then run npm install inside Resources/mcp-bridge. Launch the editor and the plugin loads; the chat panel is under Tools > Claude Assistant. Two platform notes from the README are easy to miss. On Linux (Rocky or Fedora) you need a long dnf package list including nss, gtk3 and mesa-libgbm, plus wl-clipboard or xclip for clipboard support, and the environment variables SDL_VIDEODRIVER=wayland and UE_Linux_EnableWaylandNative=1. macOS builds are documented for Apple Silicon only.
The Blueprint editing caveat, and what it means for a real project
The README's own feature list carries the most useful warning in the document. Blueprint editing, including Animation Blueprints and state machines, is marked with "Few bugs still, don't rely on fully". That is an unusually direct admission and it should shape how you evaluate the plugin. Actor manipulation, asset search, dependency and referencer queries, level opening and creation, and material and input work are listed without that caveat. Blueprint graph authoring is where the tooling is not yet trustworthy. There is a second constraint that the README does not resolve: script execution lets Claude write, compile via Live Coding, and run scripts, but only with your permission. How that permission is surfaced, whether it is per script or per session, and what happens when a Live Coding compile fails mid-operation are not described in the material available. Treat script execution as the highest-risk surface and read the source before enabling it on a team project. A third gap is dependency weight. The plugin needs the Claude Code CLI installed and authenticated on every machine, plus a Node.js runtime and an npm install for the bridge. There is no air-gapped path described.
UnrealClaude versus wiring your own MCP server
The obvious alternative is to skip the plugin and expose your own Unreal integration through the Model Context Protocol, using the same Claude Code CLI you already have. The difference is where the work sits. A hand-rolled server gives you exact control over which operations are exposed, how permissions are checked, and what the tool schemas look like for your project's conventions. It also means you own the editor-side plumbing: the docked panel, the streaming response handling, the tool call grouping, the async queue, and the session persistence that UnrealClaude ships as one package. UnrealClaude's value is that bundle plus the dynamic UE 5.7 context loader, which is the piece hardest to reproduce well. If your team already has an MCP server for internal tooling, the plugin's bridge is a second server to maintain rather than a replacement. If you have no MCP infrastructure and want editor-side assistance this week, the plugin is the shorter path, provided you accept its Blueprint limitations and its source-build requirement.
Maintenance, release cadence and the licence question
The release history shows v1.4.5 in early May 2026, v1.5.0 in mid May, and v1.5.1 on 26 June 2026, so the project is being maintained on a roughly monthly cadence rather than being abandoned. That matters for a plugin pinned to a specific engine version, because UE point releases and Claude Code CLI changes both break integrations of this kind. Expect to re-run the RunUAT BuildPlugin step whenever you move engine version, and to re-run npm install in Resources/mcp-bridge when the submodule moves. The README displays an MIT badge, but the repository metadata supplied here lists the licence as unknown. Those two signals conflict and the discrepancy is not explained in the material. If you plan to ship this inside a commercial product, read the LICENSE file in the repository you actually cloned and confirm it before you build a dependency on it. Nothing here is legal advice; the point is simply that the badge and the metadata disagree, and only one of them is authoritative.
Who should build this, and what to check before you do
The plugin suits a solo developer or small team on Windows, Linux or Apple Silicon who already holds a Claude Pro or Max subscription, builds C++ plugins from source as a matter of course, and wants actor, asset and level operations driven from a chat panel without standing up MCP infrastructure. It does not suit anyone who needs a signed binary, anyone working on a locked-down machine without Node.js or outbound authentication, or anyone whose daily work is Blueprint graph authoring, given the README's own warning. The verification order is short. Build the plugin with RunUAT against your exact 5.7 install and confirm the packaged output lands with Binaries, Source, Resources and Config intact. Then run npm install in Resources/mcp-bridge and check it completes. Then open Tools > Claude Assistant and exercise one actor operation and one asset query before you touch Blueprint tools at all. If the BuildPlugin step fails, the rest of the plugin is unreachable regardless of how good the context loader turns out to be.
Editorial conclusion
Adopt UnrealClaude if you already pay for Claude Pro or Max, work on Win64, Linux or Apple Silicon, and want editor-side chat plus scripted actor and asset operations without wiring your own MCP server. Do not adopt it if you need a signed binary drop-in, if Blueprint authoring is the core of your workflow, or if you cannot accept an unresolved licence question in a shipped product. Before you commit, verify three things: that a RunUAT BuildPlugin pass against your exact 5.7 install succeeds, that npm install completes in Resources/mcp-bridge, and that the MIT badge in the README matches the LICENSE file in the repository you cloned.
Community notes