# Resolve Conform

Conforming, relinking, and finishing prep 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-conform -g -a claude-code -y`
Codex: `npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-conform -g -a codex -y`
Cursor: `npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-conform -g -a cursor -y`
Gemini CLI: `npx skills add samuelgursky/davinci-resolve-mcp --skill resolve-conform -g -a gemini-cli -y`

## Description

Conforming, relinking, and finishing prep in the DaVinci Resolve MCP. Apply when importing/relinking editorial, checking a conform against a reference, repairing reversed/retimed subclips, tracing grades across a re-conform, building relink plans, or QCing a conformed timeline frame-by-frame, live in a running Resolve OR offline against .drt/.drp files and the project DB. Routes to the live conform tools, the offline conform QC engine, and the online-editor craft skill.

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

# Resolve Conform / Interchange
Bridges online-editing / finishing *craft* to this repo's *tools*.

- **Craft / finishing**, the global `online-editor` skill (conform, relink,
  finishing philosophy in Resolve and Flame). Use for *how a finishing editor
  thinks*, not tool mechanics.
- **Live tool mechanics**, `docs/kernels/timeline-conform-interchange-kernel.md`
  (the `timeline` conform/interchange boundary).
- **Offline conform engine**, `resolve-advanced/README.md` → `conform`,
  `color_trace`, `offline_ref`, `editorial`, `drt`, `project_db`.

## No Resolve? The work does not have to stop

`timeline author_offline` writes an importable timeline (`drt` / `otio` / `edl`) from a
file-path clip plan without any connection, and every not-connected error now carries an
`offline_alternative` block pointing at it.

Say plainly what happened: the live operation failed and a file was written, the
timeline is not in a project until someone imports it. Read the warnings back too.
`media_tc_origin_assumed` is the one that matters: OTIO source frames are
timecode-absolute, and an event without `media_start_tc_frame` imports as an *empty*
timeline with no error at all.

Default to `drt` (Resolve-native, project version 17 / Resolve 21.0, older builds need
`drt downgrade`). Pick `otio` when the plan carries retimes; a `.drt` flattens them.

## Two servers

| Job | Server | Tools |
|---|---|---|
| Import / relink / compare a **running** conform | `davinci-resolve` (Python, live) | `timeline` (conform actions), `media_pool` (`safe_relink`, `safe_import_sequence`) |
| Conform QC math, reverse-clip repair, lineage, grade tracing, `.drt`/`.drp`/DB edits with **no Resolve open** | `davinci-resolve-advanced` (Node) | `conform`, `color_trace`, `offline_ref`, `editorial`, `drt`, `project_db` |

## What this build cannot do (check before you offer it)

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