説明
Unified MCP Server is a local MCP host for Unreal Engine that lets editor tools and AI agents connect through one authenticated loopback endpoint instead of separate servers per plugin.
Instead of hard-coding agent access into every feature plugin, the server runs JSON-RPC 2.0 over HTTP on 127.0.0.1 and aggregates tools from provider plugins at runtime. Each provider registers through a small C++ contract, and the host exposes prefixed tool names to MCP clients through one bearer-token protected endpoint.
Whether you connect Cursor, Claude Desktop, custom Python agents, or internal automation, Unified MCP Server gives you one stable handshake file, local-only security defaults, and a clean extension point for bridge plugins — without bundling Node.js, Python, mcp-remote, or any standalone executable.
🔹 Key Features
Single local MCP host
Run one MCP-compatible endpoint inside the Unreal Editor instead of maintaining a separate local server for every plugin or tool integration.
Provider-based tool registration
Tools come from other plugins through IUmcpToolProvider. The host does not hard-code project tools, partner plugins, or domain-specific business logic.
Prefixed tool names
Provider-local tools are exposed as providerId_tool so multiple bridge plugins can attach tools without name collisions.
Loopback-only security model
The server binds to 127.0.0.1, is disabled by default, and requires a bearer token on every request.
Handshake file for agents
On start, host, port, and token are written to Saved/UnifiedMcpServer/agent/mcp_endpoint.json for local agent configuration.
Editor lifecycle controls
Start, stop, and rotate the bearer token from the Tools menu or optional Blueprint lifecycle helpers.
Request diagnostics
Request metadata is appended to Saved/UnifiedMcpServer/logs/mcp_requests.jsonl for local troubleshooting and support.
C++ core with optional Blueprint helpers
The server is implemented in C++ and exposes selected lifecycle and diagnostics functions for editor automation. MCP tool providers remain C++ modular features.
Zero bundled executables
No Node.js, Python, mcp-remote, or standalone server binary is included.
🔹 Typical Use Cases
Local AI coding agents connected to Unreal Editor tools
Multiple plugins sharing one MCP server and one auth token
Bridge plugins for search, context, asset, or pipeline tools
Editor automation and QA workflows that need a stable local endpoint
Teams that want agent access without rewriting every plugin integration
🔹How It Works
Unified MCP Server keeps MCP transport, authentication, and routing in one editor module, but leaves tool implementation to provider plugins.
The host collects registered provider tools, prefixes them by provider ID, and routes tools/list and tools/call requests to the matching provider at call time. This avoids changing the server plugin every time a new tool source is added.
🔹Requirements
Engine: Unreal Engine 5.4+
Code: C++ plugin with Runtime interface module and Editor server module
Loopback HTTP endpoint: 127.0.0.1 only
Project tools: require separate provider or bridge plugins
Included Content
Unified MCP Server C++ plugin
Runtime provider contract module (UnifiedMcpServerInterface)
Editor HTTP server module (UnifiedMcpServerEditor)
Project settings, Tools menu actions, request log, and handshake file workflow
Documentation and setup guide
Known Scope:
Unified MCP Server is not a full AI stack or tool pack. It focuses on local MCP hosting, bearer-token auth, provider aggregation, and editor lifecycle controls.
It does not include an AI model, LLM provider, or project-specific tools by itself. Blueprint support is limited to server lifecycle and diagnostics; MCP tool providers remain C++ contracts. Some stdio-only MCP clients may still need a user-installed bridge.
🔹Support
For support, feature requests or workflow questions, use the Fab support section or the Discord support channel:
🔹 Discord Support Channel