Scenario for Blender: AI images, video, 3D and PBR materials in the viewport, plus a local MCP server for agents. Blender 5.0+ extension, GPL-3.0-or-later.
# Add to your Claude Code skills
git clone https://github.com/scenario-labs/blender-pluginGuides for using ai agents skills like blender-plugin.
Last scanned: 10/16/2026
{
"issues": [
{
"file": "README.md",
"line": 172,
"type": "secret-exfiltration",
"message": "Instruction appears to send credentials/secrets to an external endpoint",
"severity": "medium"
}
],
"status": "PASSED",
"scannedAt": "2026-10-16T08:46:39.013Z",
"npmAuditRan": false,
"pipAuditRan": true,
"promptInjectionRan": true
}See how blender-plugin compares with popular alternatives.
blender-plugin is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by scenario-labs. Scenario for Blender: AI images, video, 3D and PBR materials in the viewport, plus a local MCP server for agents. Blender 5.0+ extension, GPL-3.0-or-later. It has 301 GitHub stars.
Yes. blender-plugin passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/scenario-labs/blender-plugin" and add it to your Claude Code skills directory (see the Installation section above).
blender-plugin is primarily written in Python. It is open-source under scenario-labs on GitHub, so you can review or fork the full source.
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-plugin against similar tools.
No comments yet. Be the first to share your thoughts!
30 days in the Featured rail · terms & refunds
⚠️ 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.
Automated security scan — not a certification.
Experimental. Bring Scenario image, video, 3D, PBR material, audio and 360 environment generation into Blender. Use scene captures and selected meshes as inputs, explore camera moves, and turn a written scene description into a greybox layout with Blockout. A compact composer, sidebar, expanded Studio view and local MCP server provide access from your scene. This is a Python extension with pinned SDK dependency wheels, licensed GPL-3.0-or-later. Read the known limitations before relying on a workflow.

Install from the official extension repository so that Blender can offer updates:
https://blender.scenario.com/repo/index.json.To install from a ZIP instead, download scenario-<version>.zip from the
releases page and keep
it zipped. Verify your download: for releases that include SHA256SUMS, save the
ZIP, scenario-handbook-<version>.html and SHA256SUMS together, check them with
sha256sum -c SHA256SUMS (macOS: shasum -a 256 -c SHA256SUMS) and, with the
GitHub CLI, run gh attestation verify scenario-<version>.zip -R scenario-labs/blender-plugin
(details). Historical v* releases have
neither. Drag the ZIP onto a Blender window, or use Edit > Preferences > Get
Extensions > Install from Disk, then continue with step 4. A ZIP copy does not
update itself; see Updates.
A copy installed from the official repository updates through Blender. Open Preferences > Add-ons > Scenario > Updates for update checks and Blender's native Get Extensions manager. Enable Allow Online Access before checking. Updates are installed only when you choose them in Blender. The repository offers releases from 0.10.0 on.
A ZIP copy lives in Blender's local repository and does not update itself. Keep updating it with Install from Disk, followed by a restart, or switch to the repository: uninstall the ZIP copy first, install Scenario from the repository, then enter your key and secret again. Uninstalling deletes the ZIP copy's storage, including its stored jobs and the media that the video, sound and Film review strips Scenario added play from; past generations remain available under Project history (cloud) in Generations. Never keep both copies installed. Read Switch from a ZIP to the repository before switching, and the update guide for compatibility and manual fallback.
The Blender Extensions terms
restrict extensions whose functionality depends on external registration, keys
or payments, including access to external services. Scenario requires an account
and API credentials, so this extension is distributed through its own repository
at https://blender.scenario.com/repo/index.json, with each release's ZIP also
attached to its GitHub release.
Its manifest declares the permissions it uses and their reasons.
In the 3D viewport, press N and open Scenario, or use the Scenario button in the viewport header. Pick a lane and model, enter a prompt, add any required reference and inspect the estimate before Generate. Results appear in Generations and your Output Folder, with actions for viewing or importing supported media. The user guide describes each lane and its controls.
The local scenario-blender server connects an authorized agent to the open
scene and generation into it. The hosted mcp.scenario.com
server provides platform-wide collections, training, workflows and usage without
requiring Blender; connect both when needed.
The default local endpoint is http://127.0.0.1:9876/mcp. Agents (MCP) shows
its status and bearer token and provides client setup for Claude Code, Cursor,
Claude Desktop and Codex under the name scenario-blender. Treat the token and
copied setup as secrets. Connected agents can read the scene and request paid
work; arbitrary Python execution is a separate opt-in permission, disabled by default.
Use the MCP reference for complete client setup, tool contracts, security controls and headless configuration. The headless entry point is:
blender --background scene.blend --command scenario_blender
Scenario API requests use an API key and secret. Saved Blender credentials are the default; Credentials > Environment explicitly selects an environment pair instead. The extension does not provide browser OAuth sign-in. The hosted Scenario MCP service has its own authentication, described in its linked docs. Blender stores saved credentials in its preferences, not an OS keychain.
Cost previews send prompts and parameters to https://api.cloud.scenario.com
while you edit, before Generate. Upload reference sends files, scene captures or
exported meshes; generation and prompt tools spend credits. Catalogs, thumbnails
and result previews load from Scenario; cloud history and Library assets load
when requested. Saved keys, prompts, job state and media remain in Blender
preferences, ex