← Back to Projects
Library

UE Cortex

An 11-agent Claude Code system that turns a natural-language prompt into a working Unreal Engine 5 project via an MCP orchestration server

Claude CodeMCPUnreal EnginePythonNext.jsAI Agents

Overview

UE Cortex is a multi-agent AI system for Unreal Engine 5 game development. Eleven specialist Claude Code agents — covering systems architecture, multiplayer, world building, Blueprints, DevOps, UI, audio, cinematics, performance, technical art, and AI — are coordinated by a Python MCP orchestration server that turns a single natural-language prompt into a Game Design Document, a dependency-ordered task graph, and a running set of generated project files. The product ships as a $99 one-time purchase through a companion Next.js marketing and checkout site.

Key Features

  • 11 specialist Claude Code agents with 83 topic-scoped reference files, each loaded on demand rather than pre-loaded into every session
  • MCP orchestration server (plan_game → approve_plan → run_all) that converts a prompt into a GDD and a 5-phase dependency-ordered task DAG, dispatching agents in parallel per phase
  • Shared GAME_STATE.json contract layer so cross-agent outputs — GAS attributes, save schema, HUD bindings — stay consistent instead of siloed one-shot answers
  • Built-in PIE verification runner that smoke-tests the generated project and self-corrects by routing compile/runtime errors back to the responsible agent
  • Provider-agnostic LLM client (Anthropic, Groq, Ollama) and a bundled minimal MCP server for driving the UE Editor directly — start/stop PIE, read logs, write files
  • Direct-sales site with Paddle checkout, EULA clickwrap, and presigned Cloudflare R2 delivery (48-hour expiring download links, no permanent public URL)

Technical Decisions

Agent identity (personality, workflow) is deliberately separated from agent knowledge (ref files), so a UE5 rule change never requires touching an agent’s core definition — the same philosophy is applied one level up in the orchestrator, where a single GAME_STATE.json file is the sole inter-agent communication channel, making agent output verifiable and diffable instead of buried in conversation history. Product delivery uses short-lived R2 presigned URLs rather than a static GitHub/Drive link specifically so a leaked link expires on its own instead of being redistributable indefinitely.