Blender MCP Server

Open Models MCP for Blender Using Ollama. Exposed over MCP by the blender mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

Control Blender 3D with natural language prompts via local AI models. Built on the Model Context Protocol (MCP), connecting Claude, Cursor, or any MCP client to Blender through a local Ollama LLM.

Its toolset

Everything the assistant can do here goes through one of these:

• blender_get_scene_info — Full scene summary: objects, camera, render settings
• blender_get_object_info — Detailed object info: transforms, materials, mesh stats
• blender_create_object — Add a primitive mesh (CUBE, SPHERE, CYLINDER, ...)
• blender_modify_object — Change location, rotation, scale, visibility
• blender_delete_object — Remove an object from the scene
• blender_set_material — Create and assign a Principled BSDF material
• blender_render_image — Render current scene to a file
• blender_execute_code — Run arbitrary Python/bpy code in Blender
• blender_get_polyhaven_categories — List PolyHaven asset categories
• blender_search_polyhaven_assets — Search PolyHaven library with pagination
• blender_download_polyhaven_asset — Download & import a PolyHaven asset
• blender_set_texture — Apply a downloaded PolyHaven texture to an object

Configuration

| Dependency | Version | Install | |-----------|---------|---------| | Blender | 3.0+ | blender.org | | Python | 3.10+ | System or python.org | | Ollama | Latest | ollama.com | | uv | Latest | pip install uv |

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

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. Blender's toolset — blender_get_scene_info, blender_get_object_info, blender_create_object and 11 more — is a fair guide to whether it matches your workflow. It is maintained by dhakalnirajan; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Blender's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• 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.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Blender.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the blender mcp server does with a few real requests.