Note: the PyPI package
blender-mcpis nowmcp-for-blender. Existing setups keep working —uvx blender-mcpstill runs the server and no config change is required. New installs should usemcp-for-blender. What changed and why
One command sets up your AI apps and the Blender addon:
macOS / Linux
curl -LsSf https://www.mcp-for-blender.com/install.sh | sh
Windows (PowerShell)
irm https://www.mcp-for-blender.com/install.ps1 | iex
From Command Prompt instead: powershell -c "irm https://www.mcp-for-blender.com/install.ps1 | iex"
Prefer not to run a script, or Windows Defender blocked it? Install uv with winget, open a new terminal, then run setup:
winget install --id=astral-sh.uv -e
uvx mcp-for-blender setup
Already have uv? Run uvx mcp-for-blender setup instead.
It installs uv if needed, finds the MCP clients on your machine (Claude Desktop, Claude Code, Codex, Cursor, VS Code, Devin Desktop/Windsurf, OpenCode, Antigravity), and lets you pick which to set up. Then it installs the Blender addon and enables it. Your existing config is kept: it only adds a blender entry and saves a .bak of each file it changes.
Then fully quit and reopen your AI app (on Windows, quit it from the system tray), open Blender, and ask it to build something. The addon starts its server when Blender opens.
# macOS
brew install uv
# Linux
curl -LsSf https://astral.sh/uv/install.sh | sh
# Windows
winget install --id=astral-sh.uv -e
# or, with uv's installer
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
> **Warning:** Do not proceed before installing uv. Use the official installer — *not* `pip install uv`.
**2. Add the MCP server to your client**
{
"mcpServers": {
"blender": {
"command": "uvx",
"args": ["mcp-for-blender"]
}
}
}
claude mcp add blender uvx mcp-for-blender
codex mcp add blender -- uvx mcp-for-blender
uvx mcp-for-blender install-addon
Then in Blender: **Edit → Preferences → Add-ons** → enable **Interface: MCP for Blender**.
**4. Connect**
The addon starts its server when Blender opens. To check, press `N` in the 3D viewport → open the **MCP for Blender** tab (click **Start MCP Server** if it isn't running). That's it — ask Claude to build something.
Note: Only run one instance of the MCP server (either Cursor or Claude Desktop), not both.
| Two-way communication | Connect Claude AI to Blender through a socket-based server |
| Object manipulation | Create, modify, and delete 3D objects in Blender |
| Material control | Apply and modify materials and colors |
| Visual verification | Multi-angle, camera, wireframe, X-ray and animation-strip views, plus renders, so the AI checks its own work |
| Code execution | The AI writes Blender Python directly |
| Asset & model generation | Poly Haven assets, Sketchfab models, Poly Pizza low-poly models, and AI-generated 3D models via Meshy, Tripo, Hyper3D Rodin and Hunyuan3D |
Generate AI 3D models (Meshy, Hunyuan3D, Tripo, Hyper3D Rodin) straight into Blender without bringing your own API keys. More details
The system consists of two main components:
addon.py) — a Blender addon that creates a socket server within Blender to receive and execute commandssrc/blender_mcp/server.py) — a Python server that implements the Model Context Protocol and connects to the Blender addonThe quickest way is the one-line installer. It installs uv, configures your MCP clients, and installs and enables the Blender addon:
# macOS / Linux
curl -LsSf https://www.mcp-for-blender.com/install.sh | sh
# Windows (PowerShell)
irm https://www.mcp-for-blender.com/install.ps1 | iex
Already have uv? Run uvx mcp-for-blender setup instead. On Windows, winget install --id=astral-sh.uv -e installs uv without running a script. See Quickstart for what it changes. The rest of this section covers manual setup.
brew install uv
**Windows**
winget install --id=astral-sh.uv -e
Then open a new terminal so it's on your PATH. Or use uv's installer:
powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
Then add uv to the user path in Windows (you may need to restart Claude Desktop after):
$localBin = "$env:USERPROFILE\.local\bin"
$userPath = [Environment]::GetEnvironmentVariable("Path", "User")
[Environment]::SetEnvironmentVariable("Path", "$userPath;$localBin", "User")
**Linux**
curl -LsSf https://astral.sh/uv/install.sh | sh
It lands in `~/.local/bin` — open a new shell so it's on your PATH.
Otherwise, installation instructions are on their website: [Install uv](https://docs.astral.sh/uv/getting-started/installation/)
On every OS, use uv's **official installer above — not `pip install uv`**, which may not create the `uvx` command and can hide uv inside an environment your client can't see.
Warning: Do not proceed before installing uv.
MCP clients started from a GUI (Claude Desktop, Cursor, VS Code from the Dock/Start menu) do not inherit your terminal's PATH, so a bare "command": "uvx" can fail with spawn uvx ENOENT even though uvx works in your terminal. If that happens:
which uvx (macOS/Linux) or where uvx (Windows) — and use it as "command", e.g. /opt/homebrew/bin/uvx or C:\Users\<you>\.local\bin\uvx.exe."command": "cmd", "args": ["/c", "uvx", "mcp-for-blender"].Avoid conda / pyenv / version conflicts.
uv chooses which Python runs the server. On machines with conda (auto-activated base), pyenv, or asdf — or with a new
| 日期 | 榜单 | 排名 | 周期新增 | 总 STAR |
|---|