Three.ws Blender MCP Server

Drive a local Blender headlessly: inspect, convert, render and script 3D files.

Local serverstdio

What is the Three.ws Blender MCP Server?

Three.ws Blender is an MCP integration. Drive a local Blender headlessly: inspect, convert, render and script 3D files.

Packages and local setup

The published npm package is @three-ws/blender-mcp, version 0.5.0. Its declared MCP transport is stdio.

The package declares BLENDER_PATH: Absolute path to the Blender 3.0+ executable. Leave unset to discover it on PATH and at the platform's standard install locations.; BLENDER_MCP_TIMEOUT_MS: Ceiling for one Blender job in milliseconds. Renders and heavy conversions are the slow ones.; BLENDER_MCP_WORKDIR: Directory for outputs written when a tool is called without an explicit output path.; BLENDER_MCP_ALLOW_PYTHON: Set to 0 to withdraw blender_run_python, which executes caller-supplied Python inside Blender, from the advertised tool list.; BLENDER_MCP_INLINE_IMAGE_BYTES: Ceiling on inlined image bytes. Past this the image stays on disk and the response says where.; BLENDER_MCP_INLINE_IMAGE_PX: Longest edge of the render copy returned inline in a tool result. The full-resolution PNG is always written to disk.; BLENDER_MCP_MAX_CONCURRENCY: How many Blender processes may run at once. Further calls queue rather than compete for memory.; THREE_WS_BASE: Base URL of the three.ws deployment backing blender_forge_import.; THREE_WS_FORGE_TIMEOUT_MS: Ceiling for one text-to-3D generation in milliseconds.; THREE_WS_FORGE_PROVIDER_KEY: Meshy/Tripo API key for the bring-your-own-key geometry lane. The default image lane is free and needs no key..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.5.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related design & creative tools MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
BLENDER_PATHAbsolute path to the Blender 3.0+ executable. Leave unset to discover it on PATH and at the platform's standard install locations.Optional
BLENDER_MCP_TIMEOUT_MSCeiling for one Blender job in milliseconds. Renders and heavy conversions are the slow ones.Optional
BLENDER_MCP_WORKDIRDirectory for outputs written when a tool is called without an explicit output path.Optional
BLENDER_MCP_ALLOW_PYTHONSet to 0 to withdraw blender_run_python, which executes caller-supplied Python inside Blender, from the advertised tool list.Optional
BLENDER_MCP_INLINE_IMAGE_BYTESCeiling on inlined image bytes. Past this the image stays on disk and the response says where.Optional
BLENDER_MCP_INLINE_IMAGE_PXLongest edge of the render copy returned inline in a tool result. The full-resolution PNG is always written to disk.Optional
BLENDER_MCP_MAX_CONCURRENCYHow many Blender processes may run at once. Further calls queue rather than compete for memory.Optional
THREE_WS_BASEBase URL of the three.ws deployment backing blender_forge_import.Optional
THREE_WS_FORGE_TIMEOUT_MSCeiling for one text-to-3D generation in milliseconds.Optional
THREE_WS_FORGE_PROVIDER_KEYMeshy/Tripo API key for the bring-your-own-key geometry lane. The default image lane is free and needs no key.Optional