three.ws Blender MCP Server

What this does

three.ws Blender exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

BLENDER_PATH
BLENDER_MCP_TIMEOUT_MS
BLENDER_MCP_WORKDIR
BLENDER_MCP_ALLOW_PYTHON
BLENDER_MCP_INLINE_IMAGE_BYTES
BLENDER_MCP_INLINE_IMAGE_PX
BLENDER_MCP_MAX_CONCURRENCY
THREE_WS_BASE
THREE_WS_FORGE_TIMEOUT_MS
THREE_WS_FORGE_PROVIDER_KEY

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install three.ws Blender?

Run the Claude Code command in the install section to add three.ws Blender to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with three.ws Blender?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to three.ws Blender as well.

Does three.ws Blender need an API key?

Yes. Before it can run, set these environment variables: BLENDER_PATH, BLENDER_MCP_TIMEOUT_MS, BLENDER_MCP_WORKDIR, BLENDER_MCP_ALLOW_PYTHON, BLENDER_MCP_INLINE_IMAGE_BYTES, BLENDER_MCP_INLINE_IMAGE_PX, BLENDER_MCP_MAX_CONCURRENCY, THREE_WS_BASE, THREE_WS_FORGE_TIMEOUT_MS, THREE_WS_FORGE_PROVIDER_KEY. They go in the env block of your MCP config.