Codex DaVinci Resolve MCP
The Codex DaVinci Resolve MCP is a safety-first local server that lets AI inspect, create, edit, export, and render videos in DaVinci Resolve, with built-in safeguards against destructive actions.
Health & Inspection
Check Resolve connectivity, version, and capabilities
List all projects in the current library
Inspect current project state (timelines, tracks, items, markers, media pool)
Run read-only production preflights (timeline, media, settings, disk capacity)
Discover available render formats, codecs, resolutions, and presets
Monitor render queue progress and job status
Project Management
Create, open, and save projects
Export verified DRP backups (without overwriting existing files)
Apply allowlisted project settings (frame rate, resolution, etc.)
Media & Timeline Editing
Import media files into media pool bins
Create timelines and duplicate them as versioned revisions
Append or precisely place clips on a timeline
Add and manage video, audio, and subtitle tracks (rename, enable/disable, lock/unlock)
Edit timeline item properties (transform, crop, composite)
Add timeline markers with optional custom data
Insert standard or Fusion (Text+) titles at specified timecodes
Apply LUT files to color nodes on timeline items
Rendering & Export
Configure render settings (format, codec, resolution, quality, output directory)
Queue render jobs and optionally start them immediately
Verify rendered files via
ffprobe(codec, streams, dimensions, frame rate, duration, file size, optional SHA-256)Export timelines to interchange formats (DRT, OTIO, AAF, EDL, FCPXML, CSV, ALE, CDL)
Safe Deletion (Two-Step)
Prepare a destructive action (preview + validate, returns a one-use 5-minute token)
Execute deletion only with the matching confirmation token — supports projects, timelines, timeline items, media, tracks, markers, and render jobs
Security: All tool calls use an authenticated loopback bridge with HMAC-SHA256 signatures, nonces, and timestamps, and are written to a local audit log.
Allows AI agents to control DaVinci Resolve for video editing, including project management, media import, timeline editing, rendering, and quality control.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Codex DaVinci Resolve MCP Open project 'Demo', duplicate timeline as 'Edit v2', and render H.264 to output folder."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Codex DaVinci Resolve MCP
A local, safety-first MCP server that lets Codex inspect, produce, edit, export, and render videos in DaVinci Resolve through prompts.
The connector has two interchangeable transports:
Direct for Resolve Studio with local external scripting enabled.
Authenticated loopback bridge for Resolve Lite/free. Resolve launches a persistent
fuscriptchild on127.0.0.1; requests use HMAC-SHA256 signatures, timestamp freshness, and one-use nonces, so the shared secret never travels over the socket and captured requests cannot be replayed.
The MCP surface never exposes raw Python, Lua, shell execution, arbitrary Resolve methods, network scripting, or unrestricted filesystem access.
Requirements
DaVinci Resolve 21; the verified target is Resolve Lite 21.0.2.4 from the Mac App Store.
Python 3.11 and
uv.Codex CLI/app for registration.
FFmpeg and ffprobe only for the live acceptance test.
Related MCP server: Svetovid
Production installation
Install a non-editable, workspace-independent server runtime:
uv tool install --force --python 3.11 .Install the authenticated bridge and its private configuration:
davinci-resolve-bridge-install --workspace "$PWD"The installer preserves the random token on upgrades, writes configuration files with mode 0600, and deploys applicable macOS targets for a regular Studio install, the all-users Resolve script location, and the sandboxed App Store Lite container.
Restart Resolve. Open a saved project, then choose Workspace → Scripts → Codex Resolve Bridge. The menu is available inside a project, not from the Project Manager. The bridge remains alive until Resolve exits.
Register the stable executable with Codex:
codex mcp add davinci-resolve \
--env DAVINCI_TRANSPORT=auto \
-- "$HOME/.local/bin/davinci-resolve-mcp"Recommended defense-in-depth settings in ~/.codex/config.toml:
[mcp_servers.davinci-resolve]
command = "/ABSOLUTE/PATH/TO/.local/bin/davinci-resolve-mcp"
startup_timeout_sec = 20
tool_timeout_sec = 300
required = false
default_tools_approval_mode = "writes"
[mcp_servers.davinci-resolve.env]
DAVINCI_TRANSPORT = "auto"
[mcp_servers.davinci-resolve.tools.resolve_execute_destructive_action]
approval_mode = "prompt"Start a new Codex task after registration so it discovers the server. For project-scoped configuration, adapt .codex/config.toml.example.
Supported workflows
The 27 typed MCP tools cover:
health, project listing, state inspection, production preflight, project creation/open/save, verified DRP backups, and allowlisted settings;
media import, bins, timeline creation, clip append/placement, tracks, transforms, crop/composite properties, markers, Text+ titles, and LUTs;
non-destructive, version-named timeline revisions that preserve the source edit;
render-format/codec discovery, render configuration, queueing, progress, H.264/AAC output, and DRT/OTIO/AAF/EDL/FCPXML/text exports;
bounded delivery QC using an allowlisted
ffprobeexecutable, including codec, streams, dimensions, frame rate, duration, file size, and optional SHA-256 checks;separately prepared and confirmed deletion of projects, timelines, items, media, tracks, markers, and render jobs.
Safe prompting pattern
Ask Codex to call resolve_health and resolve_production_preflight first. For an existing user project, it should export a unique .drp backup and duplicate the working timeline with a versioned name before editing. Provide idempotency keys for additive operations, inspect state after writes, rerun preflight before delivery, and call resolve_verify_media on the rendered file. Deletion is always two-step: resolve_prepare_destructive_action, then resolve_execute_destructive_action with the returned token.
Example:
Open “Product Launch”, run a 1080p/24 delivery preflight, export a versioned DRP backup, duplicate the current timeline as “Product Launch — Edit v004”, and make the requested edits only on that revision. Render H.264/AAC to my allowed output folder, verify the resulting codec, audio, dimensions, frame rate, duration, and file size, then save. Do not overwrite or delete anything.
Configuration
Variable | Default | Meaning |
|
|
|
|
| Shared bridge configuration and token |
|
| Local security audit log |
|
| Per-request timeout from 1 to 900 seconds |
| unset | Must equal |
The installer creates conservative media/output allowlists. Rerun it with --allow-root or --allow-output-root to add a directory. Paths are canonicalized before authorization, so symlink escapes are rejected. App Store Resolve can reliably access ~/Movies; the live test therefore uses ~/Movies/CodexResolveMCP.
An unsaved transient Resolve project is intentionally not auto-discarded. If resolve_create_project returns unsaved_project_active, save it in Resolve or call resolve_open_project with a known saved project and save_current=false before creating another project.
Render settings are applied in small verified groups. Some documented quality values are codec-specific; render_setting_rejected identifies the exact rejected key rather than silently accepting a partial configuration.
Plugin distribution
This repository includes a Codex plugin bundle under
plugins/resolve-studio-control and a repo
marketplace catalog at .agents/plugins/marketplace.json.
The bundle keeps the MCP server local and starts the installed
davinci-resolve-mcp executable; it never exposes the Resolve bridge to the
public internet.
For a local checkout, add the repository marketplace and install the plugin:
codex plugin marketplace add /ABSOLUTE/PATH/TO/codex-davinci-resolve-mcp
codex plugin add resolve-studio-control@codex-resolveThe installer prerequisite is Python 3.11 plus DaVinci Resolve. Install the
package and bridge first with the commands in Production installation, then start
Resolve's Codex Resolve Bridge script. The plugin's resolve-studio skill
enforces the preflight, DRP backup, versioned timeline and delivery-QC loop.
The public release site is generated from site/ and deployed through
GitHub Pages. This is an independent integration and is not affiliated with
Blackmagic Design.
Publication materials are collected in the
OpenAI submission packet, including the
copy-ready listing, exact reviewer matrix, security facts and hosted-MCP plan.
For setup and incident handling, see the public Support guide.
Verification
uv sync --all-extras --frozen
PYTHONPATH=src .venv/bin/ruff format --check .
PYTHONPATH=src .venv/bin/ruff check .
PYTHONPATH=src .venv/bin/mypy src scripts/live_e2e.py
PYTHONPATH=src .venv/bin/pytest
PYTHONPATH=src .venv/bin/python scripts/contract_check.py
uv build
uv export --frozen --no-dev --no-hashes --no-emit-project --format requirements.txt | \
uvx pip-audit --requirement /dev/stdin --progress-spinner off --strictLive verification is intentionally separate. Create and open a saved empty project named Codex MCP Bridge Bootstrap ..., start the bridge, then run:
PYTHONPATH=src .venv/bin/python scripts/live_e2e.pyThe harness generates deterministic A/V fixtures, communicates only through real MCP stdio calls, exports and verifies a DRP backup, creates a versioned timeline revision, runs studio preflight, verifies persisted edits, renders, performs MCP delivery QC plus an independent ffprobe check, exports DRT, deletes only its unique Codex MCP E2E ... project through a scoped confirmation token, and restores the bootstrap project.
See SPEC.md for the contract and acceptance gates.
Troubleshooting
Scripts shows “No Scripts”: restart Resolve after installation and open a saved project before checking Workspace → Scripts.
bridge_not_running: run Codex Resolve Bridge from the Workspace menu.bridge_timeout: inspect Resolve for a modal. If its native API remains blocked, restart Resolve and the bridge.direct_unavailable: expected on Resolve Lite;DAVINCI_TRANSPORT=autofalls back to the authenticated bridge.Render setting rejected: call
resolve_get_render_options, use returned API tokens, and omit codec-specific settings that the selected codec rejects.
Available Tools
27 toolsresolve_add_markerB
Add a timeline marker at an exact frame with optional private custom data.
Inputs: frame (required), name, note, color, +5 more. Returns: object
resolve_add_trackC
Add and optionally name a video, audio, or subtitle track.
Inputs: track_type (required), name, index, audio_type, +3 more. Returns: object
resolve_append_clipsC
Append or precisely place clips on a timeline using media IDs, names, or allowed paths.
Inputs: clips (required), timeline_id, timeline_name, idempotency_key. Returns: object
resolve_apply_lutAIdempotent
Apply an allowed local LUT file to a one-based color node on selected timeline items.
Inputs: item_ids (required), lut_path (required), node_index, timeline_id, +1 more. Returns: object
resolve_configure_renderAIdempotent
Configure a render using discovered format/codec values and an allowed output directory.
Inputs: codec (required), format (required), output_dir (required), custom_name (required), +3 more. Returns: object
resolve_create_projectA
Create and open a project, optionally applying allowlisted timeline/color settings.
Inputs: name (required), settings, media_location, reuse_existing, +1 more. Returns: object
resolve_create_timelineB
Create a timeline, optionally importing/placing strictly located clips with frame ranges.
Inputs: name (required), clips, make_current, idempotency_key. Returns: object
resolve_duplicate_timelineB
Create a saved, version-named timeline revision while preserving the source timeline.
Inputs: new_name (required), timeline_id, make_current, timeline_name, +1 more. Returns: object
resolve_edit_itemsCIdempotent
Edit allowlisted transform/crop/composite properties or enable/name timeline items.
Inputs: edits (required), timeline_id, timeline_name. Returns: object
resolve_execute_destructive_actionADestructive
Execute the exact prepared delete once; mismatched, expired, or replayed tokens fail.
Inputs: action (required), arguments (required), confirmation_token (required). Returns: object
resolve_export_project_backupB
Save and export a verified, private DRP backup without overwriting an existing file.
Inputs: output_file (required), idempotency_key, with_stills_and_luts. Returns: object
resolve_export_timelineBIdempotent
Export the selected timeline to an allowed interchange file path.
Inputs: export_type (required), output_file (required), timeline_id, timeline_name, +1 more. Returns: object
resolve_get_render_optionsARead-onlyIdempotent
Discover exact available formats, codecs, resolutions, presets, and current render choice.
Inputs: format. Returns: object
resolve_get_stateARead-onlyIdempotent
Inspect the current project, timelines, tracks, items, markers, and optionally media.
Inputs: max_items, include_media, include_timeline_items. Returns: object
resolve_healthARead-onlyIdempotent
Check Resolve connectivity, version, active context, transport, policy, and capabilities.
Inputs: no named parameters. Returns: object
resolve_import_mediaC
Import existing files from configured media roots into an optional media-pool bin.
Inputs: paths (required), bin_name, idempotency_key. Returns: object
resolve_insert_titleC
Insert a standard or Fusion title at the current or supplied timeline timecode.
Inputs: kind, text, template, timecode, +3 more. Returns: object
resolve_list_projectsARead-onlyIdempotent
List projects in the current local Resolve project-library folder without opening them.
Inputs: no named parameters. Returns: object
resolve_open_projectBIdempotent
Save the current project by default, then open an existing named project.
Inputs: name (required), save_current. Returns: object
resolve_prepare_destructive_actionBRead-onlyIdempotent
Validate and preview an exact delete request; returns a one-use five-minute token.
Inputs: action (required), arguments (required). Returns: object
resolve_production_preflightARead-onlyIdempotent
Read-only studio preflight for timeline, media, settings, render choice, and disk capacity.
Inputs: output_dir, timeline_id, require_audio, require_video, +5 more. Returns: object
resolve_queue_renderA
Add one render job from current settings and optionally start only that job.
Inputs: start, idempotency_key. Returns: object
resolve_render_statusBRead-onlyIdempotent
Inspect render queue records and authoritative status/progress without changing jobs.
Inputs: job_ids. Returns: object
resolve_save_projectAIdempotent
Save the current Resolve project and verify Resolve returned success.
Inputs: no named parameters. Returns: object
resolve_set_project_settingsBIdempotent
Apply allowlisted project settings such as frame rate and resolution, then save.
Inputs: settings (required). Returns: object
resolve_set_track_stateBIdempotent
Rename, enable/disable, or lock/unlock an existing timeline track.
Inputs: track_type (required), track_index (required), name, locked, +3 more. Returns: object
resolve_verify_mediaARead-onlyIdempotent
Verify an allowlisted media delivery with bounded ffprobe checks and optional SHA-256.
Inputs: path (required), expectations. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 27 tools
Most tools have distinct purposes, but there is some overlap between resolve_get_state and resolve_health, both providing status information. Descriptions help differentiate them.
All tools use the 'resolve_' prefix and mostly follow verb_noun naming (e.g., resolve_add_marker). However, 'resolve_production_preflight' is a noun phrase rather than a verb, breaking the pattern slightly.
27 tools is on the higher side but appropriate for a comprehensive video editing server covering project, timeline, media, color, and render operations.
Core workflows are covered (project CRUD, timeline editing, media import, rendering). Missing tools for deleting projects or timelines, and audio-specific operations, but the surface is largely complete for editorial tasks.
Maintenance
Related MCP Connectors
MCP server for Clipkit — gives AI agents a video toolbox via the Clipkit schema.
AI video editor for agents and humans: timeline, captions, color, audio and generation as MCP tools.
AI video generation MCP server for Kling, MiniMax, Luma & Hunyuan with prompt blueprints.
MCP server for Google Veo AI video generation
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceComprehensive MCP server for DaVinci Resolve with 295+ tools to control projects, timelines, editing, color grading, rendering, and more via natural language.106 PyPI7MIT
- AlicenseAqualityCmaintenanceAn MCP server that lets AI agents visually perceive and edit video inside DaVinci Resolve Studio by rendering frames and manipulating the timeline.21MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that connects AI coding assistants to DaVinci Resolve, enabling query and control through natural language.MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that exposes the complete DaVinci Resolve scripting API, enabling AI assistants to control DaVinci Resolve programmatically with over 440 tools for project management, timeline editing, color grading, rendering, and more.26MIT