All AI tools for Unreal Engine / CodeFizz Editor Agent vs Unreal MCP

Checked 7 October 2026

CodeFizz Editor Agent vs Unreal MCP

Unreal MCP is free and comes from Epic, but it is Experimental and only in Unreal Engine 5.8. CodeFizz Editor Agent is a paid product for 5.6, 5.7 and 5.8. It can create and edit StateTrees, covers Enhanced Input, records and reads Unreal Insights traces on 5.7 and 5.8, and drives the Blueprint debugger and the Niagara Debugger. If you are on 5.8 and the Experimental label is fine for your work, start with Epic's tool. Pick CodeFizz when you need 5.6 or 5.7, or the areas Epic's toolsets do not cover.

Side by side

Fact	CodeFizz Editor Agent	Unreal MCP
Price	From $19.99 a month. Three day free trial with no card. A one-time Lifetime option is also offered.	Part of Unreal Engine 5.8. Epic sets no separate price for it.
Unreal versions	5.6, 5.7 and 5.8, all on the same release	5.8
Runs on	Windows	Not stated by Epic
Who runs the AI	Your own agent and the AI plan you already pay for: Claude Code, Cursor, Gemini CLI, Codex or any MCP client. CodeFizz sells no AI credits.	Your own agent. Epic names Claude Code, Cursor, VS Code, Gemini and Codex.
Published size	1400+ commands across 37 categories, of which 43 only check results.	No number given. Epic's docs speak of hundreds of tools in the registry.

"Published size" is the number each vendor states, in its own unit. A tool is not the same size in every product, so do not judge by that row alone.

Choose CodeFizz Editor Agent when

You work on Windows, you want depth in Niagara, Sequencer, Control Rig, PCG and StateTree, you want the agent to profile and debug as well as build, and you want to use the AI agent you already have.

Choose Unreal MCP when

You are on 5.8, you want something free that comes from Epic, and an Experimental feature is fine for your work.

What CodeFizz Editor Agent does besides build

Making an asset is the easy part. The real work starts when the frame rate drops, an effect shows nothing, or an enemy stands still. These are six jobs CodeFizz Editor Agent gives your agent for that, each with a question you might ask.

Find what makes the game slow

You ask: "Why does this level drop to 40 frames a second?"

The agent records an Unreal Insights trace while the game runs, then reads it for you. It names the worst frames, the functions that cost the most time and the GPU passes that take the longest. It can also switch one console variable on and off and report the difference in frame time, GPU passes and CPU timers.

Needs Unreal Engine 5.7 or 5.8.

Commands: performance_start_trace, performance_analyze_insight, performance_profile_gpu, performance_ab

Debug a Blueprint step by step

You ask: "Why does the door not open when I press E?"

The agent puts a breakpoint on a node and starts the game. When play stops at that node, it reads the call stack and the values on the object, then steps forward one node at a time. It can also watch a pin and list the nodes that ran last. This is the Blueprint debugger you already know, with the agent at the controls.

Commands: set_breakpoint, debug_step, get_call_stack, inspect_debug_value, set_pin_watch

Look inside a running Niagara effect

You ask: "Why do no particles show, and why is this effect so expensive?"

The agent reads the live particle count and the values on each particle, the same data the Attribute Spreadsheet shows. It can pause, step or slow down every effect, and it measures what one system costs on the game thread, the render thread and the GPU. If the stack has errors, it reads them and can apply the fix that the Fix issue button in the editor applies.

Commands: get_niagara_particle_stats, get_niagara_particle_data, set_niagara_debug_playback, profile_niagara_system, fix_niagara_stack_issue

See why an AI character does what it does

You ask: "Why is the enemy standing still?"

During play, the agent reads the Behavior Trees that are running and can pause the game when a tree reaches a node you name. It runs an Environment Query and returns the engine's own debug view of the result. On Unreal Engine 5.8 it also reads live Mass entities and the values they hold.

