Skip to content
Back to search

blender-plugin

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.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/scenario-labs/blender-plugin with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/scenario-labs/blender-plugin'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/scenario-labs--blender-plugin/badge.svg)](/listings/scenario-labs--blender-plugin)

HTML

<a href="/listings/scenario-labs--blender-plugin"><img src="/api/listings/scenario-labs--blender-plugin/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. Download `scenario-<version>.zip` from the [releases page](https://github.com/scenario-labs/blender-plugin/releases). Keep it zipped. [Verify the download](docs/USER_GUIDE.md#verify-your-download) when checksums and attestations are supplied with that release. 2. Drag the ZIP onto a Blender window, or use Edit > Preferences > Get Extensions > Install from Disk. The extension appears as "Scenario" in Blender's Add-ons list. 3. In Scenario, open Organization settings > API Keys > Add API Key and follow the instructions to obtain the key and secret. 4. Open Edit > Preferences > Add-ons > Scenario. Leave **Credentials** set to **Saved in Blender**, paste the key and secret, then press **Test connection**. Choose an Output Folder for generated files.

Updates

Open **Preferences > Add-ons > Scenario > Updates** for repository setup, update checks and Blender's native Get Extensions manager. The official repository address is `https://blender.scenario.com/repo/index.json`; it becomes available after the first verified adopted-package release. Enable **Allow Online Access** before checking. Updates are installed only when you choose them in Blender.

