Grok + UE MCP

What it’s for

Unreal Editor is a deep tool. The interesting question for AI-assisted development is: can an agent actually drive it — inspect the scene, spawn actors, touch assets, help author Blueprints — instead of only chatting about C++ in a vacuum?

GrokUE_MCP is a blank UE 5.8 Blueprint project and integration workspace for connecting Grok (and other MCP clients) to the editor through Epic’s Model Context Protocol (MCP) plugin. It is not a game prototype. It exists to prove, document, and stabilize that workflow.

Why it exists

“AI can edit Unreal” is easy to claim and hard to verify. This repo is the lab notebook: phases run, toolsets probed, hitches written down, screenshots kept. If you care about agentic editor work, you want evidence and a repeatable session setup, not a vibes-based demo.

What it validated (high level)

Across the documented phases, the project exercised things like:

MCP connection into the editor (local HTTP MCP endpoint)
Discovery and use of Epic’s shipped toolsets (scene read/write, asset-oriented tools, and more)
A custom project toolset for health/session-style checks
Multi-client use (e.g. Grok TUI + Cursor)
Content-pipeline style work: materials, DataTables, Blueprint graph authoring, mesh import experiments

There’s a dedicated capabilities writeup in the repo if you want the scannable “what works / what doesn’t” list without reading every phase note.

What it is not

Not a gameplay framework
Not a promise that every editor action is unattended
Not a replacement for a human who still opens the project, confirms the viewport, and restarts the editor when plugins change

The honest part of the docs is what still needs a human in the loop.

Who it’s for

Engineers and studios exploring AI + Unreal Editor automation who want a concrete UE 5.8 workspace and written results to build on — or to steal patterns for their own MCP setups.

Want the details?

Start with the capabilities summary and notes in the repo:

→ github.com/BrokenGameplayStudios/GrokUE_MCP
→ Especially Docs/CAPABILITIES.md in that project