<p align="center">
<a href="https://www.scenario.com/"><img src="docs/images/scenario-logo.png" height="84" alt="Scenario"></a>
</p>
<h1 align="center">Scenario for Blender</h1>
<p align="center">
<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>
<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>
<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>
<img alt="Blender 5.0 and later" src="https://img.shields.io/badge/Blender-5.0%2B-orange">
<a href="https://docs.scenario.com"><img alt="API documentation" src="https://img.shields.io/badge/documentation-api-black.svg"></a>
<a href="https://help.scenario.com"><img alt="App documentation" src="https://img.shields.io/badge/documentation-app-black.svg"></a>
<a href="https://mcp.scenario.com/docs"><img alt="MCP documentation" src="https://img.shields.io/badge/documentation-mcp-black.svg"></a>
<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>
<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>
</p>
**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](docs/KNOWN_LIMITATIONS.md) before relying on a workflow.
## Requirements
- Blender 5.0 or later, as declared in the [extension manifest](scenario/blender_manifest.toml).
- A Scenario account with API access: [sign in](#authentication), or an API key and its secret. See
[Obtain your API key](https://docs.scenario.com/get-started/documentation/quick-start-guide/step-1-obtain-your-api-key)
and [Scenario help](https://help.scenario.com) for current account requirements.
- An internet connection and Blender's **Allow Online Access** setting enabled
under Edit > Preferences > System > Network before contacting Scenario.
- Scenario generations and prompt helpers consume Creative Units (CU). Review
the displayed estimate before Generate; models, parameters and references
affect the cost. See [costs](docs/USER_GUIDE.md#costs) and the limitations above.
## Install
Install from the official extension repository so that Blender can offer updates:
1. Turn on **Allow Online Access** under Edit > Preferences > System > Network.
2. Open Edit > Preferences > Get Extensions > Repositories, choose **Add Remote
Repository** and enter `https://blender.scenario.com/repo/index.json`.
3. Find Scenario in Get Extensions and install it. It appears as "Scenario" in
Blender's Add-ons list.
4. In Scenario, open Organization settings > API Keys > Add API Key and follow
the instructions to obtain the key and secret.
5. 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.
To install from a ZIP instead, download `scenario-<version>.zip` from the
[releases page](https://github.com/scenario-labs/blender-plugin/releases) 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](docs/USER_GUIDE.md#verify-your-download)). 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](#updates).
### 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](docs/USER_GUIDE.md#switch-from-a-zip-to-the-repository)
before switching, and the [update guide](docs/USER_GUIDE.md#updates) for
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 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.
## Quick start
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](docs/USER_GUIDE.md) describes each lane and its controls.
To rate the extension or tell Scenario what to improve, use the heart in the
Scenario panel or **Feedback** in Studio. **Share anonymous usage data**, in the
extension's preferences, stays off unless you turn it on.
## Features
- [Image](docs/USER_GUIDE.md#image): generate from text or reference images and
use results as textures or references.
- [Video](docs/USER_GUIDE.md#video): generate from prompts, images or scene playblasts.
- [3D](docs/USER_GUIDE.md#3d): generate meshes, run provider edit tasks on a
selected mesh and
[apply a saved edit](docs/USER_GUIDE.md#apply-a-saved-mesh-edit) back to it.
- [Materials](docs/USER_GUIDE.md#materials): generate saved PBR texture sets and
apply them explicitly to a chosen mesh material slot.
- [Audio](docs/USER_GUIDE.md#audio): generate speech, music or sound effects and
add results to the sequencer.
- [Render Image](docs/USER_GUIDE.md#render-image): use a scene capture and look
references to produce a still.
- [Render Video](docs/USER_GUIDE.md#render-video): work with timeline captures,
a camera path planner and style references.
- [Blockout](docs/USER_GUIDE.md#blockout): turn a scene description into a
greybox layout, then refine or rebuild it.
- [Environment](docs/USER_GUIDE.md#environment): generate 360 panoramas, HDRIs
and upscales, then apply them to the scene World.
- [Prompt tools and model picker](docs/USER_GUIDE.md#the-form): browse models
and prepare prompts; prompt helpers can spend credits.
- [Floating composer](docs/USER_GUIDE.md#the-floating-composer): access the
current lane from the viewport.
- [Generations](docs/USER_GUIDE.md#generations): inspect local results and
available project history.
- [Expanded Studio view](docs/USER_GUIDE.md#expanded-studio-view): run workflows
and browse or organize Library assets.
- [Film tasks](docs/USER_GUIDE.md#film-tasks): turn a JSON recipe into shots, a
timeline, a review scene and an exported video.
## Agents (MCP)
The local `scenario-blender` server connects an authorized agent to the open
scene and generation into it. The hosted [mcp.scenario.com](https://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 its **Connect** buttons add it as `scenario-blender` to Claude
Code, Codex, Cursor or Claude Desktop. It needs no credential, so any program on
this computer can connect. 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](docs/MCP.md) for complete client setup, tool contracts,
security controls and headless configuration. The headless entry point is:
```sh
blender --background scene.blend --command scenario_blender
```
### Authentication
**Credentials > Sign in with Scenario** opens your web browser on Scenario's
sign-in page and keeps the resulting session in the extension's private state
folder, refreshed in the background, never in `userpref.blend` or a `.blend`
file, then asks which team and project the work goes to.
**Saved in Blender** uses an API key and secret from the preferences, and
**Credentials > Environment** explicitly selects an environment pair instead.
The hosted Scenario MCP service has its own authentication, described in its
linked docs. Blender stores saved API keys in its preferences, not an OS keychain.
## What leaves your machine
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. Anonymous usage data, off by default, and feedback you send go
to `blender.scenario.com`; browser sign-in exchanges and refreshes its tokens with
`clerk.scenario.com`. Saved keys, prompts, job state and media remain in
Blender preferences, extension storage or output files. Connected local agents
can read your scene and request paid work using your account. Read
[Privacy and data handling](docs/PRIVACY.md) for destinations, storage, clipboard
use and current limits.
## Documentation
Start with the [user guide](docs/USER_GUIDE.md), [known limitations](docs/KNOWN_LIMITATIONS.md)
and [changelog](CHANGELOG.md). The [documentation index](docs/index.md) links
architecture, integration status and developer references. The public HTML
handbook address is [blender.scenario.com](https://blender.scenario.com/). Build
HTML from the maintained Markdown with `make docs`; see
[documentation builds](CONTRIBUTING.md#documentation-builds) for website and
single-file outputs.
## Staying up to date
Follow [releases](https://github.com/scenario-labs/blender-plugin/releases), or
choose **Watch > Custom > Releases** on GitHub for release notifications.
## Support
Use [Support](SUPPORT.md) for bug reports, feature requests and the information
to include. Account, billing and API-key questions go to support@scenario.com
or Scenario's in-app support. Never post credentials or signed asset URLs in a
public issue.
Report vulnerabilities privately through **Security > Report a vulnerability**
or the contact in [Security](SECURITY.md); do not open a public issue.
## Development
Read [Contributing](CONTRIBUTING.md) for the pinned environment, local checks,
portable tools and isolated Blender test loop. [AGENTS.md](AGENTS.md) is the
canonical conventions contract for humans and agents; [agent tools](docs/development/agents.md)
describes the shared commands. Follow the [Code of Conduct](CODE_OF_CONDUCT.md).
Optional local hooks are installed with `make hooks`; see [installation and scope](CONTRIBUTING.md#optional-local-hooks).
Offline tests need no Scenario account. Live smoke tests spend credits and
require explicit authorization; they are outside the default checks.
Discover repository maintenance commands with
`uv run --locked --no-env-file python -m tools --help` from the repository root.
The `assets check` and `assets optimize` commands share the
[documentation image policy](CONTRIBUTING.md#screenshots) with the unit suite.
Native CI covers Blender 5.0.1, 5.1.2 and 5.2.3 on Linux and Windows for pull
requests. A separate informational workflow schedules Blender 5.1.2 checks on
macOS Apple silicon and Windows x64 weekly; see [matrix maintenance](CONTRIBUTING.md#bumping-the-blender-matrix)
for failure tracking.
## Sibling integrations
Scenario for Blender is one of several Scenario integrations. The plugins share
the Scenario name, the id `scenario` inside each host's namespace and the support
channel (support@scenario.com), not necessarily the same licence.
- [Scenario for Unity](https://github.com/scenario-labs/Scenario-Unity), Unity
package `com.scenarioinc.scenario`. Scenario for Unity is MIT-licensed; this
extension is GPL-3.0-or-later because Blender add-ons that import bpy must be
GPL-compatible.
- [Scenario skills for agents](https://github.com/scenario-labs/skills) (MIT).
- The [Scenario MCP server](https://mcp.scenario.com) provides Scenario tools
outside Blender. The [MCP guide](docs/MCP.md#local-server-and-mcpscenariocom)
explains how it relates to this extension's local server.
## Licence
Copyright 2026 Scenario Inc. First-party extension code is free software: you
can redistribute it and/or modify it under the terms of the GNU General Public
License as published by the Free Software Foundation, either version 3 of the
License, or (at your option) any later version. It is distributed WITHOUT ANY
WARRANTY; see [LICENSE](LICENSE) for the full text. First-party source headers
and the extension manifest declare GPL-3.0-or-later, and the extension ZIP
includes the same GPL text. Bundled dependencies, adopted sources and assets
retain their original licences and notices; see the
[SDK bundle](docs/SDK_BUNDLE.md) and [source adoption](docs/STUDIO_ADOPTION.md).
The [bundled icon notice](scenario/icons/README.md) records the generator, the
font option and the icons' first-party design origin. Scenario Inc. made the
exploration gallery covers (`docs/images/exploration-*.png`) and also publishes
them at [www.scenario.com/explorations](https://www.scenario.com/explorations/).
[Blender's licence guidance](https://www.blender.org/about/license/) requires a
GPL-compatible licence for published add-ons using its Python API. The
[Blender Extensions Platform](https://docs.blender.org/manual/en/latest/advanced/extensions/licenses.html)
requires GPL-3.0-or-later for add-ons it hosts. This project distributes outside
that platform and uses GPL-3.0-or-later for its first-party extension code.
The GPL grants no trademark rights: "Scenario" and the Scenario logo belong to
Scenario Inc., and Blender is a registered trademark of the Blender Foundation;
this extension is not affiliated with or endorsed by the Blender Foundation. See
[TRADEMARKS.md](TRADEMARKS.md).
### Acknowledgements
The local MCP design acknowledges
[Blender Lab's blender_mcp project](https://projects.blender.org/lab/blender_mcp)
(GPL-3.0-or-later, Blender Authors) as a design reference.
Its [project page](https://www.blender.org/lab/mcp-server/) describes
the upstream implementation, which uses a separate stdio MCP server and TCP
connection to its Blender add-on. This extension implements loopback HTTP,
main-thread tool dispatch and an opt-in Python gate.
The [SPZ reader](scenario/core/scene/spz.py) reads
[Niantic's SPZ Gaussian splat format](https://github.com/nianticlabs/spz).
The [MCP protocol module](scenario/mcp/protocol.py) supports protocol revisions
2025-06-18, 2025-03-26 and 2024-11-05.