VibeUE: Unreal Engine Vibe Coding Tool VibeUE, an MCP Expansion and AI Editor Toolset for Unreal Engine 5.8+, adds deep editor capabilities including terrain, audio, animation, Niagara, UMG, Blueprint authoring, and a PerformanceService for diagnosing frame rate issues. The tool complements Unreal's native AI toolsets by focusing on domains the engine does not cover, such as real-world terrain from GPS, Custom-HLSL scratch-pad modules, and performance profiling with Unreal Insights trace analysis. A free API key unlocks real-world terrain tools; everything else works without one. VibeUE is the MCP Expansion + AI Editor Toolset for Unreal Engine 5.8+. Unreal 5.8 added a built-in MCP server and AI toolsets; VibeUE is an MCP Expansion that plugs straight into them and adds a deep AI Editor Toolset — a library of editor capabilities — Blueprints, materials, landscape, foliage, animation, Niagara, UMG, audio, StateTree, gameplay tags, input, UVs, performance/profiling , and more — registered into the engine's own ToolsetRegistry and ModelContextProtocol server, plus rich domain skills served through Unreal's native AgentSkill system. Any MCP-capable agent Claude Code, Cursor, Copilot, … drives your editor through Unreal's standard MCP endpoint. ⚠️ VibeUE requires Unreal's native MCP to be set up first— enable theUnreal MCPplugin which auto-enablesToolset Registry and theEditor Toolsplugin, then start the MCP server. Follow Epic's guide:. VibeUE then expands that endpoint — Unreal MCP in the Unreal Editor no separate server and no in-editor chat.A free API key set inEditor Preferences → Plugins → VibeUE unlocks the real-worldterraintools; everything else works without one. Unreal 5.8 ships its own AI toolsets Blueprints, materials, actors, assets, meshes, data tables, … . VibeUE complements them — it focuses on the domains and depth the engine doesn't cover: Terrain & world — Landscape sculpting/heightmaps/splines, landscape auto-materials + RVT, Foliage, procedural FPS Map Blockout , and real-world terrain heightmaps + water from GPS . Audio — MetaSound and SoundCue graph authoring. Animation assets — AnimSequence keyframe editing, AnimMontage authoring, AnimBP state machines, Skeleton bone/socket/retarget/blend-profile editing. FX depth — Niagara emitter color/curve authoring and Custom-HLSL scratch-pad modules. UI — UMG widgets with MVVM bindings, animation authoring, and preview/PIE validation. Higher-order Blueprint authoring — timelines, event dispatchers, delegates, custom-event pins, comment boxes, and a batch build graph builder. Editor safety — TransactionService wraps the editor's transaction buffer undo / redo / checkpoints so an agent can group and roll back its own edits — the engine's toolsets expose none. ⚡ Performance & profiling — VibeUE's standout: see the dedicated section below. Python-first access — run any unreal. Python in the editor and introspect the whole API. Web research — search / fetch / geocode for in-context research and terrain workflows. It deliberately does not duplicate the engine's general tools basic asset/actor/blueprint/material CRUD, screenshots, logs, PIE — agents use Unreal's native toolsets for those. Unreal's native AI toolsets have zero performance tooling — they can start PIE/Simulate but can't measure anything. VibeUE's PerformanceService fills that gap so an agent can actually diagnose and fix frame rate: — Game/Render/GPU/RHI thread split + a frame timing CPU-vs-GPU-bound verdict and a concrete next-step hint. Run this first — optimising the GPU does nothing on a CPU-bound frame. Unreal Insights capture — start trace / stop trace / get trace status , with bookmark and region start / region end markers.— reads the trace analyse and log back and returns a perf summary frame stats, worst frames, hitches, notable log lines . Trace-attached — profile a representative standalone build, not just the editor viewport. start standalone python import unreal print unreal.PerformanceService.frame timing CPU vs GPU bound — diagnose FIRST unreal.PerformanceService.start trace "cap", "" Insights trace … reproduce the workload ideally under PIE / standalone … unreal.PerformanceService.stop trace print unreal.PerformanceService.analyse "both", "" Pair with the profiling and frame-rate skills for the full CPU/GPU drill-down. VibeUE plugs into three native UE 5.8+ systems: Toolsets ToolsetRegistry — VibeUE's services register as UToolsetDefinition s, so their methods become AICallable tools on the MCP endpoint. They're also BlueprintCallable , so the same methods are callable from Python as unreal.