A socket bridge gives an AI the reach of Blender Python
MCP for Blender joins two local pieces. A Blender add-on opens a socket inside the application, while a Python MCP server translates client tool calls into scene operations. Once connected, a model can inspect objects, create geometry, alter materials, export GLB or FBX files, and execute Blender Python. The old blender-mcp name now redirects to mcp-for-blender, and the README says existing uvx blender-mcp configurations keep working.
That loop is the reason to use it. The model can inspect a scene, act on it, then request another view instead of merely suggesting menu clicks. The measured checkout was only 1.6 MB with about 23,556 source lines, yet it exposed enough surface area for modeling, materials, scene queries, exports, and external assets. You still need to judge the geometry and watch what the code changes. A successful tool call does not make the result production-ready.
Safe mode narrows code execution, but the socket has no login
The most important setting is BLENDER_MCP_SAFE_MODE=1. Without it, the execute_blender_code tool can run arbitrary Python in Blender. Safe mode checks scripts and blocks direct file access, program launches, network access, and code intended to persist after the command. Common Blender work, including modeling, rendering, saving, importing, and exporting, remains available. The README also tells users to save their work before handing control to a model.
The add-on listens on localhost at port 9876 by default. Its socket protocol has no authentication or encryption, so the local bind is part of the security boundary. The documentation recommends an SSH tunnel instead of exposing the socket directly. Minimal telemetry is also on by default: it includes an install ID, session ID, tool name, result, timing, software versions, operating system, and timestamp. Prompt, code, screenshot, and scene collection requires opt-in, while DISABLE_TELEMETRY=true turns off the smaller record too.
What happened when we ran it
Our sandbox installed commit 8ce9f8d in 13 seconds, pulling 62 packages and using 68 MB on disk. The build completed in 2 seconds. Pytest then finished in 10 seconds with 263 passed, 0 failed, and 1 skipped of 263. Pip-audit reported 0 known vulnerabilities in the installed Python environment. For a tool that can execute code inside a creative application, that clean run is a meaningful reason to try the pinned commit.
The repository contained 40 files and about 23,556 lines of source. It had a Dockerfile and a tests directory, but our scan found 0 CI workflow files. That does not cancel the 263 passing tests; it leaves a question about whether every proposed change is forced through the same suite before merging. Our run covered installation, build, tests, and dependency auditing in a fresh unprivileged Debian container. It did not grade generated meshes or drive an interactive Blender desktop.
The quick start has 3 steps and 2 processes
New users install uv, register uvx mcp-for-blender with an MCP client, and install the bundled Blender add-on. Blender 3.0 or newer and Python 3.10 or newer are required. The final connection still depends on both sides being alive: the MCP process must be available to the client, and the Blender sidebar server must be started. The docs warn against running more than one MCP server instance at once.
Desktop applications can miss uvx even when a terminal finds it because GUI apps may inherit a different PATH. The README shows how to use an absolute executable path and suggests pinning Python 3.11 when conda, pyenv, asdf, or a newer interpreter causes package trouble. Those notes matter more than the 13-second package install because most setup failures happen at the border between the client, Python environment, and add-on.
Docker only contains the MCP server. Blender still runs on the desktop and must accept the connection. Docker Desktop provides host.docker.internal on macOS and Windows; Linux needs host networking with BLENDER_HOST=localhost. Open issue 372 reports that viewport screenshots fail with Windows Blender and the MCP server in Docker. The report has no fix or diagnosis, so test that path before building a workflow around visual feedback.
Asset imports add credentials and license work
Poly Haven search needs no API key and its assets are CC0. Poly Pizza requires a key, and the README says about 69% of its catalog uses CC-BY, which requires attribution. The add-on stores source and license data on imported objects to help that credit survive in the .blend file. Sketchfab, Hyper3D, and Hunyuan3D bring their own accounts, credentials, endpoints, and terms. Teams should enable only the providers they intend to use.
The asset path can also interrupt the editing loop. Poly Haven downloads happen on Blender's main thread, so the interface freezes until a transfer finishes. The guide recommends 1k or 2k assets unless the camera will be close. Poly Pizza downloads may fail behind a Cloudflare challenge on datacenter, VPN, or cloud connections. Neither issue appeared in our 10-second test run because it did not exercise those network services.
A September 2026 push matters more than the missing release page
GitHub recorded the latest push on September 27, 2026. The renamed repository had 29,531 stars and 35 combined issues and pull requests when fetched, and the issue list showed activity during the same month. GitHub returned no latest release. That makes the recent commit history and package documentation better signs of current maintenance than a release tag that does not exist.
The project is easy to recommend for an experiment because our 62-package environment stayed small and all 263 tests passed. The boundary is just as clear. This tool hands a model a broad Blender control surface through an unauthenticated local socket. Keep a human at the viewport, keep backups, and turn repeated successful prompts into ordinary reviewed Python when the work becomes important.