ue5-mcp-bridge and unreal-mcp
These are competitors offering overlapping functionality—both enable AI assistants to control Unreal Engine 5 via MCP, so users would select one based on maturity and feature completeness rather than use them together.
About ue5-mcp-bridge
Natfii/ue5-mcp-bridge
MCP server bridging AI assistants to Unreal Engine 5 editor
Exposes comprehensive tools for AI-driven UE5 editor automation—including level/actor manipulation, Blueprint modification, Animation Blueprint state machines, and material assignment—via the Model Context Protocol standard. Implements stdio transport compatible with Claude, ChatGPT, Cursor, and other MCP clients, backed by a configurable HTTP endpoint that connects to the UnrealClaude plugin or custom REST implementations. Provides 20+ specialized tools spanning asset management, script execution, character setup, and async task queuing designed for workflow acceleration rather than asset generation.
About unreal-mcp
chongdashu/unreal-mcp
Enable AI assistant clients like Cursor, Windsurf and Claude Desktop to control Unreal Engine through natural language using the Model Context Protocol (MCP).
Implements a native C++ TCP server plugin paired with a Python MCP server using FastMCP, enabling comprehensive Unreal workflows including actor manipulation, Blueprint creation with node graph editing, and real-time viewport control. The architecture uses stdio transport between AI clients and the Python server, which communicates via TCP (port 55557) with the Unreal plugin to execute serialized commands and return responses.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work