blender-ai-copilot-flow
Health Warn
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 5 GitHub stars
Code Warn
- Code scan incomplete — No supported source files were scanned during light audit
Permissions Pass
- Permissions — No dangerous permissions requested
No AI report is available for this listing yet.
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
blender-ai-copilot-flow
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.
Why
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
| 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 |
Quick Start
Every command below is self-contained: open PowerShell, copy it, paste it, press Enter.
- Download
mcp-for-blender-pro.zipfrom Releases. - In Blender, open Edit → Preferences → Get Extensions → menu → Install from Disk.
- Select the ZIP, enable mcp-for-blender-pro, then open 3D Viewport → N → MCP Pro.
- Choose a provider, add your connection details and select a model.
- Send a message in Blender or click Open Studio Window.
Features
- Approve every operation—each tool call is proposed before it runs.
- Cancel safely—Stop halts the workflow after the current step, mid-plan.
- Undo by name—mutations leave named undo steps you can pick from Blender's own controls.
- Run edits in sequence—ordered steps, no collisions between operations.
- Validate tool calls—disallowed operations are caught before execution.
- Watch each step—viewport snapshots confirm what actually changed.
- Serve the flow to MCP clients—external calls meet the same supervised pipeline.
How it works
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).
Usage
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.
Configuration
| 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 |
Troubleshooting / FAQ
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.
Contributing
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.
Keywords
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
License
Released under the MIT license.
Reviews (0)
Sign in to leave a review.
Leave a reviewNo results found