Blender MCP (bpy.dev)

Install

Works in

• Codex
• SourceCraft
• Koda
• Coddy

Manual install

{"mcpServers": {"blender": {"command": "uv", "args": ["--directory", "/absolute/path/to/blender_mcp/mcp", "run", "blender-mcp"], "env": {"BLENDER_MCP_CLI_BACKEND": "bpy", "BLENDER_MCP_BPY_PYTHON": "/absolute/path/to/python-with-bpy"}}}}

What it does

The bpy.dev repository is an independent enhanced build of Blender Lab's Blender MCP project. It keeps the original design: a Blender add-on and a separate MCP server exchange data over a TCP socket, while the client talks to the server over stdio. On top of that it adds modes missing from the base version. Tools with the _for_cli suffix open a saved .blend file in a fresh process and need no running Blender UI. The backend is chosen with the BLENDER_MCP_CLI_BACKEND variable: a Blender executable or a standalone Python with the bpy module. Live tools such as execute_blender_code still work through the add-on in an open session. The agent can ask the Blender runtime for exact signatures, enums, defaults and availability of functions instead of relying only on bundled docs. Command-line runs have time and output limits, and overwriting the source file is checked before writing. This is process isolation, not an OS-level sandbox.

Who it is for. For developers and technical artists who need a Blender MCP that processes saved .blend files without a UI and gives an exact reference to the Blender Python API.

Example request

Open the saved scene.blend without a UI, list its objects and materials, then check the Blender API for the parameters the mirror operator accepts.

MCP

Transport

stdio

Authentication

not required

Limitations

This is a modified distribution of Blender Lab's project, and its provenance is described in NOTICE.md. The repository itself calls it a developer preview: a checklist is still open before publication, including package naming, a fresh-clone install check and secret scanning. The license is GPL-3.0. Standalone mode needs the path to a Python with bpy installed, and a live scene needs the add-on in Blender. Code execution in Blender is not protected by an OS sandbox; the risks are collected in SECURITY.md.

How to disable. Remove the blender entry from the MCP client config and disable the blender_mcp_addon add-on in Blender preferences. The server does not change .blend files unless you ask it to.

README in short

The description splits the project into a Blender add-on and an MCP server. The add-on accepts requests over TCP and supports host, port and auto-start settings. The server is a Python package with a blender-mcp entry point and loads tools automatically from the tools folder. Next to it sit a Python API reference and excerpts of the Blender manual in RST. The tools are listed in a separate readme_tools.rst file.