mcp_blender_get_scene_infoLABSCO 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.
Setup effort
Build from source — git clone --recursive https://github.com/tahooki/unreal-blender-mcp.git
USE CASES
01
Getting a model out of Blender and into a level
Create and shape the object, export it to a file, then import that asset into Unreal and place it as an actor.
02
Blocking out a scene by describing it
Read the current Blender scene, add primitives with materials, and adjust their transforms — checking state between steps rather than after.
03
Standing up a fresh Unreal level
Create the level, add actors, and set up a Blueprint class for the behaviour you need next.
04
Doing something neither tool list covers
Drop to Python inside whichever application it belongs in — the escape hatch, and the one to review before running.
16 tools
Listed in project docs. Your client may show a different list.
mcp_blender_get_object_infomcp_blender_create_primitivemcp_blender_create_materialmcp_blender_assign_materialmcp_blender_transform_objectmcp_blender_export_modelmcp_blender_execute_codemcp_unreal_get_engine_versionmcp_unreal_create_levelmcp_unreal_create_actormcp_unreal_import_assetmcp_unreal_create_blueprintmcp_unreal_modify_actormcp_unreal_set_materialmcp_unreal_execute_codeBEFORE YOU INSTALL
What to know first
Tools you get
16 tools named in the project's documentation.
Requires
Python 3.10 or later
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone --recursive https://github.com/tahooki/unreal-blender-mcp.git
cd unreal-blender-mcp
uv venv
source .venv/bin/activate
uv pip install -e .
python run_extended_server.pyMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"unreal-blender-ext": {
"command": "<YOUR_PATH_TO_UNREAL_BLENDER_MCP>/.venv/bin/python",
"args": [
"<YOUR_PATH_TO_UNREAL_BLENDER_MCP>/run_extended_server.py"
]
}
}
}<YOUR_PATH_TO_UNREAL_BLENDER_MCP> is the full path of the unreal-blender-mcp folder you cloned, in both places. The command is the Python inside the .venv that uv pip install -e . filled, so the server finds its dependencies; on Windows it is .venv\Scripts\python.exe.
