Labsco
MCP SERVER

Unreal-Blender MCP

by tahooki

Drive Blender and Unreal Engine from one MCP server — create primitives and materials, import assets, build levels, run Python in either.

3D, CAD & Game Engines
Summary
Two engines, one conversation — at the cost of three processes.

The payoff is a workflow that crosses the tool boundary: build and export in Blender, import and place in Unreal, all in one exchange. The honest caveat is in the project's own roadmap — the Unreal side leans on direct Python execution rather than a structured API, with predefined functions and tighter execution scope listed as planned work. Treat `mcp_unreal_execute_code` as the powerful and blunt option it is.

What it is

A single MCP server that talks to two 3D applications at once. It extends the blender-mcp project with Unreal Engine support, so an assistant can model something in Blender, export it, and place it in an Unreal level without switching tools. Three processes are involved: the MCP server, a socket server inside Blender, and an HTTP server inside Unreal provided by a plugin you copy into your project.

What you get
  • Blender scene and object information read back before anything is changed — `mcp_blender_get_scene_info`, `mcp_blender_get_object_info`
  • Primitives created, transformed, given materials and exported to a file — `mcp_blender_create_primitive`, `mcp_blender_transform_object`, `mcp_blender_create_material`, `mcp_blender_assign_material`, `mcp_blender_export_model`
  • Unreal levels, actors and Blueprint classes created, and actors modified — `mcp_unreal_create_level`, `mcp_unreal_create_actor`, `mcp_unreal_create_blueprint`, `mcp_unreal_modify_actor`
  • Assets imported into Unreal from a file, and materials set on an object — `mcp_unreal_import_asset`, `mcp_unreal_set_material`
  • The Unreal engine version reported, so the agent knows what it is talking to — `mcp_unreal_get_engine_version`
  • Arbitrary Python executed inside either application when nothing else fits — `mcp_blender_execute_code`, `mcp_unreal_execute_code`
Requirements

Python 3.10 or later, Blender 3.0 or later, Unreal Engine 5.0 or later, and the `uv` package manager. Clone with `--recursive` — blender-mcp is a submodule and the project does not work without it. Three pieces must be running: the MCP server on port 8000, the Blender addon started from the sidebar panel (port 8400, or 8401 for the extended addon), and the Unreal plugin from the `UEPythonServer` folder copied into your project's `Plugins` directory (port 8500). Start them in that order — MCP server, then Blender, then Unreal — which is the first thing the troubleshooting section tells you to check.