12 Free Unreal GenAI MCP Checks Before You Wire Agents - 2026

If you searched unreal genai mcp after UE 5.7 AI chatter and the community surge around UnrealGenAISupport (hundreds of GitHub stars; MIT GenAI + MCP bridge for Claude Desktop, Claude Code, and Cursor), you do not need another “agent builds the level overnight” reel. You need a numbered free preflight kit before any MCP client gets write-shaped tools against an Editor that still owns your shipping maps.

UnrealGenAISupport is a third-party plugin: LLM/GenAI APIs plus an MCP path aimed at UE 5.4–5.7+. The README itself says this free plugin’s MCP support is not being actively developed, points at Epic’s official Unreal MCP in Unreal Editor for 5.8+, and carries a hard caution that MCP lets the client control your project. Missing from the SERP is a Discord-pasteable pass that forces lab quarantine, localhost:9877 honesty, API key hygiene, MCP freeze awareness, and NO_LIVE_AGENT before anyone wires main.

This listicle owns the free kit for UnrealGenAISupport MCP / GenAI agent wiring. It is not the 12 free Unreal MCP agent safety tools after UE 5.8 (Epic Experimental Unreal MCP toolkit). It is not the Cursor safe session worksheet or Claude Code first safe session. It is not the loopback expose Stop. It is not the Unity MCP 1.5 checks cousin. Those own Epic 5.8 MCP, worksheets, network refusal, and Unity. This URL owns UnrealGenAISupport preflight checks.

Why this matters now

UE 5.7 release discussion (forums thread) plus months of GenAI plugin FOMO pushed indie leads to “just add the MCP JSON.” Connected ≠ safe. Stars ≠ production pin. A plugin that can spawn actors, run Python, and fire console commands inside your Editor is a build input with blast radius, not a Discord emoji.

Direct answer: Run checks 1–4 before you submodule the plugin into anything that matters. Run 5–9 on a disposable lab project with loopback + secret hygiene. Run 10–12 before any agent may write on a branch that ships. If check 11 fails (no NO_LIVE_AGENT latch), stop — that is the point of the kit. Authority: UnrealGenAISupport README + Epic’s Unreal MCP docs for lane clarity.

Who this list is for

Time: 25 minutes for 1–4; 2–3 hours for a full lab smoke.
Honest limit: Free-plugin MCP is frozen-ish per README; Epic’s 5.8 Unreal MCP is a different radio. Re-read both before you promise partners “we have Unreal MCP.”

Non-repetition

Four-check minimum (if you only have twenty-five minutes)

Do not enable MCP clients on a shipping Editor until these four are green.

Selection criteria (how a check earned a slot)

A check is in only if all of these are true:

1. Free — no paid SaaS required to pass.
2. Primary job is safe GenAI/MCP enablement — install, contain, verify, or refuse — not a random Blueprint tip.
3. Grounded in UnrealGenAISupport README, Epic MCP docs, or UE community release reality.
4. Honest limits can be stated in one sentence.
5. Useful before first agent write on a real map.

GenAI vs MCP vs Epic Unreal MCP (cheat sheet)

Mixing lanes without a receipt is how teams debug the wrong port for two days.

The twelve checks

1. Docs latch (README caution + freeze)

Do: Open UnrealGenAISupport. Read the MCP section, the CAUTION that MCP lets Claude/Cursor control the project, and the note that MCP in this free plugin is not being actively developed. Skim Epic’s Unreal MCP page so you know the official 5.8 lane exists.

Pass: Ticket links README + Epic docs; freeze note quoted.
Fail: “Stars mean production-ready MCP.”
Next: Keep both URLs in the agent prompt footer.

2. Lab project quarantine

Do: Clone or copy a throwaway Unreal project (UE-GenAI-MCP-Lab-YYYYMMDD). Do not point Claude Desktop / Cursor MCP config at the only shipping .uproject. Backup or use Git before first connect — the README already says to backup and use VCS.

