Maintainer of this skill?
A controlled AI workflow for Blender: every copilot edit is a supervised tool call—proposed, approved, executed in sequence, cancellable after the current step and undoable by name—inside a visual studio with a built-in MCP server. · blender-ai-copilot-flow · blender · blender 3d · blender addon · blender plugin · blender extension
# Add to your Claude Code skills
git clone https://github.com/tiobeharxi1987/blender-ai-copilot-flowGuides for using ai agents skills like blender-ai-copilot-flow.
See how blender-ai-copilot-flow compares with popular alternatives.
blender-ai-copilot-flow is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by tiobeharxi1987. A controlled AI workflow for Blender: every copilot edit is a supervised tool call—proposed, approved, executed in sequence, cancellable after the current step and undoable by name—inside a visual studio with a built-in MCP server. · blender-ai-copilot-flow · blender · blender 3d · blender addon · blender plugin · blender extension. It has 59 GitHub stars.
blender-ai-copilot-flow's catalog security scan is still queued. You can run an instant dependency and prompt-injection check now with the "Scan for vulnerabilities" button above.
Clone the repository with "git clone https://github.com/tiobeharxi1987/blender-ai-copilot-flow" and add it to your Claude Code skills directory (see the Installation section above).
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh blender-ai-copilot-flow against similar tools.
No comments yet. Be the first to share your thoughts!
Available after the catalog security scan passes.
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
The deep catalog scan for this skill is still queued. Run an instant dependency check now instead.
A controlled AI workflow for Blender: every copilot edit is a supervised tool call—proposed, approved, executed in sequence, cancellable after the current step and undoable by name—inside a visual studio with a built-in MCP server.
[
Nothing lands unseen: every edit is proposed, approved, run in order, and reversible by name.
The scary part of AI in a production scene is not what it builds—it is what it might change while you blink. blender-ai-copilot-flow makes every copilot action a visible step in a controlled flow: proposed before execution, approved by you, applied in sequence with earlier steps finished first, cancellable after the current operation, and undoable through named undo steps. Tool calls are validated against the allowed set before they run. You get the speed of an AI copilot with the audit trail of a pipeline.
| Without | With |
|---|---|
| Fear of a wrecked scene | Nothing runs without your approval |
| Mystery diffs you discover later | Each operation named and proposed before it executes |
| Parallel edits colliding mid-brief | Sequential execution—one ordered flow |
| No way back after a bad run | Named undo steps for every mutation |
| Runaway multi-step plans | Cancel halts the workflow after the current step |
| "Is this call even allowed?" | Python tool validation catches disallowed operations |
Every command below is self-contained: open PowerShell, copy it, paste it, press Enter.
mcp-for-blender-pro.zip from Releases.blender-ai-copilot-flow runs inside Blender as an extension: the copilot inspects your scene through 27 supervised tools, proposes each brief as a sequence of named operations, and executes them in order with your approval, a safe cancel and named undo per mutation. Python tool validation checks each call against the allowed set before it runs—it catches disallowed operations, though it is not a security sandbox—and the same supervised flow is exposed to external clients through a local authenticated endpoint (http://127.0.0.1:9876/mcp).
A careful production pass. "Add the three lights and the camera, one step at a time—show me each before the next." Approve, watch, continue; cancel anywhere after the current step.
A reversible experiment. Let the copilot rearrange a whole section; every mutation leaves a named undo step, so one pick takes the scene back to the mark you named.
Supervised scripting. When a brief needs execute_code, the snippet is proposed, validated and approved like any other step—no silent scripts.
| Setting | Default | What it does |
|---|---|---|
| Approvals | Per operation | Every tool call is proposed before execution |
| Cancellation | After current step | Stop finishes the running operation and halts the plan |
| Named undo | Every mutation | Each edit leaves a named undo step |
| Execution order | Sequential | Steps run one after another so edits stay ordered |
| Tool validation | Enabled | Disallowed operations are caught before they run |
| Workflow mode | Single assistant | Plain chat or a Team chain with the same controls |
| Provider | OpenAI | OpenAI, Anthropic Claude, Google Gemini, OpenRouter, OpenCode Zen, Ollama or Custom API |
| MCP endpoint | http://127.0.0.1:9876/mcp |
Local Streamable HTTP endpoint for external MCP clients |
| Interface language | English | English, German, French, Spanish or Chinese |
| Asset services | Optional keys | Service keys for asset providers that require them |
The copilot stopped mid-brief. Stop ends after the current step by design—approve the next step to continue, or check the last proposal for a question it asked.
How is this different from Blender's undo? Named undo steps are created per copilot mutation, so you can jump back to a specific named point instead of counting Ctrl+Z presses.
Can I skip approvals for trusted steps? Approvals are the core of the flow—but quick, low-risk edits can be approved in rapid succession.
Is validation a security sandbox? No—it catches disallowed operations before they run; treat it as a seatbelt, not a firewall.
Do external MCP clients follow the same rules? They manage their own approval policies; Blender-side visibility and undo still apply to every call.
Found a step that should be gated differently? Open an issue with the brief and the operation in question, or send a pull request. If blender-ai-copilot-flow keeps your scenes safe, a star helps others find it.
blender-ai-copilot-flow · blender · blender 3d · blender addon · blender plugin · blender extension · blender scripting · blender automation · blender mcp · blender ai · blender assistant · blender copilot · blender chatgpt · blender llm · blender agents · bpy · 3d modeling · 3d automation · mcp · mcp server · model context protocol · ai for blender · operation approvals · named undo · undo steps · cancellation · safe cancel · sequential execution · ordered steps · tool validation · supervised tools · scene tools · scene inspection · scene generation · ai modeling · ai materials · viewport screenshot · studio workspace · task board · agent teams · multi agent · product visualization · geometry nodes · 3d workflow · 3d rendering · windows 3d · ai 3d · ollama · openai · anthropic claude · google gemini · openrouter · opencode zen · model catalog · connection profiles · custom api
Released under the MIT license.