Machine-facing surface for agents and integrations that need Unreal-aware reads, diagnosis, and controlled workflow access.
Structured routes for tools, agents, and editor integrations. Project reads, diagnosis, and governed workflow entry points. Consistent safety rules across integrations. Best fit for machine-driven workflows and orchestration
Runtime entries
24
Runtime entries
Canonical product actions spanning diagnosis, project reads, workflows, auth, and governance.
MCP tool routes
20
MCP tool routes
Machine-facing routes for Unreal-aware reads, diagnosis, and governed workflow access.
VSCode actions
29
VSCode actions
Editor-native command coverage with the same runtime and trust model underneath.
Surface types
5
Surface types
CLI, MCP, VSCode, CI, and the optional UE bridge.
Generic agent tooling can call commands. Unreal teams need structured, project-aware context.
Context blindness
Machine workflows need more than raw files and terminal output to reason well about Unreal-specific work.
Unclear action boundaries
Agent workflows lose trust quickly when execution posture and review checkpoints are not visible.
Fragmented tool stories
Different integrations should not force teams to relearn the product or its operating limits.
Weak structured output
Generic integrations often return too little usable context for downstream planning and review.
MCP that gives tools and agents a real Unreal operating layer
20 MCP routes
Machine-facing route coverage for diagnosis, project reads, and workflow access.
Shared trust model
Evidence posture and review boundaries stay aligned with every other surface.
Agent-ready structure
Outputs are shaped for tools, editor integrations, and orchestrated workflows.
Shared runtime model
Using MCP changes the integration style, not the underlying product behavior.