Pass: Lab path on the receipt; shipping project not in the client’s default MCP args.
Fail: “We’ll revert git later.”
Next: Same instinct as Epic MCP worksheets — copy first.

3. Engine lane pin (5.4–5.7 GenAISupport vs 5.8 Epic)

Do: Record your Editor version. If you are on 5.8+ and only wanted official Unreal MCP, prefer Epic’s plugins + safety tools listicle instead of wiring this community MCP “because the repo is popular.” If you are on 5.4–5.7, GenAISupport MCP is the lane this kit targets — still lab-only.

Pass: One written lane: GenAISupport_MCP or Epic_Unreal_MCP or other, never “all of them tonight.”
Fail: Both MCP servers enabled “to compare live on main.”
Next: Dual-wire only on a second lab machine with a written experiment ticket.

4. NO_LIVE_AGENT latch

Do: Write a one-line policy: No MCP client may target shipping AppID / release branch Editors. Paste it in Discord and the project README. Shipping maps stay human-driven until a numbered exception list exists.

Pass: Policy visible; exception list empty or dated.
Fail: “The agent is just helping with lighting.”
Next: Treat exceptions like mid-fest Unity pins — rare, owned, timed.

5. Install path honesty (submodule / Plugins folder)

Do: Install via the README’s documented path (commonly Plugins/GenerativeAISupport via submodule or copy). Record the commit SHA you pinned. Do not “download a zip from a random mirror.” Enable the plugin in the Editor plugins browser; rebuild if required.

Pass: Path + SHA on the receipt; plugin shows enabled.
Fail: Mystery binary in Engine/Plugins with no provenance.
Next: If packaging fails with missing modules, see plugin not found help — and keep MCP out of shipping cooks unless you intentionally exclude it (README mentions excluding MCP from build).

6. MCP client config path (mcp_server.py args)

Do: Point Claude Desktop / Cursor / Claude Code at the plugin’s mcp_server.py (path under your project’s Plugins tree per README). Wrong absolute path is the #1 “MCP not connecting” self-own. Prefer machine-local absolute paths in lab; do not commit teammate-specific paths into a shared repo without a template.

Pass: Config JSON opens; args resolve to an existing file.
Fail: Copied a tutorial path from another disk letter.
Next: Restart the MCP client after every path change.

7. Loopback pin (UNREAL_HOST / UNREAL_PORT)

Do: Keep env defaults honest: UNREAL_HOST=localhost and UNREAL_PORT=9877 (per README examples) unless you have a written lab reason to change the port. Do not bind MCP for LAN “so the contractor can help.” Do not Cloudflare-tunnel Editor control for vibes.

Pass: Config shows localhost; no public URL in env.
Fail: 0.0.0.0 or a tunnel hostname “just for tonight.”
Next: For Epic 5.8 MCP network refusal patterns, see the loopback Stop — same instinct applies here.

8. API key hygiene (GenAI features ≠ MCP config)

Do: Separate concerns. MCP is Editor control. GenAI API keys (OpenAI, Anthropic, etc.) power chat/NPC/TTS features. Store keys in Editor settings / local secrets / CI secret stores — never commit keys into mcp JSON, .uproject, or Discord screenshots. Rotate any key that was pasted into a ticket.

Pass: Keys absent from git git grep for common provider prefixes; receipt says where secrets live.
Fail: “We put the key in the MCP env block for convenience.”
Next: Company diligence: who can mint keys, who can enable MCP.

9. Editor handshake smoke (server up before client tools)

Do: With the lab project open, ensure the plugin’s Unreal-side socket/server path is running as documented (README references running the Unreal socket server side in-Editor). Only then connect the MCP client. Confirm a read-shaped tool list or a harmless inspect before any spawn/move/Python.

