← Back to directory
D

DaVinci Resolve MCP Server

Community
MCP server for DaVinci Resolve Studio, enabling AI assistants to fully control post-production workflows via the official scripting API.
GitHub source repository ↗
★ 2.3k Stars Category · Other Very popular Source revision c3c075bcc930
71FMRS · B
Reliability
9/20
Security and permissions
15/20
Maintenance
16/20
Documentation
18/20
Setup experience
13/20

This MCP server offers comprehensive control over DaVinci Resolve Studio, covering 100% of the API methods, with two modes and high test coverage. It is designed for professional post-production, emphasizing source media safety and confirmation for destructive actions.

Read the FMRS scoring method →

This is a Model Context Protocol (MCP) server that lets AI assistants control DaVinci Resolve Studio through the official Scripting API. It provides full API coverage (349/349 methods) plus guarded workflow helpers for editing, media pool organization, render setup, review markers, grading, Fusion, Fairlight, project lifecycle, extension authoring, and source-safe media analysis. The server offers two modes: Compound (34 tools, default, low context usage) and Full/Granular (341 tools, one tool per API method). An optional offline Advanced server (18 tools) works on .drp/.drt/.drx files and database operations without Resolve running.

Tools

app_control
Manage Resolve app connection, page switching, project CRUD, databases, and settings.
media_pool
Safely import media, manage bins, organize media, normalize metadata, and analyze.
timeline_editing
Create and edit timelines, handle clips, tracks, ranges, gaps, and conform operations.
media_analysis
Source-safe analysis of media files, including sync event detection, transcription, visual analysis, and metadata writeback.
review_markers
Add, copy, and manage timeline/project markers, generate review reports.
color_grading
Inspect node graphs, validate CDLs, manage versions, stills, and color groups.
fusion
Create and manage Fusion compositions, tools, and connections.
audio
Inspect audio tracks and properties, support voice isolation and auto-sync.
render_deliver
Configure render settings, validate formats and codecs, manage render queue.
extension_authoring
Helper lifecycle for Fuse, DCTL, and Lua/Python script extensions.

Setup

  1. Open DaVinci Resolve Studio (18.5+), set Preferences > General > External scripting using to 'Local'. 2. Run npx davinci-resolve-mcp setup or clone the repo and run python install.py. 3. The installer configures Claude Desktop, Claude Code, Cursor, VS Code, etc. 4. For the free edition, run python scripts/install_resolve_bridge.py and set DAVINCI_RESOLVE_BRIDGE=1.
claude_desktop_config.json
{
  "mcpServers": {
    "davinci-resolve": {
      "command": "<python>",
      "args": [
        "<path>/src/server.py"
      ]
    }
  }
}

Fit and risk

Best for

  • Video editing and post-production professionals
  • Colorists using DaVinci Resolve Studio
  • Assistant editors needing workflow automation
  • Teams wanting to integrate AI assistants for media management

Not for

  • Users relying solely on the free edition of DaVinci Resolve (requires bridge, may be unstable)
  • Those needing a network service or server-side deployment (local stdio only)
  • Those wanting automatic selection of the best take (not provided)
  • Those wanting automatic cutting to music (not provided)

Required permissions

  • Launch and control DaVinci Resolve application
  • Read and write Resolve project database
  • Read and write local media files (for analysis)
  • Perform destructive actions (with confirmation)
  • Execute external commands (e.g., ffmpeg)

Risks and side effects

  • May modify project data; ensure backups
  • Analysis tools do not modify source media, but may write metadata
  • Destructive operations require caution
  • Free edition bridge may be closed by Blackmagic

Troubleshooting

  1. Check Resolve is set to 'Local' for scripting
  2. Verify Python version is 3.10-3.12 (or newer compatible)
  3. Run `python scripts/doctor.py` to check dependencies
  4. Refer to logs and API coverage docs
  5. If using free edition, confirm bridge is installed and running

Use cases

List all projects and open one called 'My Film'
Create a timeline from all clips in the current bin
Build a multicam prep timeline
Detect 2-pops or slate claps for sync
Probe timeline for gaps, overlaps, missing media
Build a ProRes 422 HQ render plan
Copy review markers from timeline to clip
Create a Fusion TextPlus overlay

Supported clients

Claude DesktopFull support
Claude CodeFull support
CursorFull support
VS CodeFull support
WindsurfFull support
ZedFull support
ContinueFull support
ClineFull support
Roo CodeFull support
OpenCodeFull support
JetBrains IDEsFull support