use-blender

Drive live and headless Blender sessions through MCP servers and scripts for scene editing, rendering, and verification.

Updated Jun 30, 2026
One-click install
npx skills add https://github.com/bsamiee/Rasm --skill use-blender-bsamiee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: use-blender
Source: https://github.com/bsamiee/Rasm/tree/main/.claude/skills/use-blender
Command: npx skills add https://github.com/bsamiee/Rasm --skill use-blender-bsamiee

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires attrs, cattrs, numpy, OpenImageIO, and includes scripts (resource) and references (resource) components.

What problem does it solve? Automating Blender work requires choosing between a live GUI session and headless processes, handling undo steps, context overrides, and verifying that changes actually happened. This Skill routes every job to the right tool across two MCP servers and a set of scripts, so scene edits, renders, conversions, and drawings run deterministically without disturbing the user's open Blender window. ## Core Features & Use Cases - Live and headless execution: Run code in the user's Blender GUI through execute_blender_code with automatic undo steps, or in factory headless sessions via headless.py for long jobs, batches, and renders. - Verification with snapshots and captures: Record evaluated scene state as JSON snapshots and framed viewport or Workbench renders as PNGs, with pixel diffs against earlier captures to prove each change. - Domain workflows: Reference guides cover rendering, look development, animation, drafting sheets at scale, geometry nodes, CAD interchange, IFC/BIM authoring with Bonsai, and geospatial imports. - Use Case: Convert a batch of STEP and IFC files to glTF in a headless session, then snapshot and capture the imported geometry to confirm unit scale and object counts before delivering the files. ## Quick Start Ask the agent to open your current Blender scene, add a 2 meter cube at the origin, and show a captured front view with a snapshot of what changed.

Frequently Asked Questions about use-blender

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Blender Python scripts headless from the command line?▼

Use the headless.py script with uv run --script: `run` executes code on a file in a fresh factory process, `start` and `call` keep a named session alive between calls, and `render` renders frames. Each command prints one JSON outcome and exits 1 on failure.

How to verify a Blender scene change actually happened?▼

Read the post-condition in the call's result dict, then use snapshot.py to record evaluated transforms, bounds, and geometry counts, and capture.py to write a framed PNG. Both support a `since` argument that diffs against an earlier snapshot or capture.

Can Blender automation run without activating the GUI window?▼

Yes. Both MCP servers answer the GUI while Blender stays behind the frontmost application, pictures come from offscreen draws or window capture by id, and long jobs run in headless background processes that never touch the user's window.

Does Blender headless mode support add-ons and extensions?▼

Factory headless starts load stock add-ons and the extension wheel folder (OCP, ezdxf, rhino3dm, ifcopenshell) but no extension operators. Sessions run on a copy of the user's config folder, so preference and add-on writes stay isolated.

Why do bpy context area and region return None in automation?▼

Code run from a timer or background process has no active area or region. View operators and extension code reading context.area must run under bpy.context.temp_override with a VIEW_3D area and its WINDOW region.

How do I import IFC files into Blender with Bonsai?▼

Call bim.load_project with should_start_fresh_session=False to load an IFC into the open file, or build projects headless with ifcopenshell.api. Mesh edits require bim.update_representation before saving, or the old shape is written.