Pass: Client sees tools; first action is read-only or explicitly lab-scoped.
Fail: Client connected while Editor was closed; “retry until something moves.”
Next: Log Output Log / Python console errors into the receipt.

10. Blueprint MCP honesty (nodes still buggy)

Do: Treat Blueprint auto-generation — especially node connections — as 🛠️ / buggy per the README status table and open issues (e.g. EventGraph node GUID/connect failures). Lab experiments only. Do not promise producers “Claude will finish the ability graph tonight.”

Pass: Scope card says “no production BP graph MCP writes.”
Fail: Demo day depends on MCP wiring BeginPlay graphs.
Next: Use MCP for spawn/transform lab demos; keep critical graphs human.

11. Write-tool gate (NO_LIVE_AGENT enforcement)

Do: Before enabling spawn / transform / Python / console-command tools on a map you care about, re-check checks 2 and 4. Prefer a blank lab level. Disable or refuse write tools in the client when the Editor has the shipping map open.

Pass: Write tools only while lab map + NO_LIVE_AGENT green.
Fail: Shipping Persistent Level open + agent has Python.
Next: If you need automation on shipping content, use human-reviewed scripts offline — not live MCP.

12. Exit / uninstall / lane revisit

Do: End the evening with: MCP client disconnected, Editor closed or plugin disabled if not needed daily, receipt filed, and a lane revisit date (e.g. when you move to UE 5.8 official Unreal MCP). Do not leave a forgotten Claude Desktop config pointing at last month’s shipping path.

Pass: Disconnect noted; revisit date set.
Fail: Config still targets D:\Ship\Main after the lab demo.
Next: Quarterly delete stale MCP server entries.

Beginner path (first evening)

1. Read check 1 (README caution).
2. Make a lab copy (check 2).
3. Write NO_LIVE_AGENT (check 4).
4. Install plugin on the lab only (check 5).
5. Wire localhost:9877 (checks 6–7).
6. Connect client; ask for a read-only confirmation (check 9).
7. Stop. Do not spawn fifty cubes into the shipping hub on night one.

Beginner done: You can refuse “just wire MCP on main” with a primary-source link.

Developer depth — receipt template

UNREAL_GENAI_MCP_PREFLIGHT_v1
date:
owner:
engine_version:
lane: GenAISupport_MCP | Epic_Unreal_MCP | other
plugin_commit_sha:
lab_project_path:
shipping_project_excluded: yes/no
mcp_server_py_path_ok: yes/no
UNREAL_HOST: localhost
UNREAL_PORT: 9877
keys_not_in_git: yes/no
mcp_freeze_acknowledged: yes/no
blueprint_mcp_scope: lab_only / refused
NO_LIVE_AGENT: yes/no
first_smoke: read_only / write_lab / fail
signer:

CI / ops notes

Creator Discord brief (paste)

12 free Unreal GenAI MCP checks before you wire agents:
1) README caution + MCP freeze  2) Lab project only
3) Pick ONE lane (GenAISupport vs Epic 5.8 MCP)
4) NO_LIVE_AGENT on shipping maps
5) Pin plugin SHA  6) mcp_server.py path real
7) localhost:9877 only  8) Keys out of git
9) Editor up before client  10) BP nodes = buggy/lab
11) Write tools only on lab  12) Disconnect + revisit date
Stars ≠ safe. Connected ≠ production.

Excuse ladder

Failure modes

Company / diligence four-liner

1. Fact: UnrealGenAISupport is third-party MIT GenAI+MCP; free MCP path is not actively developed per README; Epic ships separate Experimental Unreal MCP on 5.8+.
2. Control: Lab-only MCP; localhost; secrets out of git; NO_LIVE_AGENT on release Editors.
3. Limit: Blueprint MCP generation incomplete/buggy; not a cert substitute.
4. Evidence: Preflight receipt + plugin SHA + lane choice.

What to lock this week

