Documentation
Install, connect, automate.
Baiqi is a local Model Context Protocol server that runs inside the Unreal Editor. This page covers installation, connecting an agent, and the shape of the tool surface.
1 / Install
Baiqi ships as a standard Unreal plugin for Windows. Drop it into your project's Plugins/ folder and let the editor build it on first launch.
Enable the plugin from Edit → Plugins → Baiqi if it is not already active. The server starts automatically with the editor.
2 / Connect an agent
The endpoint is a Streamable HTTP MCP server (JSON-RPC 2.0, MCP spec 2025-06-18). Point your client at:
Call initialize first and keep the Mcp-Session-Id response header — every later request must send it back. The transport is loopback-only by default.
3 / What is inside
Tools
463 stable editor automation tools: assets, actors, Blueprints, materials, Niagara, animation, Sequencer, PCG, UMG, PIE, and more.
Prompts
10 built-in workflow prompts that guide an agent through common editor tasks.
Resources
10 unreal:// resources for project, level, selection and editor introspection.
Engine lanes
One source tree spanning Unreal Engine 5.5, 5.6, 5.7 and 5.8.
4 / Compatibility
Every stable tool registers on all four engine lanes with the same name and schema. Where a capability depends on a newer engine API, the tool is a stub on older versions and returns a clear "requires UE 5.8" error instead of failing silently.
- Platform: Win64 (Editor).
- Engines: UE 5.5, 5.6, 5.7, 5.8.
- No Python bridge and no external services.
5 / Security
- Loopback-only by default; remote access is opt-in.
- Optional capability token for authenticated requests.
- Protected rails for read-only vs. destructive tools, plus an optional editor-side approval prompt.
6 / Need help?
Check the common issues on the support page, or email us directly.