blender

Enforce a spec-first Blender MCP workflow with organized collections and staged rendering.

1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/EdamAme-x/blender-mcp-skills --skill blender-edamame-x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blender
Source: https://github.com/EdamAme-x/blender-mcp-skills/tree/main
Command: npx skills add https://github.com/EdamAme-x/blender-mcp-skills --skill blender-edamame-x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Blender MCP workflows often lack governance and repeatability. This Skill enforces a spec-first, collection-ownership discipline to ensure reproducible results across shots and iterations.

Core Features & Use Cases

  • Enforces a fixed spec before any Blender setup, including timeline specs, collection plan, reference planning, and change-log governance.
  • Organizes assets via a strict collection structure (COL_SRC_ENV, COL_SHOT_010, COL_LIGHT, COL_CAM, COL_FX, etc.) to prevent asset misplacement and ensure clean handoffs.
  • Provides templates, references, and runbooks for consistency across stills, animation, and review gates, including lookdev and render workflows.
  • Supports a staged rendering protocol (EEVEE during exploration; Cycles GPU for final) with a formal Review Plan and Change Log discipline.

Quick Start

Create a fixed timeline-spec, set up collections, and begin with a basic blockout in EEVEE, then validate against the spec before any final render.

Frequently Asked Questions about blender

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

FAQPage Schema
How do I manage a Blender MCP workflow for shot-based animation production?

Manage a Blender MCP workflow by enforcing a fixed timeline-spec and strict collection-ownership discipline before setup. This ensures reproducible results across shots by organizing assets into predefined collections like COL_SHOT_010 and COL_LIGHT, preventing misplacement and ensuring clean handoffs.

What is the best way to organize Blender collections for consistent rendering and lookdev?

Organize Blender collections using a strict structure such as COL_SRC_ENV, COL_CAM, and COL_FX to prevent asset misplacement. This collection-ownership discipline ensures clean handoffs and consistent results across lookdev gates, staged rendering, and animation review cycles.

How do I set up a spec-first Blender workflow for reproducible still and animation renders?

Set up a spec-first Blender workflow by translating project goals into a fixed timeline-spec and collection plan before any blockout. Begin with EEVEE for exploration, validate against the spec, then switch to Cycles GPU for final staged rendering to ensure reproducibility.

Can I use EEVEE for lookdev exploration and Cycles GPU for final rendering in a staged workflow?

Yes, you can use EEVEE during exploration and Cycles GPU for final rendering within a staged rendering protocol. This approach pairs with a formal Review Plan and Change Log discipline to validate lookdev gates before committing to final shot outputs.

Why does my Blender MCP workflow lack repeatability across different shots and iterations?

Blender MCP workflows lack repeatability when they missing governance and a fixed spec. Without collection-ownership discipline, reference planning, and a Change Log, asset misplacement and inconsistent handoffs occur across shots and iterations.

Does a strict Blender MCP workflow require a Change Log and reference management for every project?

Yes, a strict Blender MCP workflow requires a Change Log and reference management to satisfy governance requirements. Maintaining templates, references, and runbooks ensures consistency across stills, animation, and review gates for reproducible shot-based productions.