UnrealClaude: Claude Code inside the Unreal Engine 5.7 editor

The gap UnrealClaude fills between Claude Code and the UE 5.7 editor

Claude Code is a terminal tool. Unreal Engine 5.7 is a GUI application with its own asset model, and the two do not naturally meet. You can point Claude Code at a C++ source tree and get useful answers, but it has no way to open a level, inspect a Blueprint graph, or query which assets reference a material. UnrealClaude closes that gap by running inside the editor. The README describes a chat panel docked in the editor with streaming responses, tool call grouping and code block rendering, plus an MCP server that other coding agents can call. The intended user is a UE developer who already has a Claude subscription and wants the assistant to act on the project rather than only talk about it. The project targets Unreal Engine 5.7 specifically, with Windows, Linux and Apple Silicon macOS listed as supported platforms, and it states that Claude Opus 4.7 and its Claude Code release are supported.

How the MCP bridge and the dynamic UE 5.7 context loader actually work

The architecture visible in the repository is two-layer. The first layer is a C++ editor plugin, UnrealClaude.uplugin, which provides the docked chat panel and the editor-side operations. The second layer is a Node.js MCP bridge that lives under Resources/mcp-bridge and is pulled in as a git submodule. The README lists more than 20 Model Context Protocol tools covering actor manipulation, Blueprint editing, level management, materials and input, and it says the bridge includes a dynamic context loader that supplies UE 5.7 API documentation on demand rather than embedding a fixed corpus. That choice matters: engine APIs move between releases, and loading documentation at call time is how the project claims accuracy for 5.7 specifically. Requests flow from the chat panel to the bridge, which calls editor operations; long-running work goes through an async task queue so operations do not time out. The plugin also gathers project context automatically, including modules, plugins and assets, and the README states it can see editor viewports. Authentication is delegated entirely to Claude Code, so there is no separate API key to manage inside Unreal.

Installing Claude Code and building the plugin from source

There are no prebuilt binaries. The README is explicit that the plugin must be built from source for your platform and engine version, which means you need a working Unreal installation with its build tooling. Start with the CLI, since the plugin depends on it.

npm install -g @anthropic-ai/claude-code
claude auth login
claude --version

The login opens a browser window to authenticate against an Anthropic account, either a Claude Pro or Max subscription or API access. The version check should print a version string; if the command is not found, the plugin will have nothing to call later.

Clone the repository with its submodule. Skipping the submodule flag is a common mistake and the README gives the recovery command.

git clone --recurse-submodules https://github.com/Natfii/UnrealClaude.git
cd UnrealClaude
git submodule update --init

Build with Unreal's automation tool. On Windows the command takes the .uplugin path and an output directory.

Engine\Build\BatchFiles\RunUAT.bat BuildPlugin -Plugin="PATH\TO\UnrealClaude\UnrealClaude\UnrealClaude.uplugin" -Package="OUTPUT\PATH" -TargetPlatforms=Win64

Linux and macOS use RunUAT.sh with the same arguments and TargetPlatforms set to Linux or Mac. Then copy the build output into your project's Plugins directory or into the engine's Marketplace plugins folder, and install the bridge dependencies.

cd <PluginPath>/UnrealClaude/Resources/mcp-bridge
npm install

Launch the editor and the plugin loads automatically. On macOS the README points to Tools > Claude Assistant to open the panel. If the plugin does not appear in the plugin browser, the README notes that it lives under the Editor category and may need scrolling rather than search.

Blueprint editing is the weakest part of the feature list

The README's own parenthetical is the most useful line in the document: Blueprint editing, including Animation Blueprints and state machines, carries the note "Few bugs still, don't rely on fully." Treat that as the project's assessment, not a hedge. If your work is mostly C++ with occasional asset queries, the MCP tools for actors, levels and asset dependency lookups are the parts you will lean on, and they are described without caveats. If your work is Blueprint-heavy, the tool that would help most is the one the maintainers flag as unreliable. There is a second constraint: the plugin is tied to UE 5.7. The README names 5.7 in the title, in the badge and in the context loader. A studio on 5.4 or 5.5 has no documented path here, and the dynamic context loader exists precisely because API documentation is version-specific, so retargeting it is not a config change. Third, the repository has no LICENSE file at the top level even though the README badge reads MIT, so the actual grant is unverifiable from the tree.

How UnrealClaude differs from a plain MCP server or a terminal-only workflow

The obvious alternative is running Claude Code in a terminal beside the editor and pointing it at your project directory. That approach needs no plugin build, no Node bridge and no UE version match, and it will still read and write C++ and config files. What it cannot do is act on the editor: no opening levels, no querying referencers, no viewport visibility. UnrealClaude's value is entirely in that editor-side surface. A second comparison is a standalone Unreal MCP server used from an external agent. That keeps the agent outside Unreal and connects over the protocol, which suits teams that want one agent session covering several tools. UnrealClaude inverts this by making the editor the host and the chat panel the primary interface, with the MCP server exposed for other agents as a secondary path. The trade-off is that you now maintain a compiled plugin inside your engine version, and every engine upgrade is a rebuild rather than a dependency bump.

Maintenance cadence, upgrade burden and the licence question

The last push to the repository was on 2026-06-26, the same day as the v1.5.1 release. Before that, v1.5.0 landed on 2026-05-14 and v1.4.5 on 2026-05-04, so the release history shows a steady stream of small versions rather than long silences. The repository is not archived. That cadence is worth weighing against the cost of adopting a source-built plugin: each engine upgrade and each plugin version means re-running the BuildPlugin command and recopying output into your project or engine plugins folder. Because the MCP bridge is a submodule with its own npm dependencies, an update also means re-running npm install under Resources/mcp-bridge. On licensing, the README badge says MIT but the repository root contains no LICENSE file, and the description field carries no licence. If you need a clear legal position before shipping, that absence is the thing to resolve with the maintainer rather than assume.

Editorial conclusion

Adopt UnrealClaude if you already pay for Claude Pro or Max, work on Windows or Apple Silicon macOS, and are comfortable building a plugin from source with RunUAT. Skip it if you need prebuilt binaries, a stable Blueprint editing workflow, or a licensed product with published terms, since the repository carries an MIT badge but ships no LICENSE file. Before committing a project, verify three things: that claude --version resolves on the machine running the editor, that the mcp-bridge submodule was actually cloned with --recurse-submodules, and that the Blueprint tools behave on your own assets rather than on the demo content.

Frequently asked questions

Official sources

1. Issues
2. Natfii/UnrealClaude on GitHub
3. README
4. Releases