mcp-unreal-agent

Use this skill whenever the user's request touches the UE5 project this skill is installed in — analyzing a bug, observing editor/scene/runtime state, reading or editing Blueprints/materials/animation/widgets/levels/sequencer/MRQ, spawning or modifying actors, running PIE, taking screenshots, or anything that would otherwise require manually opening the Unreal Editor. The `unreal-agent` MCP server gives you live, structured, editor-accurate access to the project — prefer it over guessing from source files alone.

Step-by-step playbook for installing mcp-unreal-agent into an end user's UE5 project. Read when the user asks to install the MCP, set up the agent, or follow the install prompt.

How the C++ context bridge works — when a Blueprint references a C++ class / function / variable, how the agent locates and reads the source. Read when implementing or debugging tools that surface C++ source to the agent.

How to design and register a new MCP tool — input schema (Zod), output contract, descriptions, tests. Read before adding any new tool to Tools/src/tools/.

Designing composite UE5 tools and chaining existing ones via the ID-passing contract. Use when adding a new tool, designing a multi-step flow, or refactoring primitives into a composite atomic flow.

UE5 editor API cheat sheet for AI agents — Subsystem map, deprecated→modern translations, transaction patterns, where Python reaches and where C++ is required. Read when picking the right API for a tool implementation or when porting deprecated code.