Blendmcp MCP Server

Blendmcp MCP server exists for a simple reason — assistants are far more useful when they can act on Blendmcp directly instead of describing what you should do. Control Blender from Claude and other LLMs through the Model Context Protocol.

What you get

Control Blender from Claude and other LLMs through the Model Context Protocol (MCP). blendmcp lets an AI assistant inspect and edit your Blender scene: create and transform objects, apply materials, run Python, capture viewport screenshots, and pull in assets from PolyHaven, Sketchfab, Hyper3D, and Hunyuan3D.

• Two-way communication — Connect Claude AI to Blender through a socket-based server
• Structured editing tools — Add primitives, transform objects, set materials, duplicate, and delete through dedicated tools that return the affected object's bounding box and dimensions for confirmation
• Object manipulation — Create, modify, and delete 3D objects in Blender
• Material control — Apply and modify materials and colors
• Scene inspection — Get detailed information about the current Blender scene
• Visual feedback — Capture viewport screenshots, including alongside execute_blender_code results

Setting it up

blendmcp on PyPI is all you need. Most clients run it directly, so configuration is a few lines and a restart.

What the assistant can call

Once Blendmcp is connected, these are the calls the assistant has available:

• Prerequisites — Otherwise installation instructions are on their website: Install uv
• Capabilities — The Capabilities tool exposed by this server
• Development — Tests live in tests/ and run outside Blender. Because addon.py imports bpy (only available inside Blender), tests/conftest.py installs lightweight

Configuration and credentials

You will need 2 environment variables: BLENDER_HOST, BLENDER_PORT. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Blender 3.0 or newer - Python 3.10 or newer - uv package manager: If you're on Mac, please install uv as On Windows and then add uv to the user path in Windows (you may need to restart Claude Desktop after): Otherwise installation instructions are on their website: Install uv ⚠️ Do not proceed before installing UV

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the blendmcp mcp server does with a few real requests.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Blendmcp's toolset — Prerequisites, Capabilities, Development — is a fair guide to whether it matches your workflow.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.