# Resolve Delivery

Delivery, rendering, and deliverable QC in the DaVinci Resolve MCP.

- Repository: https://github.com/samuelgursky/davinci-resolve-mcp (3887 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-delivery -g -a claude-code -y`
Codex: `npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-delivery -g -a codex -y`
Cursor: `npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-delivery -g -a cursor -y`
Gemini CLI: `npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-delivery -g -a gemini-cli -y`

## Description

Delivery, rendering, and deliverable QC in the DaVinci Resolve MCP. Apply when preparing render jobs, validating render settings, QCing a finished render against a spec (video/loudness/blanking/completeness), building or reconciling a render manifest, expanding texted/textless/stems/slate deliverables, verifying media ingest, or producing a provenance/episode report, live in a running Resolve OR offline against rendered files and the project DB. Routes to the live render tools, the offline deliverable/media/provenance tools, and the deliverables craft skills.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Resolve Delivery / Deliverable QC
Bridges delivery *craft* to this repo's *tools*.

- **Craft / specs**, the global `deliverables-knowledge`, `post-supervisor`, and
  `quality-control` / `qc-domain` skills (distributor specs, mastering, QC
  discipline). Use for *what the spec should be*, not tool mechanics.
- **Live tool mechanics**, `docs/kernels/render-deliver-kernel.md` (the `render`
  planning/validation boundary + Quick Export).
- **Offline deliverable QC**, `resolve-advanced/README.md` → `deliverable`,
  `media`, `provenance`.

## Two servers

| Job | Server | Tools |
|---|---|---|
| Plan / validate / run renders in a **running** Resolve | `davinci-resolve` (Python, live) | `render`, `render_presets` |
| QC a **finished render** vs spec, verify ingest, build manifests/provenance with **no Resolve open** | `davinci-resolve-advanced` (Node) | `deliverable`, `media`, `provenance` |

## Delivery targets (the short path)

Named render intents. `list_delivery_targets` → `prepare_delivery_job(target,
target_dir)`. Ask for `prores422hq_master`, `dnxhr_hqx_master`, `h264_1080p_web`,
or an alias (`youtube`, `tiktok`, `avid`, `stems`). One definition emits BOTH the
Resolve render settings and the `deliverable_qc` spec, so the returned `qc_spec`
is what you QC the finished file against, do not hand-write a second spec.

- Format/codec resolve against the **live** matrix. A target this machine or
  license cannot render fails with the available lists; it never silently
  substitutes. Use `check_availability: true` to see what this install supports.
- Image-sequence targets return `qc_spec: null`, `deliverable_qc` probes one
  file, a sequence is many. That is expected, not a gap.
- Bitrate is deliberately unset (Resolve has no bitrate key). Pin quality
  yourself via `settings` if a spec demands it.

The rest: https://github.com/samuelgursky/davinci-resolve-mcp/blob/HEAD/.agents/skills/resolve-delivery/SKILL.md