1. Choose GenAISupport MCP or Epic 5.8 MCP — not both on shipping.
2. Create one lab .uproject.
3. Pin plugin commit SHA.
4. Write NO_LIVE_AGENT.
5. Scrub keys from repos.
6. Verify localhost:9877 only.
7. Run read-only smoke.
8. Ban production BP MCP demos.
9. File the receipt.
10. Set a lane revisit when upgrading engine.

Producer one-pager (paste into Notion)

Title: Unreal GenAI MCP — lab only
Can: Lab Editor + localhost MCP + read-first smokes.
Cannot: Shipping map writes; LAN tunnels; keys in JSON; dual MCP on main.
Owner: Tech lead.
Revisit: Engine upgrade to 5.8+ or plugin README MCP status change.

Comparison table (this kit vs cousins)

Key takeaways

1. Unreal genai mcp demand is real — still need a numbered preflight.
2. UnrealGenAISupport ≠ Epic Unreal MCP.
3. Free-plugin MCP is not actively developed — plan accordingly.
4. Lab project first; shipping Editor last.
5. localhost:9877 — no tunnels.
6. API keys are not MCP config candy.
7. Blueprint node MCP is buggy — lab only.
8. NO_LIVE_AGENT is a latch, not a vibe.
9. Pin plugin SHA like any dependency.
10. Pick one MCP lane per evening.
11. Read-only smoke before spawn storms.
12. Disconnect and revisit on engine upgrades.
13. Cousin kits exist for Epic 5.8 and Unity — link, don’t merge.
14. Stars measure interest, not diligence.
15. Receipt beats folklore.

FAQ

Is UnrealGenAISupport the same as Epic Unreal MCP?

No. GenAISupport is a community plugin (GenAI APIs + its own MCP path for ~5.4–5.7+). Epic’s Experimental Unreal MCP lives in 5.8+ editor docs. Choose a lane (check 3).

Is the free MCP production-ready?

The README states free-plugin MCP is not being actively developed and warns about project control. Treat it as lab. Pro Fab plugins are a separate commercial story — not required for this free checklist.

What port should we use?

README examples use UNREAL_PORT=9877 with UNREAL_HOST=localhost. Do not expose beyond loopback without a written security review (default answer: don’t).

Can Claude Desktop control my project?

Yes — that is the point of MCP, and the README caution. Backup, VCS, lab project, NO_LIVE_AGENT.

Should we use this on UE 5.8?

Maybe for GenAI APIs — but for MCP, evaluate Epic’s official Unreal MCP first. Dual-wiring both MCP stacks on a shipping map is a fail.

Where do API keys go?

Editor/local secret stores — not committed MCP JSON. Check 8.

Why twelve checks instead of a tutorial?

Tutorials show happy path. Checks force refusal gates before the happy path can burn a week of map work.

How does this relate to the Unity MCP 1.5 kit?

Same shape (numbered free preflight), different engine and plugin. Cross-link; do not keyword-cannibalize.

What if Blueprint MCP fails?

Expected for node wiring. Keep critical graphs human; file issues upstream; don’t block ship on it.

Do we need the Fab Pro plugins?

Not for this free checklist. Pro is optional if you need broader model coverage/stability claims — verify on Fab yourself.

Related reading

• UnrealGenAISupport (primary)
• Unreal MCP in Unreal Editor (Epic lane)
• Unreal Engine 5.7 Released (forums)
• 12 Free Unreal MCP Agent Safety Tools After UE 5.8
• 12 Free Unity MCP 1.5 Checks Before You Wire Agents
• Unreal 5.8 MCP Cursor Safe Session Worksheet
• Stop Exposing Unreal MCP Beyond Loopback
• Unreal guide
• 25 free Discord servers
• Courses

Wire agents in a lab, on loopback, with a receipt — or do not wire them. Popular GenAI MCP repos are still build inputs with blast radius; twelve free checks are cheaper than a ruined Persistent Level.