# DaVinci Resolve MCP Server
English | [็ฎไฝไธญๆ](README.zh-CN.md)
[](https://github.com/samuelgursky/davinci-resolve-mcp/releases)
[](https://www.npmjs.com/package/davinci-resolve-mcp)
[](docs/reference/api-coverage.md)
[-blue.svg)](#server-modes)
[-18%20tools-blueviolet.svg)](#server-modes)
[](docs/reference/api-coverage.md#test-results)
[](https://www.blackmagicdesign.com/products/davinciresolve)
[](https://www.python.org/downloads/)
[](https://opensource.org/licenses/MIT)
A Model Context Protocol (MCP) server that lets AI assistants control DaVinci Resolve Studio through the official Scripting API. It provides full API coverage plus guarded workflow helpers for editing, media pool organization, render setup, review markers, grading, Fusion, Fairlight, project lifecycle tasks, extension authoring, and source-safe media analysis.
[](docs/guides/control-panel.md)
A local browser control panel ships with the server for inspecting Resolve state, running source-safe analysis, drilling into analyzed clips and shots, and editing analysis output inline. See the [Control Panel Guide](docs/guides/control-panel.md) for the full tour.
## Quick Start
```bash
npx davinci-resolve-mcp setup
```
Before connecting, open DaVinci Resolve Studio and set **Preferences > General > External scripting using** to **Local**. (On the **free edition** that preference does not help โ see [Free edition](#free-edition-in-app-bridge) below.) The npm launcher installs a managed copy under your user application-data directory, then runs the universal Python installer. The installer creates a virtual environment, detects Resolve paths, and can configure Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Zed, Continue, Cline, Roo Code, OpenCode, Codex CLI, and JetBrains IDEs.
For source installs:
```bash
git clone https://github.com/samuelgursky/davinci-resolve-mcp.git
cd davinci-resolve-mcp
python install.py
```
For platform paths, client-specific config, and manual setup, see [Installation and Configuration](docs/install.md).
The installer and server check the latest GitHub release for MCP updates. Checks are best-effort and throttled; the server never blocks MCP startup for a prompt. The installer can prompt, snooze, ignore a release, disable checks, or apply an opt-in safe auto-update for clean git checkouts.
## Free edition (in-app bridge)
Blackmagic gates *external* scripting to Studio: on the free edition
`scriptapp("Resolve")` refuses a foreign process, whatever the preference says.
Through Resolve 21.0.x the **Workspace โธ Scripts** menu was not gated โ a script
launched from it is handed the live `resolve` object (measured on free 21.0.3.7) โ
so the server can reach the free edition through a small script that runs *inside*
Resolve and re-exports it over an authenticated loopback listener. **Resolve 21.1
moved Python scripting to Studio.** On free 21.1 the Scripts menu no longer lists
`.py` files at all (reported on Fedora 44 in #203; a Lua script in the same folder
lists normally). Whether the Console still runs Python there is unconfirmed, so
treat the bridge as a 21.0.x path until that is measured.
```bash
python scripts/install_resolve_bridge.py
# restart Resolve, open a project, then: Workspace > Scripts > resolve_bridge
```
The installer and MCP client use `~/.config/davinci-resolve-mcp/bridge.json`
by default. To keep the authenticated bridge config elsewhere, set
`DAVINCI_RESOLVE_BRIDGE_CONFIG` while running the installer and in the MCP
client environment; both sides will use that path.
Once that listener is running it is used **automatically** whenever external
scripting is unavailable โ no environment variable required. Setting
`DAVINCI_RESOLVE_BRIDGE=1` *forces* the bridge instead: it becomes the only
transport tried, so a bridge that stops answering reports its own fault rather
than quietly falling back to another transport. Use it when the bridge is the
path you intend to depend on.
On **macOS**, Resolve looks for Python 3 in exactly two places: the
`PYTHON3HOME` environment variable, then `/usr/local/bin/python3`. Homebrew,
pyenv, uv and conda land in neither, so the script silently never appears in the
menu. A python.org install works because its installer creates
`/usr/local/bin/python3` โ but you do not need one: point Resolve at the
interpreter you already have, no `sudo` required.
```bash
launchctl setenv PYTHON3HOME "$(python3 -c 'import sys; print(sys.prefix)')"
```
Use `launchctl setenv`, not `export` โ Resolve is launched from the Dock and
never sees your shell's environment. Restart Resolve afterwards. A Lua canary is
installed alongside so you can tell "Python not detected" apart from a wrong
folder.
Two things that bite (#182). The prefix must contain **both**
`lib/libpython3.X.dylib` and `bin/python3` under that exact **unversioned**
name โ Homebrew's framework builds often ship only `bin/python3.13`, which is
half a Python as far as Resolve is concerned, and the installer's preflight now
says so instead of reporting a usable prefix. And `launchctl setenv` **does not
survive a reboot**; if scripts stop listing weeks later with no error, that is
why. For something persistent, put an interpreter where Resolve already looks
(this one needs `sudo`, and check that `/usr/local/bin` does not precede your
normal Python on `PATH`):
```bash
sudo ln -s "$(command -v python3)" /usr/local/bin/python3
```
Validated on free 21.0.3.7 and Studio 19.1.3.7, both macOS. The Windows paths
added in v2.70.1 (issue #106) shipped unverified; reports on free 21.0.1.11
(issue #109) and free 21.0.3.7 (issue #112) have since shown the bridge
installing, listing and serving from **both** `%PROGRAMDATA%` and `%APPDATA%` on
Windows 11, so those paths are now confirmed rather than assumed. Linux is
confirmed as well: a report on free 20.3.2.9 (issue #129, Fedora 43) shows the
bridge installing to `~/.local/share/DaVinciResolve/Fusion/Scripts/Utility`,
listing against the system Python โ Linux has none of this discovery problem โ
and serving end-to-end. No platform now rests on an assumption: macOS was
validated directly, Windows and Linux on user reports.
Note that the bridge holds its port for as long as it serves. Before v2.70.3 a
Windows bridge could outlive Resolve and block the next session's listener; if
you are on an older build and a bridge stops answering, check for a stale
`fuscript.exe` still holding the port.
This is the documented in-app path, not a licence circumvention, but Blackmagic
could close it โ treat it as a supported-until-it-is-not tier. Loopback only,
HMAC-signed requests, one-use nonces.
## Local Control Panel
Launch the single-user local control panel from the repository root:
```bash
venv/bin/python -m src.control_panel
```
The command starts a loopback-only server and opens the control panel in your browser at a URL that carries a per-launch access token (`http://127.0.0.1:8765/#token=โฆ`) โ use that exact URL; the panel refuses requests without it. To have an AI coding agent do this, ask: **"Open the Resolve MCP control panel for this repo."** Agents should use `venv/bin/python -m src.control_panel` unless your Python environment is already active. Persisted analysis jobs refresh the local search index automatically after successful slices; the manual Build Index action is for rebuilding from existing reports.
## Server Modes
| Mode | Entry point | Tools | Best for |
|------|-------------|-------|----------|
| Compound | `src/server.py` | 37 | Default mode for most assistants. Related Resolve operations are grouped behind action parameters to keep context usage low. |
| Full / granular | `src/server.py --full` or `src/resolve_mcp_server.py` | 390 | Power users who want one MCP tool per Resolve API method. |
The compound server is recommended unless you specifically need the granular one-tool-per-method surface.
### Advanced server โ beyond the scripting API (optional, Node)
The same package ships a second, optional MCP server: **`davinci-resolve-advanced-mcp`** (bin
`bin/davinci-resolve-advanced-mcp.mjs`). Where the Python server drives a *live* Resolve over the
sanctioned scripting API, the advanced server does what the API **can't** โ it reads and edits Resolve
**files** (`.drp` / `.drt` / `.drx`) and applies DB/XML-level changes **with no Resolve running**, so it
runs cloud *or* local. 18 tools: `drp`, `drt`, `drx` (per-clip grade codec **plus a deterministic,
offline grading/QC catalog** โ within-camera + cross-camera skin (v2 skin-line metric) + b-roll +
neutral-patch WB matching, match-to-reference, saturation/black-balance, contrast-normalize, ASC CDL
import, lossless grade-transfer + season-look authoring, named-LUT attach, scope reads + intent tags,
verify-grade, display-referred frame extraction, broadcast-legal QC), `offline_ref`,
`conform` (frame-oracle conform/relink QC + lineage), `color_trace` (carry grades across a re-conform),
`fusion`, `audio_plan`, `fairlight` (bus routing), `audio`, `project_read`, `project_db`, `pipeline`
(a **DB-as-truth pipeline**: compile YAML project specs into a canonical SQLite DB, then run stages with
gates, provenance, and intentโactual drift detection), `capabilities`, `deliverable` (deliverable QC /
compliance), `media` (media front-end / AE ingest), `editorial` (editorial integrity / changelist),
`provenance` (provenance / audit / episode report). It can also be consumed **as a
library** (importable engine API), not just spawned as a server.
DRX grade writes are **live-calibrated against Resolve Studio**: grade params take Resolve's
on-screen panel units by default (`space: 'ui' | 'drx'`), and the structural writes (power windows,
qualifiers, HDR zones, HSL curves, ColorSlice, blur/key/motion-effects) are panel-readback-verified โ
per-control status in `resolve-advanced/vendor/drx-parameters/CALIBRATION-STATUS.md`. It also closes
a UI-only gap: **programmatic "Cleanup Node Graph"** (`drx` `relayout` for one clip, `project_db`
`relayout_node_graphs` for a whole project) โ node layout tidied, grade content byte-preserved.
Add it alongside the live server (both ship in one `npm install`):
```json
{
"mcpServers": {
"davinci-resolve": { "command": "<python>", "args": ["<path>/src/server.py"] },
"davinci-resolve-advanced": { "command": "node", "args": ["<path>/bin/davinci-resolve-advanced-mcp.mjs"] }
}
}
```
`install.py` prints both entries. The core is pure-JS/MIT with no required native modules; a few features
need user-installed tools (ffmpeg for `audio`, `sharp`/`better-sqlite3` for some paths) โ call the
`capabilities` tool for live status and install hints.
Unlike the Python server, this one has Node dependencies. `npx davinci-resolve-mcp setup` installs them
into the managed install (`npm install --omit=dev --omit=optional` under `resolve-advanced/`) and only
then registers the bin. If that install could not run โ offline, or npm unavailable โ setup registers
an `npx` command for the advanced server instead, so the entry it writes always boots. To repair an
existing install without re-running setup: `npx davinci-resolve-mcp sync`.
### Bradford Post Assistant โ managed application (closed beta)
The maintainers also build **Bradford Post Assistant**, a desktop application on top of this
open foundation. Where the MCP servers give an agent hands, Post Assistant is the working
copilot around them โ an on-device AI assistant for post-production where client material
never leaves the workstation:
- **A post-production copilot** โ a desktop app that sits alongside DaVinci Resolve and
watches the session live (timeline, grades, and frames โ not just API calls), with an
embedded AI assistant and agent runtime, local media analysis (transcription, frame
analysis, editorial intelligence), and in-app conform QC.
- **Memory** โ persistent, encrypted on-device assistant memory plus cross-episode learning
mined from your pipeline's decoded facts (season-look drift, per-camera correction priors,
hero-frame libraries, conform path-map reuse), with accumulation managed for you and a
reviewed-insight workflow.
- **Self-contained by design** โ Post Assistant wires everything itself: this MCP for
Resolve control, the Bradford API for its extended services, and your choice of LLM
provider. Nothing to configure by hand, no separate clients to manage, and the app keeps
itself (and its bundled MCP) current with signed auto-updates.
- **An extended professional toolset** โ grade surgery on live projects, 22+ adaptive grade
families, a curated looks library, delivery-spec validation, editorial pacing/cleanup
analysis, natural-language color direction, and Fusion composition authoring โ delivered
through the managed Bradford API.
- **Production workflows** โ the raw tools composed into finished, real-world flows
(turnover โ conform โ QC โ delivery, season-look carry, episode reporting) with the
guardrails and approvals a client-facing shop expects.
It is currently in **closed beta** โ you can request access at
[bradfordoperations.com/software/post-assistant](https://www.bradfordoperations.com/software/post-assistant).
The open-source servers are complete and fully functional on their own.
## What You Can Do
```text
"List all projects and open the one called 'My Film'"
"Create a timeline called 'Assembly Cut' from all clips in the current bin"
"Build a multicam prep timeline from selected camera angles and preserve source media"
"Detect 2-pops or slate claps and suggest record offsets for sync prep"
"Publish analysis summaries, keywords, people, and slate hints into Resolve clip metadata"
"Probe this timeline for gaps, overlaps, missing media, and source frame ranges"
"Safely import this image sequence, organize it into bins, and normalize clip metadata"
"Build a ProRes 422 HQ render plan, validate the settings, and queue the job"
"Copy review markers from the timeline to the selected clip and export a review report"
"Snapshot this clip's grade, validate a CDL update, and export a temp LUT"
"Create a Fusion TextPlus overlay on the selected clip and verify graph connections"
"Report audio channel mappings, voice isolation availability, and subtitle support"
"Install this MCP-marked DCTL or script, classify refresh/restart needs, then remove it"
```
## Core Capabilities
| Area | What the compound server supports |
|------|-----------------------------------|
| App and project control | Launch/reconnect, page switching, project CRUD, project folders, databases, cloud project wrappers, settings, presets, archives |
| Media pool and ingest | Safe import, image sequences, multicam prep timelines, bin organization, metadata normalization, metadata field inventory, marks, annotations, relink/proxy/full-resolution guards |
| Media analysis | Source-safe file/clip/bin/project analysis, 2-pop/slate-clap sync-event detection, default Resolve metadata and Media Pool marker writeback, persisted analysis artifacts, existing-report reuse, host_chat_paths visual analysis (finalized per clip with `commit_vision`, works with any vision-capable MCP client) with opt-out, transcription with opt-out |
| Timeline editing and conform | Track/item probing, title text key scans/writes, copy/move/duplicate helpers, ripple insert, range operations, gaps/overlaps, source ranges, checked interchange exports/imports |
| Review annotations | Timeline/item/clip markers, custom data, flags, clip color, copy/move/sync cleanup, review reports, marker thumbnail review |
| Color and grading | Node graph probing, CDL validation, grade copy, DRX/LUT helpers, versions, Gallery stills, color groups |
| Fusion | Timeline-item comps, safe tool creation, input writes, port inspection, validated connections, scoped bulk writes |
| Audio and Fairlight | Track/item probes, source mapping, guarded audio property writes, voice isolation, auto-sync planning, transcription/subtitle probes |
| Render and deliver | Format/codec matrix probing, render settings validation, queued job lifecycle checks, guarded Quick Export |
| Extension authoring | Fuse, DCTL, ACES DCTL, and Resolve-page Lua/Python script lifecycle helpers with safe MCP-marked install/remove |
| Craft guidance | The bundled editorial, colour, audio, and workflow guidance served as prose over MCP โ indexed, searchable, and readable by any client, not just ones with this repository on disk |
### Operation envelope
Every compound tool return carries an `_operation` block beside its payload, so
an agent reads one shape instead of a different key per tool: `status`
(`success` / `partial` / `blocked` / `failed`), `verification` (with
`contradiction` kept distinct โ Resolve reported success and the readback
disagreed), `changes` (the semantic delta), `warnings`, and an `execution_id`.
Two absences are meaningful and deliberate. `verification.status: "unverified"`
means *no evidence was reported*, not "checked and clean". A missing `changes`
means the action did not report a delta, not that nothing changed โ an empty
`{}` there would be a confident, wrong answer about an edit that simply never
declared one.
The envelope is namespaced rather than merged into the top level because
`status`, `operation`, `warnings`, `result` and `changes` are all already domain
keys here; flattening would rewrite a background job's `status: "done"` and a
confirm gate's `status: "confirmation_required"`. `setup(action="set_defaults",
params={"result_envelope": "pure" | "legacy"})` changes the shape, per call via
`params={"envelope": ...}`, per process via `RESOLVE_MCP_RESULT_ENVELOPE`.
### Agent execution traces ("Why did the editor do this?")
Multi-step AI operations correlate across tool calls into unified execution
traces. Each trace aggregates tool durations (`duration_ms`), call counts, cumulative
semantic deltas (`items_deleted`, `items_added`), and readback verifications.
Agents and editors can inspect workflows via `resolve_control`:
`get_execution_trace(execution_id?)`, `list_recent_executions()`, or open a
scoped execution with `begin_execution(request="...")` / `end_execution()`.
`export_execution_report(execution_id?, format="markdown"|"json")` writes a
reviewable audit artifact with the same summary, defaulting to
`logs/execution-reports/<execution_id>.md`. `path` writes it anywhere you want
it instead โ alongside a conform in a dated TransferFiles folder, say โ and
creates the directories to get there, so check the path before you send it.
An existing file is never replaced without `overwrite: true`.
`inspect_operation(tool?, target_action?, target_params?)` evaluates pre-flight
risk level (`low`, `medium`, `high`, `critical`), destructive potential, and blast
radius (`item`, `track`, `timeline`, `project`, `system`) before taking action, while
`list_lifecycle_hooks()` inspects active execution interceptors.
It is a heuristic over action names, not a simulation โ it never touches the
project and does not validate your parameters, so `recognised: false` means the
levels are defaults rather than a finding, and `snapshot_available: null` means
rollback availability was not determined rather than absent. Every shipped hook
observes; none replaces a tool's result, so `dry_run` always reaches the real
handler and nothing synthesises a preview for an action that has none.
A report for a run where nothing was verified says **"not established โ no
checks recorded"**, not "passed". Absence of evidence is a question still open,
and an audit document is the last place to let a reader read it as an all-clear.
Traces live in a 100-entry in-memory ring and are appended to
`logs/execution-traces.jsonl` beside `server.log` โ `RESOLVE_MCP_TRACE_FILE`
moves it, and `RESOLVE_MCP_LOG_FILE` moves `server.log` itself (a path, or empty
for no file; the offline test suite points it at a temporary file so it never
writes into the operator's log). `list_recent_executions` reports that path and whether it is
writable, so "the log is empty" and "nothing is being written" are
distinguishable without reading the source. What is recorded is tool name,
action, timing, status, semantic deltas and verification โ no parameters and no
file paths. The one free-text field is the `request` you pass to
`begin_execution`, so treat it the way you would a commit message on a client
project.
## Verified-Trap Guard
`src/utils/api_truth.py` records behaviours of the Resolve API that were measured
against a live build rather than read off a signature โ calls that return `True`
having done nothing, settings keys silently rejected, methods that are not there
at all. That ledger used to be **pull-only**: it answered
`resolve_control(action="api_truth")` and was otherwise a file nobody greps in
the middle of a job.
It now reaches the caller at the callsite. An action mapped to a symbol with a
recorded fact carries a compact `known_limitation` on its result โ symbol,
reality, recommendation, and nothing else, because response weight is a real cost
on a long grading session and the full entry is one lookup away.
A fact is only attached when the mapping names that exact symbol. Nothing is
inferred from a similar name: an unrelated explanation stapled to a failure reads
as a diagnosis, and a wrong diagnosis is worse than none.
**One behaviour refuses rather than warns.** `TimelineItem.CopyGrades` replaces
the target's grade wholesale โ measured by baking each state to a 33-point LUT
and comparing bytes โ returns `True` while doing it, and creates no version to go
back to. Applied to clips carrying hand-work, that is unrecoverable loss reported
as success. So actions that call it refuse until the caller passes
`acknowledge_trap: true`:
```json
{
"success": false,
"error": "'timeline_item_color.copy_grades' is refused: its verified behaviour destroys existing work that cannot be recovered afterwards.",
"known_limitation": [{"symbol": "TimelineItem.CopyGrades", "reality": "...", "recommended": "..."}],
"retry_with": {"acknowledge_trap": true}
}
```
The intent is not to forbid the operation โ it is to make the caller say out loud
that they know what it does. Dry runs are exempt: a preview destroys nothing.
Set `RESOLVE_MCP_DISABLE_TRAP_GUARD=1` to turn both the refusal and the advisory
push off. This is a behaviour change for callers that previously received a bare
`{"success": true}` from a destructive copy.
Facts that power a refusal must stay re-measurable, so a live probe re-derives
each one and records `drifted` when Resolve stops agreeing; a test fails if a
`destroys_prior_work` entry has no probe.
## Optional Extras
The core install is deliberately small: Python, ffmpeg, and the Resolve scripting
API. Some features need more, and **each one refuses honestly with its own
install line rather than degrading into a guess** โ a fabricated tempo or an
invented level produces confident, wrong output, which is worse than no feature.
Run `python scripts/doctor.py` to see which of these you have.
| Extra | Unlocks | Licence |
|---|---|---|
| **ffmpeg** on PATH | Silence detection, dead-space markers, level measurement, audio analysis. The single most useful thing to install. | LGPL/GPL โ invoked as a subprocess, never bundled |
| `pip install numpy` | Colour pre-balance, reference-still matching, sound-density audit | BSD |
| `pip install librosa` | Beat, bar and phrase detection for music-driven cutting | ISC |
| `pip install -U openai-whisper` | Transcription, and everything word-level built on it | MIT |
| `pip install open_clip_torch` | Visual similarity and `find_similar` | MIT |
| `pip install transformers` | CLAP audio embeddings | Apache-2.0 |
| `pip install opencv-python` | Additional frame analysis | Apache-2.0 |
`media_analysis` action `capabilities` reports the analysis stack in detail and
tells you what each missing piece would enable.
**Nothing here is bundled.** Model weights carry their own licences separate from
the code that loads them; check them before commercial use.
## What This Does Not Do
Knowing where a tool stops is worth as much as knowing what it does, and it is
cheaper to read it here than to discover it mid-project.
| Not supported | Why, and what you get instead |
|---|---|
| **Choosing the best take** | Performance is most of what makes a take right, and none of it is measurable from a waveform or a transcript. `rank_takes` ranks *fluency* โ fillers, restarts, script coverage โ and says so in every response. The take that plays is regularly the least fluent one, because the hesitation is often the acting. Use it to find the clean safety take, not to choose the read. |
| **Automatic music editing** | Optional `librosa` support provides beat detection and beat/bar/phrase cut-point plans, not a finished assembly. Downbeats are inferred from the first beat; use `beat_offset` for pickups. Speech-silence tools are unsuitable for finding musical edit points. |
| **Judging a cut** | Nothing here has an opinion about whether an edit is good. Every destructive action is plan โ review โ confirm for that reason. |
| **Replacing an editor** | The output is a first-pass assembly, in the assistant-editor sense: ingest, sync, organize, string out, flag problems. It is a starting point you cut, not a finished cut. Defaults are deliberately **generous** โ a first assembly is supposed to run long, because trimming is fast and visible while recovering discarded material is slow and invisible. |
| **Modifying your source media** | By design and without exception โ see below. |
Anything analyzed but unverifiable is reported as unverified, never folded into
"fine". An empty result means "nothing found", never "nothing to find".
## Source Media Safety
This project treats camera originals and source media as immutable. Analysis tools read source files and write reports only to sidecar, scratch, or project analysis directories; confirmed metadata publishing writes only to Resolve's project database. The server must not modify, transcode, proxy, or create derivatives of source media unless the user explicitly asks for that. See [Media Analysis Guide](docs/guides/media-analysis-guide.md) for the detailed source-safe workflow.
## Security Posture
The default server is a local stdio process launched by your MCP client; it does not expose a network listener or built-in multi-user auth surface. The two opt-in local HTTP surfaces โ the control panel and the networked MCP transport โ bind loopback only and require a per-launch bearer token on every request, with Host/Origin checks against DNS rebinding and CSRF. Tool metadata includes MCP client-safety hints for read-only, destructive, idempotent, and external-resource operations. Destructive writes on both servers honour `destructive.safe_mode` and the security audit log; only the compound server archives a timeline before mutating it โ granular writes are refused or recorded, never recovered. See [Security Policy](SECURITY.md) for operational boundaries, confirmation guidance, and vulnerability reporting.
## Key Stats
| Metric | Value |
|--------|-------|
| MCP Tools | **37** compound / **390** granular (live server) |
| Advanced (offline) tools | **18** โ .drp/.drt/.drx + DB authoring, no Resolve running |
| Kernel Actions | **136** guarded workflow actions across 9 compound tools |
| API Methods Covered | **361/361** (100%) |
| Methods Live Tested | **338/361** (93.6%) |
| Live Test Pass Rate | **338/338** (100%) |
| Tested Against | DaVinci Resolve 19.1.3 Studio + Resolve 20.3.2 Studio + Resolve 21.0.2 Studio + Resolve 21.0.3 **free** (via the in-app bridge) |
For method-by-method status, see [API Coverage and Test Results](docs/reference/api-coverage.md). For current workflow support, see [Kernel Action Coverage](docs/kernels/README.md).
`analyze_media` executes directly by default, persists inspectable reports/artifacts under the analysis root, requests host-chat visual analysis via the `host_chat_paths` protocol (analyze returns absolute frame paths + a JSON schema; the host chat reads each frame as an image and calls `media_analysis(action="commit_vision", ...)` to finalize), runs transcription through the configured local backend, and writes analysis summaries plus source-time Media Pool clip markers back to the Resolve project. Pass `include_visuals=false`, `include_transcription=false`, `publish_metadata=false`, `timed_markers=no`, or `dry_run=true` only when you want to opt out of those default behaviors. Skipping `commit_vision` leaves the run in `pending_host_vision_analysis` โ surfaced as a failure mode, not silently downgraded.
## Documentation
| Document | Use it for |
|----------|------------|
| [Installation and Configuration](docs/install.md) | Requirements, installer options, supported clients, server modes, manual config |
| [API Coverage and Test Results](docs/reference/api-coverage.md) | Key stats, API coverage table, live-test status, full method reference |
| [Kernel Action Coverage](docs/kernels/README.md) | Current guarded workflow action map |
| [AI Skill Reference](docs/SKILL.md) | Operational context for AI assistants using the compound server |
| [Control Panel Guide](docs/guides/control-panel.md) | Local browser panel tour: Overview, Review (bin/clip/shot), Analyze, Setup, Preferences |
| [Media Analysis Guide](docs/guides/media-analysis-guide.md) | Source-safe FFprobe, FFmpeg, Whisper, sidecar, and analysis-root workflows |
| [Multicam Setup Helper Guide](docs/guides/multicam-setup-guide.md) | Stacked timeline prep, helper/API boundary, and Resolve UI conversion steps |
| [Editorial Decision Guide](docs/guides/editorial-decision-guide.md) | Project-owned editorial craft guidance for analysis and timeline decisions |
| [Conforming an Avid AAF](docs/guides/conforming-an-avid-aaf.md) | Why all three Resolve-native routes fail on a consolidated turnover, and which one is dangerous |
| [Native .drt Authoring](docs/guides/native-drt-authoring.md) | Offline template-spliced timeline authoring: cuts, retimes, transitions, fades, markers, compounds โ and the measured laws behind them |
| [Headless Edit Loop](docs/guides/headless-edit-loop.md) | Driving Resolve from the command line: which interchange formats relink and round-trip, measured in GUI and -nogui |
| [Color Decision Guide](docs/guides/color-decision-guide.md) | Project-owned color correction guidance and Resolve color API boundaries |
| [Contributing and Project Layout](docs/contributing.md) | Contribution workflow, platform support, security notes, repository structure |
| [Security Policy](SECURITY.md) | Local stdio trust boundary, tool metadata, confirmation guidance, reporting |
| [Release Process](docs/process/release-process.md) | Maintainer release checklist, version surfaces, validation, tags, and release notes |
| [Changelog](CHANGELOG.md) | Historical release notes |
Extension authoring references live in [docs/authoring](docs/authoring/). Resolve developer-package notes live in [docs/notes](docs/notes/) and [docs/integrations](docs/integrations/). Prompt recipes live in [examples](examples/).
## Requirements
- DaVinci Resolve 18.5+ on macOS, Windows, or Linux. **Studio** supports external scripting directly. The **free edition** does not โ Blackmagic gates external scripting to Studio โ but it is still reachable through the [in-app bridge](#free-edition-in-app-bridge), which runs inside Resolve from the ungated **Workspace โธ Scripts** menu.
- Python 3.10+ (3.10-3.12 is the lowest-risk range). Python 3.13/3.14 also work on recent Resolve builds (verified on Studio 20.3.2); older builds may fail to connect on 3.13+, in which case use 3.10-3.12.
- Not connecting? `python3 scripts/doctor.py` checks the Python the server runs on and prints the exact fix for each problem: 32-bit or wrong-architecture Python, a Python too new for your Resolve build, or several Pythons where the MCP client starts the wrong one. See [Checking the Python environment](docs/install.md#checking-the-python-environment).
- Resolve external scripting set to **Local** (Studio). On the free edition this
preference has no effect โ use the [in-app bridge](#free-edition-in-app-bridge)
instead.
Resolve 19.1.3 remains the compatibility baseline. Resolve 20.x scripting calls are additive, version-guarded, and live-tested on 20.3.2. Resolve 21.0 scripting additions (audio classification, speaker-detection transcription, IntelliSearch, slate analysis, motion-deblur, speech generation, session background-task control) are exposed behind runtime capability detection, so they stay inert on older builds and activate automatically on Resolve 21+. They are live-tested on Studio 21.0.2.4 โ see the [Resolve 21 delta](docs/reference/api-coverage.md#resolve-21-delta-detail). Note that `AnalyzeForIntellisearch`, `AnalyzeForSlate` and `GenerateSpeech` each require a separately-downloaded AI Extras pack, and Resolve reports a missing pack inconsistently (some return `False`, others an error string), so these actions report `success: false` with the Resolve-supplied reason rather than guessing.
## Reporting Bugs and Requesting Features
Tell your assistant "send this as a bug" or "send this as a feature request". It
drafts a GitHub issue from the conversation, including the failing call and
its error, and attaches the server version, Resolve build, connection mode and
OS. Local paths, your username and anything that looks like a secret are
redacted. Nothing is filed for you: you get a prefilled link, review the
draft, and submit it on GitHub yourself. You can also
[open an issue](https://github.com/samuelgursky/davinci-resolve-mcp/issues/new/choose)
directly.
## Development
```bash
python src/server.py # Compound server
python src/server.py --full # Granular server
venv/bin/python tests/test_import.py
venv/bin/python scripts/audit_api_parity.py
```
Release and validation rules are in [docs/process/release-process.md](docs/process/release-process.md). AI agents working in this repository should start with [AGENTS.md](AGENTS.md); Claude Code users can also read [CLAUDE.md](CLAUDE.md), which points to the same canonical instructions.
## License
MIT
## Author
Samuel Gursky (samgursky@gmail.com)
- GitHub: [github.com/samuelgursky](https://github.com/samuelgursky)
## Acknowledgments
- Blackmagic Design for DaVinci Resolve and its scripting API
- The Model Context Protocol team for enabling AI assistant integration