Unreal MCP — Control Unreal Engine via MCP

Main

• Decide transport first: direct HTTP MCP inside the plugin is simplest; use the TypeScript bridge only if you need stdio-style setups.

• Treat plugin compilation as one-time bootstrap: build for your UE version, then distribute binaries to teammates.

• Start with low-risk operations (screenshots, asset listing) before enabling destructive tools in agent sessions.

Source-backed notes

• README describes a native C++ Automation Bridge plugin and dual transport (native HTTP/SSE or WebSocket bridge).
• README shows native HTTP MCP with default port 3000 and sample claude mcp add ... --transport http wiring.
• README notes Blueprint-only projects can’t compile native plugins without adding a C++ class first.

FAQ

• Do I need Node.js for the native path?: No — README says the plugin includes a built-in HTTP MCP server.
• Will one build work across UE versions?: No — README notes binaries are tied to a specific UE version.
• How do I verify it’s connected?: Check Unreal logs for MCP transport messages and your client’s server status.