Control Blender Scenes from MCP Agents with BlenderMCP
Use BlenderMCP when an MCP-capable agent needs to inspect, create, and modify Blender scenes through a controlled Blender bridge.
npx skills add agentskillexchange/skills --skill control-blender-scenes-from-mcp-agents-with-blendermcp
uvx blender-mcp, install the upstream Blender add-on from the BlenderMCP repository, open Blender, enable the add-on, click Connect, then use the MCP client to operate the scene.Use BlenderMCP when an operator wants an MCP-capable agent to work directly inside Blender: inspect the current scene, create or transform objects, adjust materials, manipulate cameras and lights, capture viewport screenshots, import assets, or run Blender Python through the local bridge.
What this skill actually does
Invoke this instead of using Blender normally when the task benefits from natural-language iteration, agent-visible scene state, or repeatable assistant-driven 3D setup work across objects, materials, assets, and generated scene changes.
The scope boundary is Blender scene operation through an MCP server and Blender add-on. It is not a generic 3D product card, a general creative platform listing, or an MCP directory entry; the repeatable workflow is connecting a local Blender session to an MCP client and letting the agent inspect and change the scene under operator control.
Inputs and prerequisites: Blender 3.0+, Python 3.10+, uv/uvx, the BlenderMCP Blender add-on, and an MCP-capable client such as Claude Desktop or another MCP host..
Setup notes: Install uv from a trusted package manager, add an MCP server entry that runs uvx blender-mcp , install the upstream Blender add-on from the BlenderMCP repository, open Blender, enable the add-on, click Connect, then use the MCP client to operate the scene.
Source and verification boundary: use https://blendermcp.org as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a MCP workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.