A ZIP installed into Blender's local repository can still be updated with **Install from Disk**, followed by a restart. Adding the official repository does not migrate that installation's preferences or storage. See the [update guide](docs/USER_GUIDE.md#updates) for fresh installs, compatibility and manual fallback.

Why not extensions.blender.org

The [Blender Extensions terms](https://extensions.blender.org/terms-of-service/) 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 GitHub releases. Its manifest declares the permissions it uses and their reasons.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 282 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <a href="https://www.scenario.com/"><img src="docs/images/scenario-logo.png" height="84" alt="Scenario"></a>
  3. </p>
  4. <h1 align="center">Scenario for Blender</h1>
  5. <p align="center">
  6. <a href="https://github.com/scenario-labs/blender-plugin/releases"><img alt="Latest release" src="https://img.shields.io/github/v/release/scenario-labs/blender-plugin"></a>
  7. <a href="https://github.com/scenario-labs/blender-plugin/actions/workflows/ci.yml"><img alt="CI" src="https://github.com/scenario-labs/blender-plugin/actions/workflows/ci.yml/badge.svg"></a>
  8. <a href="LICENSE"><img alt="Licence GPL-3.0-or-later" src="https://img.shields.io/badge/license-GPL--3.0--or--later-blue"></a>
  9. <img alt="Blender 5.0 and later" src="https://img.shields.io/badge/Blender-5.0%2B-orange">
  10. <a href="https://docs.scenario.com"><img alt="API documentation" src="https://img.shields.io/badge/documentation-api-black.svg"></a>
  11. <a href="https://help.scenario.com"><img alt="App documentation" src="https://img.shields.io/badge/documentation-app-black.svg"></a>
  12. <a href="https://mcp.scenario.com/docs"><img alt="MCP documentation" src="https://img.shields.io/badge/documentation-mcp-black.svg"></a>
  13. <a href="https://scorecard.dev/viewer/?uri=github.com/scenario-labs/blender-plugin"><img alt="OpenSSF Scorecard" src="https://img.shields.io/ossf-scorecard/github.com/scenario-labs/blender-plugin?label=openssf+scorecard&style=flat"></a>
  14. <a href="https://www.bestpractices.dev/en/projects/15531/passing"><img alt="OpenSSF Best Practices" src="https://img.shields.io/cii/level/15531?label=openssf+best+practices&style=flat"></a>
  15. </p>
  16. **Experimental.** Bring Scenario image, video, 3D, PBR material, audio and 360
  17. environment generation into Blender. Use scene captures and selected meshes as
  18. inputs, explore camera moves, and turn a written scene description into a greybox
  19. layout with Blockout. A compact composer, sidebar, expanded Studio view and local
  20. MCP server provide access from your scene. This is a Python extension with pinned
  21. SDK dependency wheels, licensed GPL-3.0-or-later. Read the
  22. [known limitations](docs/KNOWN_LIMITATIONS.md) before relying on a workflow.
  23. ![The Scenario sidebar with all creation tabs and a clearly labelled offline Image example](docs/images/panel-image.png)
  24. ## Requirements
  25. - Blender 5.0 or later, as declared in the [extension manifest](scenario/blender_manifest.toml).
  26. - A Scenario account with API access: [sign in](#authentication), or an API key and its secret. See
  27. [Obtain your API key](https://docs.scenario.com/get-started/documentation/quick-start-guide/step-1-obtain-your-api-key)
  28. and [Scenario help](https://help.scenario.com) for current account requirements.
  29. - An internet connection and Blender's **Allow Online Access** setting enabled
  30. under Edit > Preferences > System > Network before contacting Scenario.
  31. - Scenario generations and prompt helpers consume Creative Units (CU). Review
  32. the displayed estimate before Generate; models, parameters and references
  33. affect the cost. See [costs](docs/USER_GUIDE.md#costs) and the limitations above.
  34. ## Install
  35. Install from the official extension repository so that Blender can offer updates:
  36. 1. Turn on **Allow Online Access** under Edit > Preferences > System > Network.
  37. 2. Open Edit > Preferences > Get Extensions > Repositories, choose **Add Remote
  38. Repository** and enter `https://blender.scenario.com/repo/index.json`.
  39. 3. Find Scenario in Get Extensions and install it. It appears as "Scenario" in
  40. Blender's Add-ons list.
  41. 4. In Scenario, open Organization settings > API Keys > Add API Key and follow
  42. the instructions to obtain the key and secret.
  43. 5. Open Edit > Preferences > Add-ons > Scenario. Leave **Credentials** set to
  44. **Saved in Blender**, paste the key and secret, then press **Test connection**.
  45. Choose an Output Folder for generated files.
  46. To install from a ZIP instead, download `scenario-<version>.zip` from the
  47. [releases page](https://github.com/scenario-labs/blender-plugin/releases) and keep
  48. it zipped. Verify your download: for releases that include `SHA256SUMS`, save the
  49. ZIP, `scenario-handbook-<version>.html` and `SHA256SUMS` together, check them with
  50. `sha256sum -c SHA256SUMS` (macOS: `shasum -a 256 -c SHA256SUMS`) and, with the
  51. GitHub CLI, run `gh attestation verify scenario-<version>.zip -R scenario-labs/blender-plugin`
  52. ([details](docs/USER_GUIDE.md#verify-your-download)). Historical `v*` releases have
  53. neither. Drag the ZIP onto a Blender window, or use Edit > Preferences > Get
  54. Extensions > Install from Disk, then continue with step 4. A ZIP copy does not
  55. update itself; see [Updates](#updates).
  56. ### Updates
  57. A copy installed from the official repository updates through Blender. Open
  58. **Preferences > Add-ons > Scenario > Updates** for update checks and Blender's
  59. native Get Extensions manager. Enable **Allow Online Access** before checking.
  60. Updates are installed only when you choose them in Blender. The repository offers
  61. releases from 0.10.0 on.
  62. A ZIP copy lives in Blender's local repository and does not update itself. Keep
  63. updating it with **Install from Disk**, followed by a restart, or switch to the
  64. repository: uninstall the ZIP copy first, install Scenario from the repository,
  65. then enter your key and secret again. Uninstalling deletes the ZIP copy's storage,
  66. including its stored jobs and the media that the video, sound and Film review
  67. strips Scenario added play from; past generations remain available under
  68. **Project history (cloud)** in Generations. Never keep both copies installed. Read
  69. [Switch from a ZIP to the repository](docs/USER_GUIDE.md#switch-from-a-zip-to-the-repository)
  70. before switching, and the [update guide](docs/USER_GUIDE.md#updates) for
  71. compatibility and manual fallback.
  72. ### Why not extensions.blender.org
  73. The [Blender Extensions terms](https://extensions.blender.org/terms-of-service/)
  74. restrict extensions whose functionality depends on external registration, keys
  75. or payments, including access to external services. Scenario requires an account
  76. and API credentials, so this extension is distributed through its own repository
  77. at `https://blender.scenario.com/repo/index.json`, with each release's ZIP also
  78. attached to its GitHub release.
  79. Its manifest declares the permissions it uses and their reasons.
  80. ## Quick start
  81. In the 3D viewport, press **N** and open **Scenario**, or use the Scenario button
  82. in the viewport header. Pick a lane and model, enter a prompt, add any required
  83. reference and inspect the estimate before Generate. Results appear in Generations
  84. and your Output Folder, with actions for viewing or importing supported media.
  85. The [user guide](docs/USER_GUIDE.md) describes each lane and its controls.
  86. To rate the extension or tell Scenario what to improve, use the heart in the
  87. Scenario panel or **Feedback** in Studio. **Share anonymous usage data**, in the
  88. extension's preferences, stays off unless you turn it on.
  89. ## Features
  90. - [Image](docs/USER_GUIDE.md#image): generate from text or reference images and
  91. use results as textures or references.
  92. - [Video](docs/USER_GUIDE.md#video): generate from prompts, images or scene playblasts.
  93. - [3D](docs/USER_GUIDE.md#3d): generate meshes, run provider edit tasks on a
  94. selected mesh and
  95. [apply a saved edit](docs/USER_GUIDE.md#apply-a-saved-mesh-edit) back to it.
  96. - [Materials](docs/USER_GUIDE.md#materials): generate saved PBR texture sets and
  97. apply them explicitly to a chosen mesh material slot.
  98. - [Audio](docs/USER_GUIDE.md#audio): generate speech, music or sound effects and
  99. add results to the sequencer.
  100. - [Render Image](docs/USER_GUIDE.md#render-image): use a scene capture and look
  101. references to produce a still.
  102. - [Render Video](docs/USER_GUIDE.md#render-video): work with timeline captures,
  103. a camera path planner and style references.
  104. - [Blockout](docs/USER_GUIDE.md#blockout): turn a scene description into a
  105. greybox layout, then refine or rebuild it.
  106. - [Environment](docs/USER_GUIDE.md#environment): generate 360 panoramas, HDRIs
  107. and upscales, then apply them to the scene World.
  108. - [Prompt tools and model picker](docs/USER_GUIDE.md#the-form): browse models
  109. and prepare prompts; prompt helpers can spend credits.
  110. - [Floating composer](docs/USER_GUIDE.md#the-floating-composer): access the
  111. current lane from the viewport.
  112. - [Generations](docs/USER_GUIDE.md#generations): inspect local results and
  113. available project history.
  114. - [Expanded Studio view](docs/USER_GUIDE.md#expanded-studio-view): run workflows
  115. and browse or organize Library assets.
  116. - [Film tasks](docs/USER_GUIDE.md#film-tasks): turn a JSON recipe into shots, a
  117. timeline, a review scene and an exported video.
  118. ## Agents (MCP)
  119. The local `scenario-blender` server connects an authorized agent to the open
  120. scene and generation into it. The hosted [mcp.scenario.com](https://mcp.scenario.com)
  121. server provides platform-wide collections, training, workflows and usage without
  122. requiring Blender; connect both when needed.
  123. The default local endpoint is `http://127.0.0.1:9876/mcp`. **Agents (MCP)** shows
  124. its status, and its **Connect** buttons add it as `scenario-blender` to Claude
  125. Code, Codex, Cursor or Claude Desktop. It needs no credential, so any program on
  126. this computer can connect. Connected agents can read the scene and request paid
  127. work; arbitrary Python execution is a separate opt-in permission, disabled by default.
  128. Use the [MCP reference](docs/MCP.md) for complete client setup, tool contracts,
  129. security controls and headless configuration. The headless entry point is:
  130. ```sh
  131. blender --background scene.blend --command scenario_blender
  132. ```
  133. ### Authentication
  134. **Credentials > Sign in with Scenario** opens your web browser on Scenario's
  135. sign-in page and keeps the resulting session in the extension's private state
  136. folder, refreshed in the background, never in `userpref.blend` or a `.blend`
  137. file, then asks which team and project the work goes to.
  138. **Saved in Blender** uses an API key and secret from the preferences, and
  139. **Credentials > Environment** explicitly selects an environment pair instead.
  140. The hosted Scenario MCP service has its own authentication, described in its
  141. linked docs. Blender stores saved API keys in its preferences, not an OS keychain.
  142. ## What leaves your machine
  143. Cost previews send prompts and parameters to `https://api.cloud.scenario.com`
  144. while you edit, before Generate. Upload reference sends files, scene captures or
  145. exported meshes; generation and prompt tools spend credits. Catalogs, thumbnails
  146. and result previews load from Scenario; cloud history and Library assets load
  147. when requested. Anonymous usage data, off by default, and feedback you send go
  148. to `blender.scenario.com`; browser sign-in exchanges and refreshes its tokens with
  149. `clerk.scenario.com`. Saved keys, prompts, job state and media remain in
  150. Blender preferences, extension storage or output files. Connected local agents
  151. can read your scene and request paid work using your account. Read
  152. [Privacy and data handling](docs/PRIVACY.md) for destinations, storage, clipboard
  153. use and current limits.
  154. ## Documentation
  155. Start with the [user guide](docs/USER_GUIDE.md), [known limitations](docs/KNOWN_LIMITATIONS.md)
  156. and [changelog](CHANGELOG.md). The [documentation index](docs/index.md) links
  157. architecture, integration status and developer references. The public HTML
  158. handbook address is [blender.scenario.com](https://blender.scenario.com/). Build
  159. HTML from the maintained Markdown with `make docs`; see
  160. [documentation builds](CONTRIBUTING.md#documentation-builds) for website and
  161. single-file outputs.
  162. ## Staying up to date
  163. Follow [releases](https://github.com/scenario-labs/blender-plugin/releases), or
  164. choose **Watch > Custom > Releases** on GitHub for release notifications.
  165. ## Support
  166. Use [Support](SUPPORT.md) for bug reports, feature requests and the information
  167. to include. Account, billing and API-key questions go to support@scenario.com
  168. or Scenario's in-app support. Never post credentials or signed asset URLs in a
  169. public issue.
  170. Report vulnerabilities privately through **Security > Report a vulnerability**
  171. or the contact in [Security](SECURITY.md); do not open a public issue.
  172. ## Development
  173. Read [Contributing](CONTRIBUTING.md) for the pinned environment, local checks,
  174. portable tools and isolated Blender test loop. [AGENTS.md](AGENTS.md) is the
  175. canonical conventions contract for humans and agents; [agent tools](docs/development/agents.md)
  176. describes the shared commands. Follow the [Code of Conduct](CODE_OF_CONDUCT.md).
  177. Optional local hooks are installed with `make hooks`; see [installation and scope](CONTRIBUTING.md#optional-local-hooks).
  178. Offline tests need no Scenario account. Live smoke tests spend credits and
  179. require explicit authorization; they are outside the default checks.
  180. Discover repository maintenance commands with
  181. `uv run --locked --no-env-file python -m tools --help` from the repository root.
  182. The `assets check` and `assets optimize` commands share the
  183. [documentation image policy](CONTRIBUTING.md#screenshots) with the unit suite.
  184. Native CI covers Blender 5.0.1, 5.1.2 and 5.2.3 on Linux and Windows for pull
  185. requests. A separate informational workflow schedules Blender 5.1.2 checks on
  186. macOS Apple silicon and Windows x64 weekly; see [matrix maintenance](CONTRIBUTING.md#bumping-the-blender-matrix)
  187. for failure tracking.
  188. ## Sibling integrations
  189. Scenario for Blender is one of several Scenario integrations. The plugins share
  190. the Scenario name, the id `scenario` inside each host's namespace and the support
  191. channel (support@scenario.com), not necessarily the same licence.
  192. - [Scenario for Unity](https://github.com/scenario-labs/Scenario-Unity), Unity
  193. package `com.scenarioinc.scenario`. Scenario for Unity is MIT-licensed; this
  194. extension is GPL-3.0-or-later because Blender add-ons that import bpy must be
  195. GPL-compatible.
  196. - [Scenario skills for agents](https://github.com/scenario-labs/skills) (MIT).
  197. - The [Scenario MCP server](https://mcp.scenario.com) provides Scenario tools
  198. outside Blender. The [MCP guide](docs/MCP.md#local-server-and-mcpscenariocom)
  199. explains how it relates to this extension's local server.
  200. ## Licence
  201. Copyright 2026 Scenario Inc. First-party extension code is free software: you
  202. can redistribute it and/or modify it under the terms of the GNU General Public
  203. License as published by the Free Software Foundation, either version 3 of the
  204. License, or (at your option) any later version. It is distributed WITHOUT ANY
  205. WARRANTY; see [LICENSE](LICENSE) for the full text. First-party source headers
  206. and the extension manifest declare GPL-3.0-or-later, and the extension ZIP
  207. includes the same GPL text. Bundled dependencies, adopted sources and assets
  208. retain their original licences and notices; see the
  209. [SDK bundle](docs/SDK_BUNDLE.md) and [source adoption](docs/STUDIO_ADOPTION.md).
  210. The [bundled icon notice](scenario/icons/README.md) records the generator, the
  211. font option and the icons' first-party design origin. Scenario Inc. made the
  212. exploration gallery covers (`docs/images/exploration-*.png`) and also publishes
  213. them at [www.scenario.com/explorations](https://www.scenario.com/explorations/).
  214. [Blender's licence guidance](https://www.blender.org/about/license/) requires a
  215. GPL-compatible licence for published add-ons using its Python API. The
  216. [Blender Extensions Platform](https://docs.blender.org/manual/en/latest/advanced/extensions/licenses.html)
  217. requires GPL-3.0-or-later for add-ons it hosts. This project distributes outside
  218. that platform and uses GPL-3.0-or-later for its first-party extension code.
  219. The GPL grants no trademark rights: "Scenario" and the Scenario logo belong to
  220. Scenario Inc., and Blender is a registered trademark of the Blender Foundation;
  221. this extension is not affiliated with or endorsed by the Blender Foundation. See
  222. [TRADEMARKS.md](TRADEMARKS.md).
  223. ### Acknowledgements
  224. The local MCP design acknowledges
  225. [Blender Lab's blender_mcp project](https://projects.blender.org/lab/blender_mcp)
  226. (GPL-3.0-or-later, Blender Authors) as a design reference.
  227. Its [project page](https://www.blender.org/lab/mcp-server/) describes
  228. the upstream implementation, which uses a separate stdio MCP server and TCP
  229. connection to its Blender add-on. This extension implements loopback HTTP,
  230. main-thread tool dispatch and an opt-in Python gate.
  231. The [SPZ reader](scenario/core/scene/spz.py) reads
  232. [Niantic's SPZ Gaussian splat format](https://github.com/nianticlabs/spz).
  233. The [MCP protocol module](scenario/mcp/protocol.py) supports protocol revisions
  234. 2025-06-18, 2025-03-26 and 2024-11-05.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.