Blender VSE Control

接入你的智能体
從發布者安裝。不是 PlugMCP 端點。
遠端 URL 還是本機指令? 兩種安裝方式的差異
來自發布者

Local, revision-safe Blender VSE control for AI agents: typed timeline edits, four MCP tools, bounded context, and fresh-process persistence verification.
Let AI agents edit in Blender while the timeline stays visible, editable, and under your control.
Blender VSE Control is a local, typed, revision-safe control layer for
Blender's Video Sequence Editor (VSE). Applications and agents can inspect,
edit, resume work on, and render named .blend timelines, then verify that
their changes persist. The file remains the source of truth, and human changes
remain protected.
Status: alpha. Blender 5.1 is the primary verified target. The bundled bridge declares compatibility with Blender 4.2+, but official support claims cover only the versions listed in the release notes.
Blender VSE Control is the timeline execution layer, not the creative director. For an automated workflow that runs from concept and storyboard through source-media preparation and final assembly, pair it with an available director or production-orchestration Skill:
.blend, protects human
revisions, renders when requested, and verifies that the saved timeline
persists.Media generation, sourcing, and licensing remain the responsibility of the
upper-layer workflow and its chosen tools. The resulting .blend stays
editable, so a human can intervene without giving up control.
Linux and macOS:
curl -LsSf https://raw.githubusercontent.com/Aoike123/blender-vse/main/install.sh | sh
Windows (PowerShell):
powershell -ExecutionPolicy ByPass -c "irm https://raw.githubusercontent.com/Aoike123/blender-vse/main/install.ps1 | iex"
The script installs uv when it is missing, then
installs the blender-vse-mcp command on uv's managed Python 3.12 and checks
for Blender. Register blender-vse-mcp as a stdio MCP server in your host the
same way as any other MCP server; nothing else needs configuring.
Projects always live in blender-vse-projects/ inside the folder the host runs
in, and tools take paths relative to it, such as demo.blend. Moving or
renaming the workspace keeps everything working.
stale_base error..blend
in a fresh Blender process and checks saved structural facts. It does not
inspect frames or judge visual or creative correctness.Source contributors use Python 3.10+:
python -m venv .venv
python -m pip install -e ".[dev]"
blender-vse status
To connect an Agent host from a checkout, install .[mcp] and register
blender-vse-mcp. See the local MCP guide.
The repository also includes a progressive-disclosure
blender-vse Skill. It defines prompt-level
read, patch, and recovery discipline, while the MCP server handles execution.
The server also serves this Skill as its instructions, a blender-vse prompt,
and blender-vse://skill/... resources, so one-line installs get it too.
Neither layer stores the host's conversation history.
For local Codex installation, the repository is also a validated plugin root that can build a deterministic local-marketplace archive. See the plugin guide.
Create or read a project, then use the returned revision, timeline_hash,
and observation_id in a patch:
blender-vse read ./projects/demo.blend --create
blender-vse patch ./projects/demo.blend \
--base-revision 0 \
--base-timeline-hash HASH_FROM_READ \
--read-token TOKEN_FROM_READ \
--patch-id patch-title-001 \
--commands '[{"op":"add_text","text":"Hello","channel":3,"frame_start":1,"length":90}]'
blender-vse verify ./projects/demo.blend
Read the project again before every subsequent patch. See the getting-started guide for Python examples and setup details.
For long-running Agent sessions, start with summary and request a targeted
range/detail read only when needed. Use --view full only for explicit
legacy debugging. See the context model.
One manifest, tests/test-plan.json, defines every
test profile, performance target, and hard timeout:
Run python tests/run.py list to inspect the plan. Detailed safety and CI rules
are documented in Testing.
This repository is responsible for Blender execution, allowlisted timeline
operations, revision safety, and persistence verification. It validates
externally generated
proxy manifests before
attaching them. It does not generate or source media, download or transcode
media, encode or rebuild proxies, automate general Blender 3D workflows or
arbitrary bpy operations, maintain a project-wide asset database, or provide
an agent framework. Attaching a proxy preserves the original source path, and
final rendering still uses the source media.
Blender VSE Control is released under the MIT License. The vendored Blender MCP Bridge remains under its own MIT license; see Third-party notices.
Local, revision-safe Blender VSE control for AI agents: typed timeline edits, four MCP tools, bounded context, and fresh-process persistence verification.
工具
尚無工具清單。遠端伺服器會在首次健康檢查後取得工具清單。
常見問題
在本頁複製適用於 Cursor、Claude Desktop、Claude Code 或 VS Code 的 stdio 設定。它使用發布者的安裝方式,而不是 PlugMCP 代理伺服器。
這筆記錄未列出必要的環境變數。
Blender Vse 透過 stdio 在本機執行。
上次檢查時間:2026-11-05。 Local, revision-safe Blender VSE control for AI agents: typed timeline edits, four MCP tools, bounded context, and fresh-process persistence verification.