DaVinci Resolve
MCP server by Samuel Gursky
Control DaVinci Resolve Studio from your assistant: edit timelines, organize media, set up renders and work on color.
Install DaVinci Resolve
Runs on your machine. Your client starts it with this command:
Needs Node.js on your computer. The setup steps below show where the command goes in each client.
Share this server
Opens this page, with the install command and setup steps.
mcp.tc/i/davinci-resolveAbout
A community MCP server that lets an AI assistant control DaVinci Resolve Studio through its official Scripting API. It covers editing, media pool organization, render setup, review markers, grading, Fusion, Fairlight, project lifecycle tasks and source-safe media analysis. A local browser control panel is included for inspecting Resolve state.
It runs locally over stdio. Running npx davinci-resolve-mcp setup installs a managed copy, creates a Python virtual environment and can register the server with clients such as Claude Desktop, Claude Code, Cursor, VS Code and Codex CLI. No API key is needed. DaVinci Resolve Studio must be open with Preferences > General > External scripting using set to Local. This is not an official Blackmagic Design product.
What you can do
- Edit timelines and organize the media pool
- Set up and manage render jobs
- Add review markers
- Work on color grading
- Control Fusion and Fairlight features
- Handle project lifecycle tasks
- Run source-safe media analysis
Tools
Local servers list their tools once they’re running, and this one doesn’t publish its list in advance. Your client shows them after you add it.
Example prompts
Create a new timeline from the clips in my Interviews bin
Add review markers at every cut on the current timeline
Set up a render job for the current timeline as H.264 MP4
Organize the media pool into bins by clip type
Set up
Every client starts DaVinci Resolve on your machine with the same command. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport stdio davinci-resolve -- npx davinci-resolve-mcp setup- Start Claude Code and type
/mcp. davinci-resolve should show as connected.
Add --scope user to make it available in every project.
Claude Desktop
- Open Settings → Developer → Edit Config. It opens
claude_desktop_config.json. Add:
{
"mcpServers": {
"davinci-resolve": {
"command": "npx",
"args": [
"davinci-resolve-mcp",
"setup"
]
}
}
}- Save the file and restart Claude Desktop.
Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"davinci-resolve": {
"command": "npx",
"args": [
"davinci-resolve-mcp",
"setup"
]
}
}
}Needs Node.js on your computer.
VS Code
Install in VS Code (opens in a new tab)
Or from a terminal:
code --add-mcp '{"name":"davinci-resolve","type":"stdio","command":"npx","args":["davinci-resolve-mcp","setup"]}'Or commit it to the repo in .vscode/mcp.json:
{
"servers": {
"davinci-resolve": {
"type": "stdio",
"command": "npx",
"args": [
"davinci-resolve-mcp",
"setup"
]
}
}
}Needs Node.js on your computer.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"davinci-resolve": {
"command": "npx",
"args": [
"davinci-resolve-mcp",
"setup"
]
}
}
}- Refresh the MCP server list in Cascade.
Devin Desktop is the new name for Windsurf.
Codex
codex mcp add davinci-resolve -- npx davinci-resolve-mcp setupOr edit ~/.codex/config.toml directly:
[mcp_servers.davinci-resolve]
command = "npx"
args = ["davinci-resolve-mcp", "setup"]Needs Node.js on your computer.
Gemini CLI
gemini mcp add davinci-resolve npx davinci-resolve-mcp setupThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients that start local servers accept this shape:
{
"mcpServers": {
"davinci-resolve": {
"command": "npx",
"args": [
"davinci-resolve-mcp",
"setup"
]
}
}
}Zed puts servers under context_servers in its settings, with the same command, args and env fields.
Needs Node.js on your computer.
Embed
Show DaVinci Resolve in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work
The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.
README badge
[](https://mcp.tc/i/davinci-resolve)<a href="https://mcp.tc/i/davinci-resolve"><img src="https://mcp.tc/i/davinci-resolve/badge.svg" alt="DaVinci Resolve on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/davinci-resolve.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/davinci-resolve" title="DaVinci Resolve on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/davinci-resolve.jsonAI prompt
Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the DaVinci Resolve card to your site.
Add the mcp.tc card for DaVinci Resolve, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.
Put this tag where the card should appear. The card renders right before it:
```html
<script src="https://mcp.tc/w/davinci-resolve.js" async></script>
```
To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.
```html
<div data-mcptc="davinci-resolve"><a href="https://mcp.tc/i/davinci-resolve">DaVinci Resolve on mcp.tc</a></div>
```
Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.
If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).
For a README or other Markdown docs, use the badge instead:
```markdown
[](https://mcp.tc/i/davinci-resolve)
```
Reference: https://mcp.tc/embedChange history
This server runs on your computer, so we follow its npm package: each new version shows up here, with edits by its owner.
-
New version 5.3.4 (was 5.3.3). Read from npm.
-
New version 5.3.0 (was 5.2.11). Read from npm.
-
New version 5.2.8 (was 5.2.7). Read from npm.
-
New version 5.2.7 (was 5.2.2). Read from npm.
-
New version 5.0.7 (was 5.0.3). Read from npm.
-
New version 5.0.0 (was 4.19.3). Read from npm.
-
New version 4.19.1 (was 4.19.0). Read from npm.
-
New version 4.18.6 (was 4.18.5). Read from npm.
-
New version 4.18.3 (was 4.18.2). Read from npm.
-
New version 4.18.0 (was 4.17.0). Read from npm.
-
New version 4.17.0 (was 4.16.0). Read from npm.
-
New version 4.15.5 (was 4.15.3). Read from npm.
-
New version 4.15.0 (was 4.14.4). Read from npm.
-
New version 4.14.4 (was 4.14.3). Read from npm.
-
New version 4.14.0 (was 4.13.7). Read from npm.
-
New version 4.13.6 (was 4.13.2). Read from npm.
-
New version 4.13.2 (was 4.13.1). Read from npm.
-
New version 4.13.1 (was 4.10.6). Read from npm.
-
New version 4.10.6 (was 4.10.4). Read from npm.
-
New version 4.10.4 (was 4.10.3). Read from npm.
-
New version 4.10.3 (was 4.10.0). Read from npm.
-
New version 4.9.2 (was 4.9.0). Read from npm.
-
Tracking started: version 4.9.0.
FAQ
Can I paste mcp.tc/i/davinci-resolve into my MCP client?
No. DaVinci Resolve runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx davinci-resolve-mcp setup.
Does DaVinci Resolve need an API key?
No. It doesn’t declare any keys or environment variables. It runs with your user account’s permissions, so check what its tools can reach.
Is DaVinci Resolve a remote or a local server?
Local. Your client starts it as a process on your computer with npx davinci-resolve-mcp setup, which needs Node.js.
What can DaVinci Resolve do?
You can edit timelines and organize the media pool, set up and manage render jobs and add review markers.
Which clients can use it?
Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.
Does mcp.tc track changes to DaVinci Resolve?
Partly. It runs on your computer, so we follow its npm package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.
Who wrote this page?
mcp.tc’s robot read DaVinci Resolve’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
mcp.tc isn’t affiliated with Samuel Gursky. This page was built from DaVinci Resolve’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.