BlenderMCP

BlenderMCP turns Blender into a shared workspace. A central MCP server runs an OAuth-gated, per-user message bus; Blender addons connect as persistent clients; LLM sessions connect as ephemeral clients. Anything can dispatch a job to anything else.

The HTTP build exposes 34 MCP tools — 5 bus tools, 5 diagnostics tools, and 24 dispatch tools that wrap Blender’s command surface as flat MCP calls. Plus 6 resources for bus state, scene snapshots, and paginated console scrape, and 9 prompts covering dispatch recipes and Blender scripting workflows. The transport is the standard MCP notifications/message log channel — no custom socket, no WebSocket layer.

Get running in 5 minutes

Boot the server, attach a fake Blender peer, call a dispatch tool.
Quickstart

Use cases

Seven concrete patterns: render farms, approval workflows, multi-LLM specialization, status-probe-before-dispatch.
Use cases

Write a client

Two styles: direct dispatch tool calls vs custom _message_bus subscription.
Write your own LLM client

Dispatch tools

24 blender_* tools wrapping the addon command registry — scene reads, code exec, asset downloads, msgbus.
Dispatch tools reference

Bus tools

Five low-level tools that move messages: register, send, update, list.
Bus tools reference

Dispatch vs script

Typed command tools vs free-form Python — when to use each path.
Command dispatch vs script dispatch

What’s here

• Tutorials — learn-by-doing paths starting from scratch
• How-to — task-oriented recipes for deployment, client development, command authoring
• Reference — every tool, every parameter, every priority level
• Explanation — the design decisions: why MCP logging, how OAuth isolates buses, how dispatch tools hide the bus