Commands: get_bt_runtime, set_bt_breakpoint, run_env_query, get_mass_entity

Test a rig before an animator touches it

You ask: "Does the cloak cut through the body when the character runs?"

The agent runs the rig for as many frames as you ask, with no window open. It reports limbs that cross, feet that go through the ground, bones that shake, and how deep one mesh goes into another. It also tells you how long the rig takes to solve and which nodes cost the most.

Commands: simulate_rig, measure_mesh_penetration, get_rig_motion_report, profile_rig

Read and explain what is already in the project

You ask: "What does this material do, and what does it cost?"

The agent reads the graph and follows a wire from any node to where it ends. It reports the shader cost numbers that the engine itself shows. For PCG it reads the data that comes out of a single node. It can take a screenshot of the viewport or of an editor window, so you and the agent look at the same picture.

Commands: trace_material_connection, material_stats, pcg_inspect_node_output, take_screenshot

Job by job: CodeFizz Editor Agent and Unreal MCP

CodeFizz Editor Agent states all 8 of the jobs past building. Unreal MCP states 1 of them on its own pages. The part named "Where other tools lead" is where CodeFizz Editor Agent says No.

Job	CodeFizz Editor Agent	Unreal MCP
What it builds
Blueprints	Yes57 commands	Yes53 tools
Materials	Yes52 commands	Yes35 tools
Niagara	Yes135 commands	Yes56 tools
PCG	Yes100 commands	Yes31 tools
Sequencer	Yes220 commands	Yes140 tools
Control Rig	Yes165 commands	Yes116 tools
Animation Blueprints	Yes56 commands	No
UMG widgets	Yes54 commands	Yes23 tools
Behavior Tree and EQS	Yes36 commands	Noreads only
StateTree	Yes42 commands	Noreads only
Enhanced Input	Yes21 commands	No
Gameplay Ability System	Yes25 commands	Yes14 tools
Audio and MetaSound	Yes40 commands	No
IK Rig and retargeting	Yes32 commands	Not stated
Landscape, foliage and world	Yes55 commands	Not stated
Mass entities	Yes19 commands, UE 5.8	No
Mutable characters	Yes36 commands	Not stated
Jobs past building
Profiles the game and names what is slow	Yes5.7 and 5.8	No
Sets Blueprint breakpoints and reads values at a stop	Yes	No
Reads a running Niagara effect	Yescounts and values	No
Reads AI state during play	YesBehavior Tree	No
Test-runs a rig with no window open	Yes	No
Starts the game and reads screenshots or logs	Yes	Yes
Has checks that only report, with a pass or fail	Yes43 checks	Not stated
Takes back a change through undo or rollback	Yesa failed step is undone	Not stated
Where other tools lead
Runs on macOS	No	Not stated

Yes means the vendor states it on its own pages. Not stated means we did not find it there on 7 October 2026. It does not mean the product cannot do it. No means the vendor says so, or for Epic's Unreal MCP that the 5.8.3 engine source has no such tool. A number is the count that vendor publishes for the area, in its own unit, and Epic's numbers were counted in the 5.8.3 engine source. A tool is not the same size in every product, so read a number as a rough guide to depth and not as a score.

Sources: Aura performance profiling, Aura verification agent, NeoStack changelog, Ultimate Engine CoPilot updates, Ultimate Engine CoPilot features, Nwiro tool reference, Nwiro changelog, StraySpark tool list, Rekall product page, ClaudeUnreal home.

One fact we could check in source: in Unreal Engine 5.8.3, the toolsets of Epic's Unreal MCP have no tool for Blueprint breakpoints, for Unreal Insights traces, or for the Niagara Debugger.

Watch CodeFizz Editor Agent work

The only public benchmark of these tools uses five kinds of work: Niagara, Material, Level design, UMG widget, Animation Blueprint. Its prompts are not published, so we give no score. Here is one video of CodeFizz Editor Agent for each of the five, from the prompt to the result in the editor.

Niagara