BAIQISTUDIO
Baiqi MCP Kit connects coding agents to the Unreal Editor through a local, structured interface—so they can inspect, create, drive and verify real project state, then show the frame that proves it.
"method": "tools/call",
"name": "get_blueprint_info",
"arguments": {
"asset_path": "/Game/BP_Player"
}Five things this server does that a text-only agent cannot do alone — each backed by a tool you can call today.
take_pie_screenshots captures a series in Play-In-Editor and tiles it into one contact sheet — nine shots become a 3×3 grid with the per-frame pixel difference reported, so a walk cycle or an effect is judged from a single image.
Create and edit sequences, montages, blend spaces, aim offsets, pose assets and AnimBlueprints — sections, slots, notifies, states and transitions — then compile and read them back.
Mesh thumbnails, skeletal pose renders, Niagara frames, UMG and Blueprint snapshots, editor viewport and PIE captures — returned as files, optionally base64, so the agent sees what it made.
pie_inject_input holds movement and look input on the PIE pawn through Enhanced Input actions, legacy axis keys or direct movement, so the character walks and plays its locomotion instead of being teleported into a pose.
Write, read the value back, compile, capture, fix. Writes report what changed, validation is one call away, and the capture proves it — errors say what to change, and destructive tools can require approval.
One Streamable HTTP endpoint. Claude Code, OpenCode, DeepSeek Harness, Cursor, Windsurf, VS Code + Copilot, Cline or your own client — no per-client plugins to install.
Stop taking the model's word for it — look at the frame. On one call the server renders, captures and compares real output, so you judge the result with your eyes instead of a summary.
Give agents reliable tools for the parts of Unreal work that demand context, careful edits and proof that the result is correct.
Query assets, actors, Blueprints, components, graphs and animation data as structured responses—not guesses from a screenshot.
Create editor-native assets, wire graph nodes, configure components and change project settings through explicit operations.
Read changes back, validate Blueprints and render graph or mesh previews in the same editor session.
Requests connect to a loopback endpoint on the editor machine. No remote control plane and no project data sent to a cloud service.
Use the same MCP connection for inspection, authoring and validation across the editor.
Baiqi MCP Kit gives an agent a dependable set of hands inside the editor. The agent stays in control of the decisions; the tools make each step explicit and observable.
Fetch focused context for the next decision.
Make an asset, graph or scene change with clear inputs.
Compile, validate, query or render before proceeding.
The same stable tool surface across UE 5.5, 5.6, 5.7 and 5.8. Version differences are isolated in a compatibility layer.
Baiqi MCP Kit runs with the editor and listens on loopback by default (remote access is opt-in). Project owners can control destructive operations and sensitive capabilities.
Read the connection guideEndpoint defaults to 127.0.0.1:13777/mcp; requests stay local unless remote access is explicitly enabled (and can be token-protected).
Read-only and destructive tools are classified, with configurable deny lists and protected paths.
High-risk actions can require a visible editor-side approval before they proceed.
JSON-RPC requests use the MCP session header returned during initialization.
Baiqi MCP Kit 1.02 ships as full C++ source for Unreal Engine 5.5–5.8, compiled by the editor on first load. Start with the installation guide, or browse the tool surface first.
http://127.0.0.1:13777/mcp