Category · Creative and 3D MCP servers
Blender MCP Server: Drive 3D Modelling From an AI Assistant
The Blender MCP server is one of the more surprising things in the ecosystem: it lets an AI assistant manipulate a live Blender scene — creating objects, assigning materials, setting up renders, and running Python against the scene graph. That last capability is the important one. Because Blender's Python API reaches essentially everything, an MCP bridge to it means the assistant is not limited to a fixed tool list; it can script whatever the scene needs.
What this category covers
Creative and 3D MCP servers connect an assistant to design software rather than to data. The Blender server, published by Blender itself, exposes scene manipulation — object creation and transformation, material assignment, render configuration — plus arbitrary Python execution against the Blender API. It is open source and runs locally alongside your Blender instance. On the 2D side, the Figma MCP server plays a similar role for interface design.
How it works
The server communicates with a running Blender instance and registers its tools with your MCP client. You describe what you want in natural language; the assistant translates that into object operations or Python calls and executes them against the open scene. Because changes apply to the live document, the practical workflow is incremental — save often, work on a duplicate of anything valuable, and check results visually between steps rather than issuing long unattended sequences. Our MCP server examples page collects more integrations built along these lines.
Buying guide
Treat this as a scripting accelerator rather than an autonomous modeller. The assistant is genuinely good at the tedious, deterministic parts — batch renaming, procedural placement, material assignment across many objects, render configuration — and much less reliable at aesthetic judgement, which is the part you presumably want to keep anyway. Because the Python tool can execute arbitrary code against your scene, work on duplicates and commit .blend files to version control before running anything ambitious. Pair it with Context7 for Blender's Python API documentation: the API surface is large and shifts between releases, and version-accurate docs are the difference between a script that runs and one that throws on a renamed operator. Browse the full MCP server list for adjacent tooling.
The Tools, Ranked
Objects, materials, rendering, and full Python scripting against a live Blender scene. Open source, published by Blender.
Blender projects are files with texture and asset dependencies. A filesystem server scoped to your project directory lets the assistant find and organise them.
Useful for containerised render setups, letting the assistant manage the environment as well as the scene.
For studios versioning .blend files and scripts, the same repository access developers use applies to asset pipelines.
Pull reference material and documentation into the conversation while modelling.
The Blender Python API is large and changes between releases. Version-specific documentation materially improves the quality of generated scripts.