The project

One maintainer, six months, the whole editor.

UE-MCP is an open-source bridge between AI assistants and the Unreal Editor. It is MIT licensed, free in any project, and built in public. This page is the record behind it: who writes it, what has shipped, and what the next stretch of work is.

Maintainer

David Bingham

db-lyon

Sole maintainer. Eight people have contributed code; 1,452 of the commits are mine. Issues, the Discord, releases, documentation, and the plugin registry are all run by one person, which is the constraint this project is currently shaped by.

GitHub →Discord →hello@ue-mcp.com →
1,503
Commits
since 23 February 2026
238
Releases
roughly one every 18 hours
270
Test files
including a live-editor tier
8
Contributors
one maintainer

Contributors

Alexander Kenley
alexkenley · 29 merged
Cyber Security & Software Engineering
  • UE 5.5 and UE 5.8 bridge compatibility
  • Codex client setup, editor startup and reconnection hardening
  • Blueprint, asset-property, socket, CurveTable and StringTable tooling
  • Live skeletal and spatial queries, animation and contact authoring
  • Live-editor regression coverage

Contributed and want to be listed? hello@ue-mcp.com

Why it exists

The barrier to Unreal is not imagination.

It is the distance between knowing the result you want and knowing which of ten thousand editor affordances produces it. That distance is measured in years, and it is why so many people who could make something with Unreal never get past the first week.

UE-MCP shortens it. Describe the result, and the editor does the work: place the actors, wire the Blueprint, author the material, rebuild the navmesh, run it. Every action is a real editor operation with real undo, so what comes back is a project the person owns and can keep editing by hand.

That matters most to the people with the least runway. Students, solo developers, educators building a course, and small teams without a tools programmer are exactly who this is for, and exactly who cannot pay for it. It stays MIT.

Where it is today

Shipped, installed, in use.

16k
Installs / month
npm, last 30 days
271
GitHub stars
54 forks
1100+
Actions of its own
across 26 tool categories
830
Epic 5.8 tools wrapped
52 official toolsets, inside the 1930 total
4
Third-party plugins
published to the registry
UE 5.4-5.8
Engine support
Windows, macOS, Linux

Install and star counts are read live from npm and GitHub. Repository figures are as of August 2026.

Alignment with the engine

Built on the platform's own direction.

Unreal 5.8 ships an AI Toolset Registry, the plugin behind the editor's own MCP server. UE-MCP does not compete with it. On 5.8 it reaches that registry in-process and re-surfaces all 830 official tools as first-class actions, in the same categories as its own 1100, so a user gets the first-party surface and this one together, through a single connection.

Every hour spent here compounds the engine's investment in agentic tooling rather than duplicating it, and everything produced is open source under MIT, for anyone in the real-time 3D ecosystem to use, fork, or extend.

Every wrapped tool →How it compares →
Where it goes next

Four things funding changes.

Each of these is a known gap rather than a wish. Three of them are bounded engineering; one of them is machines. All four widen who can use the engine at all.

01

Remove the C++ toolchain requirement

The bridge is a C++ plugin that compiles on first editor launch, so today it needs Visual Studio or Xcode and a C++ project. That is the single largest barrier between a stock machine and a working install, and it falls hardest on students, artists, and educators. Precompiled per-engine binaries and a Blueprint-only path remove it.

02

Turn flows into an open curriculum

Flows are already deterministic, inspectable, repeatable multi-step runs, and the bundled 19-step demo builds a complete scene from an empty level. That mechanism is also a lesson format: run a step, read exactly what it did to the project, change it, run it again. The work is authoring that curriculum per subsystem, with an instructor path and recorded walkthroughs.

03

Engine parity, verified against real builds

5.4 through 5.8 are supported today, and each engine release moves the surface underneath every handler. The suite is 270 test files, but the live tier needs a running editor, which needs machines. Continuous verification against real engine builds, per version, is a hardware cost rather than a code problem.

04

Keep the surface extensible by other people

Four third-party plugins are published today, covering PIE recording and replay, Perforce, voxel terrain, and generative asset creation. Authoring documentation, templates, and review time are what turn four packages into an ecosystem that does not depend on one person.

Supporting the work

It is free. It is not costless.

The engine builds, the test hardware, and the hours all come from one person. Sponsorship, contributions, and gap reports from real sessions are what set the order of the list above.

Sponsor →Open an issueGet in touch