How ue-mcp compares.

Leads on breadth, orchestration, and extensibility. Only tool with a YAML flow engine, per-step rollback, and a three-shape plugin system (inject into built-ins, provide new top-level categories, or ship native C++ via a versioned bridge ABI). Covers the full editor surface including levels, gameplay systems (AI, GAS, StateTree, networking), landscape, PCG, foliage, audio, and UI. Ships a first-class PIE Record/Replay system with per-frame drift reports, multi-client recording, Take Recorder lockstep, offline diff, and per-frame PNG capture.

The cleanest drop-in: precompiled, Blueprint-only friendly, auto-updater. Strong on Blueprints, materials, animation, Niagara, and engine source. No level or gameplay authoring.

The only commercial hosted option with an in-editor agent panel. Solid scene and Blueprint coverage and 15k API docs lookup. Paid tiers gate the higher-value tools.

The original community reference, explicitly marked experimental. Coverage stops at basic actors, Blueprints, and a thin slice of materials.

One tier above chongdashu with broader Blueprint, material, and Behavior Tree coverage.

The no-plugin option: anything Python can do in UE, this can do, but everything routes through Python Remote Execution rather than typed tools.

Go single-binary option focused on headless builds, tests, and docs lookup. Editor coverage exists but is narrower than C++ plugin tools.

Condenses actions onto 22 parent tools to save context. Mid-breadth on engine systems, no gameplay framework depth.

Source analysis only. Cannot drive the editor. Useful alongside any of the above.

Forked HTTP REST plugin (37 tools, 200+ operations) with deep animation, montage, blend space, and IK retargeter coverage plus a built-in PIE record/replay system for deterministic debugging. UE 5.7 only. Pitches itself as a debugging and analysis tool rather than a prompt-to-game generator.

When the AI hits a missing tool or an incomplete action, the feedback loop catches it and files the gap automatically. Tool coverage doesn't wait for a maintainer to notice — it closes itself.

Deterministic YAML flows let you lock down multi-step operations into repeatable sequences. The model follows the script instead of improvising — fewer hallucinations, less token waste, predictable results every run.

Build custom tools on top of ue-mcp without forking or touching core. Ship a plugin that injects new actions, adds entire categories, or registers native C++ handlers — and install it with a single CLI command.