DaVinci Resolve MCP Server (samuelgursky)

Lets AI assistants control Resolve through the official Scripting API: full API coverage plus guarded helpers for editing, media pool organization, render setup, review markers, grading, Fusion and Fairlight.

View on GitHub →

How to set it up

  1. In Resolve Studio set Preferences > General > External scripting using > Local.
  2. Run the npm launcher; it installs a managed copy, creates a virtual env and detects Resolve paths.
  3. Let the installer configure your client (Claude Desktop, Claude Code, Cursor, Codex CLI and more).
  4. Open a project and ask the assistant to list timelines.

This is a plain-English summary of the project's own instructions. Commands and versions change, so always follow the current README at the source link.

Safety notes

  • Free-edition path: Resolve 21.1 moved Python menu scripting to Studio (per samuelgursky/davinci-resolve-mcp and 2sem/davinci-resolve-lite-mcp READMEs), so free-edition bridges that rely on the Scripts menu may not work on 21.1+.
  • Runs locally; no API key needed for core features.

General rule: open a duplicate of your project before letting any agent make changes, and read what a script does before approving it.

Alternatives and related tools

The AgentCut weekly

New AI connectors for After Effects, Premiere, Resolve and CapCut, tested setup notes, and what broke after app updates. One email a week.