NAJEMWEHBE/unreal-ai-connection

> **DEPRECATED — this project is no longer maintained** (deprecated 2026-07-17; active development stopped 2026-07-03, when the maintainer moved to Epic's native plugin for this workflow). No further features, fixes, releases, or PR/issue responses are promised.
>
> **Last-known-good state:** UE **5.7** officially supported & tested (source build); UE **5.6** via the prebuilt v0.9.1-ue5.6 release. Other UE versions remain best-effort via the kept compat scaffold (ADR-0001), untested.
>
> **Toolchain note:** the maintainer's BuildConfiguration.xml pin stays **cleared** (see the 36th closing note in docs/HANDOFF.md) — UE **≤5.3** source builds require re-pinning an engine-appropriate MSVC toolchain yourself. No new build promises on any version.
>
> The code stays up under the MIT license — forks welcome. Full deprecation record: the 37th closing note.
Unreal AI Connection
**Drive Unreal Engine 5.7 from any MCP-compliant client over a local TCP socket.**
151 tools total. Zero pixel-clicking. ~50ms round-trip.
-313131?logo=unrealengine)
*Live capture — an MCP client builds the scene, places **Niagara FX** (spawn_niagara_at_location), and orbits a camera, entirely over the local TCP socket. Reproduce with scripts/capture_demo_gif.py.*
**Native C++ handlers — not Python Remote Execution.** ~50 ms round-trips across 149 tools · 637 tests · MIT · works with any MCP-compliant client (Claude Code, Cursor, Cline, Codex, Gemini, Continue, Windsurf, Zed, …).
The suite now spans **inspection and authoring** — read existing assets and *create* them: actors, levels, data tables/assets, Blueprints (incl. K2 graph nodes), material graphs, **Niagara FX, Level Sequence cinematics (camera cuts, audio, visibility), and Movie Render Queue renders** — all over the same socket.
⭐ **If this saves you time, a star helps other devs find it.**
Authoring high-quality assets: see docs/ASSET-PIPELINE-BLENDER.md.
---
Install (one paste, any client)
> **Every route below only wires the stdio bridge.** You must separately install the UE 5.7 plugin into your project's Plugins/ folder and launch the editor (it binds 127.0.0.1:18888). See docs/setup/README.md for the prerequisite, and docs/DISTRIBUTION.md for how this is published.
**Claude Code** — paste the owner/repo, no clone needed:
**Cursor** — one-click deeplink. Base64-encode your machine's bridge path into this template:
where is base64 of {"command":"python3","args":["/ABSOLUTE/PATH/TO/bridge/unreal_ai_connection_bridge.py"]} (on Windows use "command":"py" if python3 is not on PATH). Manual fallback — .cursor/mcp.json:
**VS Code** — install deeplink (URL-encode the JSON for your path):
> **Windows:** all snippets use python3; if that's not on PATH use the py launcher instead ("command": "py"). The .claude-plugin/mcp-config.json marketplace path uses python3 for cross-platform consistency — Windows users without python3 should use the manual per-client recipe in docs/setup/ with py.
**Every other client** — copy-paste recipe per client:
| Client | Route | Recipe |
|---|---|---|
| Claude Code | /plugin marketplace add NAJEMWEHBE/unreal-ai-connection | docs/setup/claude-code.md |
| Claude Desktop | edit claude_desktop_config.json | docs/setup/claude-desktop.md |
| Cursor | deeplink / .cursor/mcp.json | docs/setup/cursor.md |
| Codex CLI | codex mcp add unreal-ai-connection -- … | docs/setup/codex-cli.md |
| Windsurf | mcp_config.json | docs/setup/windsurf.md |
| Continue | ~/.continue/config.yaml | docs/setup/continue.md |
| Cline | MCP Marketplace tab / settings | docs/setup/cline.md |
| Zed | ~/.config/zed/settings.json | docs/setup/zed.md |
| Gemini CLI | ~/.gemini/settings.json | docs/setup/gemini-cli.md |
| VS Code Copilot | .vscode/mcp.json | docs/setup/vscode-copilot.md |
Also discoverable in the official MCP Registry as io.github.najemwehbe/unreal-ai-connection (feeds the VS Code MCP gallery, mcp.so, PulseMCP) and submittable to the Cline marketplace via llms-install.md.
---
Jump to
- How it fits together — architecture diagram + per-call sequence
- Why it exists — the UE 5.7 Python dead-ends this plugin sidesteps
- Why MCP specifically — one protocol, every conforming client
- Tools — 147 tools grouped into 15 expandable categories
- Quick start — copy-paste path to a running editor with the plugin live
- What's in the box — directory tree
- Status — release / test / build state
- Contributing — house rules + how to add a tool
- License
---
How it fits together