Skip to content
Back to search

resolve-claude-mcp

Connect DaVinci Resolve Studio to Claude AI through the Model Context Protocol (MCP)

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/barckley75--resolve-claude-mcp/badge.svg)](/listings/barckley75--resolve-claude-mcp)

HTML

<a href="/listings/barckley75--resolve-claude-mcp"><img src="/api/listings/barckley75--resolve-claude-mcp/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Step 1: Clone this repo

git clone https://github.com/barckley75/resolve-claude-mcp.git
cd resolve-claude-mcp
uv sync

Note the **absolute path** to the folder you just cloned — you'll need it in Step 2.

Step 2: Tell Claude Desktop about this server

Claude Desktop has a settings file called **`claude_desktop_config.json`** that lists every MCP server it should launch on startup. You need to add an entry to that file so Claude Desktop knows about Resolve Claude MCP.

The file lives in your **user folder** (not inside the Claude app):

- **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json` - **Windows:** `%APPDATA%\Claude\claude_desktop_config.json`

Open it (or create it if it doesn't exist — these commands will create a blank file you can fill in):

# macOS — opens in TextEdit
open -e "$HOME/Library/Application Support/Claude/claude_desktop_config.json"

# Windows (PowerShell) — opens in Notepad
notepad "$env:APPDATA\Claude\claude_desktop_config.json"

When the editor opens, paste in the JSON below. Replace `/absolute/path/to/resolve-claude-mcp` with the path to the folder you cloned in Step 1. If the file already has other MCP servers in it, just add the `"resolve"` block inside the existing `"mcpServers"` object — don't create a second `"mcpServers"`.

{
  "mcpServers": {
    "resolve": {
      "command": "uv",
      "args": [
        "--directory",
        "/absolute/path/to/resolve-claude-mcp",
        "run",
        "resolve-claude-mcp"
      ],
      "env": {
        "RESOLVE_SCRIPT_LIB": "/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Libraries/Fusion/fusionscript.so",
        "RESOLVE_SCRIPT_API": "/Library/Application Support/Blackmagic Design/DaVinci Resolve/Developer/Scripting",
        "PYTHONPATH": "/Library/Application Support/Blackmagic Design/DaVinci Resolve/Developer/Scripting/Modules/"
      }
    }
  }
}

> If `uv` isn't on Claude Desktop's `PATH`, use the full path — find it with `which uv` (macOS/Linux) or `where.exe uv` (Windows). On macOS via Homebrew it's typically `/opt/homebrew/bin/uv`.

<details> <summary>Windows environment variables</summary>

{
  "mcpServers": {
    "resolve": {
      "command": "uv",
      "args": [
        "--directory",
        "C:\\absolute\\path\\to\\resolve-claude-mcp",
        "run",
        "resolve-claude-mcp"
      ],
      "env": {
        "RESOLVE_SCRIPT_LIB": "C:\\Program Files\\Blackmagic Design\\DaVinci Resolve\\fusionscript.dll",
        "RESOLVE_SCRIPT_API": "C:\\ProgramData\\Blackmagic Design\\DaVinci Resolve\\Support\\Developer\\Scripting",
        "PYTHONPATH": "C:\\ProgramData\\Blackmagic Design\\DaVinci Resolve\\Support\\Developer\\Scripting\\Modules\\"
      }
    }
  }
}

If you installed Resolve on a non-default drive (e.g. `D:\`), update `RESOLVE_SCRIPT_LIB` to point at the actual location of `fusionscript.dll`. The `RESOLVE_SCRIPT_API` / `PYTHONPATH` paths stay under `C:\ProgramData\` regardless of where Resolve itself was installed.

</details>

<details> <summary>Linux environment variables</summary>

{
  "mcpServers": {
    "resolve": {
      "command": "uv",
      "args": [
        "--directory",
        "/absolute/path/to/resolve-claude-mcp",
        "run",
        "resolve-claude-mcp"
      ],
      "env": {
        "RESOLVE_SCRIPT_LIB": "/opt/resolve/libs/Fusion/fusionscript.so",
        "RESOLVE_SCRIPT_API": "/opt/resolve/Developer/Scripting",
        "PYTHONPATH": "/opt/resolve/Developer/Scripting/Modules/"
      }
    }
  }
}

</details>

Step 3: Enable Scripting in Resolve

1. Open DaVinci Resolve Studio 2. Go to **Preferences > General** 3. Under **External scripting using**, select **Local** (or **Network** if running remotely)

Step 4: Restart Claude Desktop

Quit and reopen the Claude Desktop app. You should see the Resolve Claude MCP tools available (hammer icon).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 347 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # Resolve Claude MCP
  2. Connect **DaVinci Resolve Studio** to **Claude AI** through the [Model Context Protocol (MCP)](https://modelcontextprotocol.io), enabling AI-assisted video editing, color grading, Fusion compositing, and more — all through natural language.
  3. > **Note:** This is a third-party integration and is not created by or affiliated with Blackmagic Design.
  4. >
  5. > ⚠️ **Use at your own risk.** This project is intended for testing and experimentation. **Do not use in production.** AI-assisted tools can modify or delete your project data — always work on backups.
  6. > **Platform support:** Tested only on **macOS** (Apple Silicon). The Blackmagic scripting API is cross-platform, so the core 48 Resolve-control tools may work on Windows and Linux as well, but this is unverified. The local transcription tools and the `screenshot` tool are **macOS-only** (they rely on `mlx-whisper` and macOS-specific screen-capture APIs).
  7. ## Demo
  8. <p align="center">
  9. <img src="assets/screenshot-color-page.png" alt="Claude controlling DaVinci Resolve Color page" width="800">
  10. </p>
  11. ### Color Grading with Claude
  12. ![Color grading demo](assets/demo-color-grading.gif)
  13. ### Local Transcription & Subtitles
  14. ![Transcription demo](assets/demo-transcription.gif)
  15. ## Features
  16. ### Core
  17. - Direct connection to DaVinci Resolve Studio's scripting API — no addon or plugin needed inside Resolve
  18. - Project inspection and navigation across all pages (Media, Cut, Edit, Fusion, Color, Fairlight, Deliver)
  19. - Media pool management (import, organize, browse)
  20. - Timeline creation and editing
  21. - Arbitrary Python code execution with the full Resolve API
  22. ### Color Grading
  23. - Node graph inspection and manipulation
  24. - LUT application
  25. - CDL (Color Decision List) adjustments
  26. ### Fusion (Compositing / VFX)
  27. - Create, import, export, and manage Fusion compositions
  28. - Insert Fusion generators, titles, and blank compositions
  29. - Merge timeline items into Fusion clips
  30. ### AI / DaVinci Neural Engine
  31. - **Magic Mask** — AI-powered subject isolation
  32. - **Smart Reframe** — automatic reframing for different aspect ratios
  33. - **Stabilization** — AI-powered clip stabilization
  34. - **Scene Cut Detection** — auto-detect and cut at scene boundaries
  35. - **Subtitle Generation** — AI speech-to-text with multi-language support
  36. - **Voice Isolation** — separate speech from background noise
  37. ### Local Transcription (macOS / Apple Silicon only)
  38. - **mlx-whisper** transcription running locally on your Mac's Neural Engine / GPU
  39. - Auto-chunks long files with ffmpeg (5-min pieces) — no timeouts on hour-long clips
  40. - Returns compact timestamped transcript inline for immediate use
  41. - Saves SRT file next to source for Resolve subtitle import
  42. - Multiple model sizes: tiny (fastest) to large (most accurate), default: turbo
  43. - **Windows/Linux users:** these tools are unavailable (MLX is Apple-only). The other 48 tools work fine.
  44. ### Screenshot (macOS only)
  45. - `screenshot` — captures the Resolve window so Claude can visually inspect what's on screen
  46. - Uses macOS `screencapture` + Quartz to target the Resolve window directly
  47. - Needs Screen Recording permission for Claude Desktop in System Settings
  48. - **Windows/Linux users:** this tool is unavailable
  49. ### Rendering
  50. - Browse available formats and codecs
  51. - Configure render settings
  52. - Queue and start render jobs
  53. - Monitor render progress
  54. ### Code Execution
  55. - `execute_resolve_code` — run any Python code with the Resolve API available (`resolve`, `project`, `mediaPool`, `timeline`, `mediaStorage` pre-loaded)
  56. - This is the power tool: anything the Resolve Python API can do, Claude can do
  57. ## Architecture
  58. Unlike BlenderMCP which requires a socket-based addon, Resolve Claude MCP connects directly to DaVinci Resolve via its native scripting API. This means a simpler, single-process architecture:
  59. ```
  60. Claude AI (MCP Client)
  61. |
  62. v
  63. Resolve Claude MCP Server (FastMCP)
  64. |
  65. v
  66. DaVinciResolveScript (fusionscript.so)
  67. |
  68. v
  69. DaVinci Resolve Studio (running)
  70. ```
  71. No addon to install inside Resolve. No socket server. Just one MCP server that talks directly to Resolve.
  72. ## Prerequisites
  73. - **DaVinci Resolve Studio** 18.0+ (free version has limited scripting support)
  74. - **Python** 3.10+
  75. - **uv** package manager
  76. Install uv:
  77. ```bash
  78. # macOS
  79. brew install uv
  80. # Windows
  81. powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
  82. # Linux
  83. curl -LsSf https://astral.sh/uv/install.sh | sh
  84. ```
  85. ## Installation
  86. ### Step 1: Clone this repo
  87. ```bash
  88. git clone https://github.com/barckley75/resolve-claude-mcp.git
  89. cd resolve-claude-mcp
  90. uv sync
  91. ```
  92. Note the **absolute path** to the folder you just cloned — you'll need it in Step 2.
  93. ### Step 2: Tell Claude Desktop about this server
  94. Claude Desktop has a settings file called **`claude_desktop_config.json`** that lists every MCP server it should launch on startup. You need to add an entry to that file so Claude Desktop knows about Resolve Claude MCP.
  95. The file lives in your **user folder** (not inside the Claude app):
  96. - **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`
  97. - **Windows:** `%APPDATA%\Claude\claude_desktop_config.json`
  98. Open it (or create it if it doesn't exist — these commands will create a blank file you can fill in):
  99. ```bash
  100. # macOS — opens in TextEdit
  101. open -e "$HOME/Library/Application Support/Claude/claude_desktop_config.json"
  102. # Windows (PowerShell) — opens in Notepad
  103. notepad "$env:APPDATA\Claude\claude_desktop_config.json"
  104. ```
  105. When the editor opens, paste in the JSON below. Replace `/absolute/path/to/resolve-claude-mcp` with the path to the folder you cloned in Step 1. If the file already has other MCP servers in it, just add the `"resolve"` block inside the existing `"mcpServers"` object — don't create a second `"mcpServers"`.
  106. ```json
  107. {
  108. "mcpServers": {
  109. "resolve": {
  110. "command": "uv",
  111. "args": [
  112. "--directory",
  113. "/absolute/path/to/resolve-claude-mcp",
  114. "run",
  115. "resolve-claude-mcp"
  116. ],
  117. "env": {
  118. "RESOLVE_SCRIPT_LIB": "/Applications/DaVinci Resolve/DaVinci Resolve.app/Contents/Libraries/Fusion/fusionscript.so",
  119. "RESOLVE_SCRIPT_API": "/Library/Application Support/Blackmagic Design/DaVinci Resolve/Developer/Scripting",
  120. "PYTHONPATH": "/Library/Application Support/Blackmagic Design/DaVinci Resolve/Developer/Scripting/Modules/"
  121. }
  122. }
  123. }
  124. }
  125. ```
  126. > If `uv` isn't on Claude Desktop's `PATH`, use the full path — find it with `which uv` (macOS/Linux) or `where.exe uv` (Windows). On macOS via Homebrew it's typically `/opt/homebrew/bin/uv`.
  127. <details>
  128. <summary>Windows environment variables</summary>
  129. ```json
  130. {
  131. "mcpServers": {
  132. "resolve": {
  133. "command": "uv",
  134. "args": [
  135. "--directory",
  136. "C:\\absolute\\path\\to\\resolve-claude-mcp",
  137. "run",
  138. "resolve-claude-mcp"
  139. ],
  140. "env": {
  141. "RESOLVE_SCRIPT_LIB": "C:\\Program Files\\Blackmagic Design\\DaVinci Resolve\\fusionscript.dll",
  142. "RESOLVE_SCRIPT_API": "C:\\ProgramData\\Blackmagic Design\\DaVinci Resolve\\Support\\Developer\\Scripting",
  143. "PYTHONPATH": "C:\\ProgramData\\Blackmagic Design\\DaVinci Resolve\\Support\\Developer\\Scripting\\Modules\\"
  144. }
  145. }
  146. }
  147. }
  148. ```
  149. If you installed Resolve on a non-default drive (e.g. `D:\`), update `RESOLVE_SCRIPT_LIB` to point at the actual location of `fusionscript.dll`. The `RESOLVE_SCRIPT_API` / `PYTHONPATH` paths stay under `C:\ProgramData\` regardless of where Resolve itself was installed.
  150. </details>
  151. <details>
  152. <summary>Linux environment variables</summary>
  153. ```json
  154. {
  155. "mcpServers": {
  156. "resolve": {
  157. "command": "uv",
  158. "args": [
  159. "--directory",
  160. "/absolute/path/to/resolve-claude-mcp",
  161. "run",
  162. "resolve-claude-mcp"
  163. ],
  164. "env": {
  165. "RESOLVE_SCRIPT_LIB": "/opt/resolve/libs/Fusion/fusionscript.so",
  166. "RESOLVE_SCRIPT_API": "/opt/resolve/Developer/Scripting",
  167. "PYTHONPATH": "/opt/resolve/Developer/Scripting/Modules/"
  168. }
  169. }
  170. }
  171. }
  172. ```
  173. </details>
  174. ### Step 3: Enable Scripting in Resolve
  175. 1. Open DaVinci Resolve Studio
  176. 2. Go to **Preferences > General**
  177. 3. Under **External scripting using**, select **Local** (or **Network** if running remotely)
  178. ### Step 4: Restart Claude Desktop
  179. Quit and reopen the Claude Desktop app. You should see the Resolve Claude MCP tools available (hammer icon).
  180. ## Usage
  181. Make sure DaVinci Resolve Studio is running with a project open, then talk to Claude:
  182. ### Project & Navigation
  183. > "What project do I have open?"
  184. > "Switch to the Color page"
  185. > "How many timelines are in this project?"
  186. ### Media & Timeline
  187. > "Import all the .mp4 files from ~/Videos/project/ into the media pool"
  188. > "Create a new timeline called 'Rough Cut'"
  189. > "What clips are on video track 1?"
  190. > "Add a red marker at frame 200 called 'Fix audio here'"
  191. ### Color Grading
  192. > "Show me the node graph for the first clip"
  193. > "Apply this LUT to node 1: /path/to/my.cube"
  194. > "Set CDL values: increase slope to 1.2 and reduce saturation to 0.8"
  195. ### AI Features
  196. > "Run scene cut detection on the timeline"
  197. > "Apply Smart Reframe to the first clip"
  198. > "Create a Magic Mask on clip 3 to isolate the subject"
  199. > "Generate subtitles from the audio in English"
  200. > "Enable Voice Isolation on audio track 1"
  201. > "Stabilize the second clip on video track 1"
  202. ### Transcription
  203. > "Transcribe ~/Videos/interview.mp4"
  204. > "Transcribe this clip in French using the large model"
  205. > "Export an SRT file from ~/Videos/podcast.wav to ~/Desktop/podcast.srt"
  206. > "Transcribe the audio and add subtitle markers to the timeline"
  207. ### Fusion
  208. > "List all Fusion compositions on the first clip"
  209. > "Add a Fusion composition to clip 2"
  210. > "Insert a Fusion title into the timeline"
  211. ### Rendering
  212. > "What render formats are available?"
  213. > "Set up a render to ProRes 422 HQ, output to ~/Desktop/exports"
  214. > "Add a render job and start rendering"
  215. > "What's the render progress?"
  216. ### Power Tool
  217. > "Run this code: print(project.GetSetting('timelineFrameRate'))"
  218. ## Available Tools (52)
  219. | Category | Tools |
  220. |---|---|
  221. | **Project & Navigation** | `get_project_info`, `open_page`, `get_current_page` |
  222. | **Media Pool** | `get_media_pool_structure`, `import_media`, `create_timeline` |
  223. | **Timeline** | `get_current_timeline_info`, `get_timeline_items`, `append_to_timeline`, `add_marker`, `get_markers`, `set_current_timecode`, `get_current_timecode` |
  224. | **Item Properties** | `get_timeline_item_properties`, `set_timeline_item_property` |
  225. | **Color Grading** | `get_node_graph`, `set_lut`, `set_cdl` |
  226. | **Rendering** | `get_render_formats`, `get_render_settings`, `set_render_settings`, `add_render_job`, `start_rendering`, `get_render_status`, `stop_rendering` |
  227. | **AI / Neural Engine** | `create_magic_mask`, `regenerate_magic_mask`, `smart_reframe`, `stabilize`, `detect_scene_cuts`, `create_subtitles_from_audio` |
  228. | **Audio** | `get_voice_isolation_state`, `set_voice_isolation_state` |
  229. | **Fusion** | `get_fusion_comp_list`, `add_fusion_comp`, `import_fusion_comp`, `export_fusion_comp`, `load_fusion_comp`, `delete_fusion_comp`, `rename_fusion_comp`, `create_fusion_clip`, `insert_fusion_generator`, `insert_fusion_composition`, `insert_fusion_title` |
  230. | **Export** | `export_timeline`, `export_current_frame` |
  231. | **Thumbnail** | `get_current_thumbnail` |
  232. | **Local Transcription** _(macOS only)_ | `transcribe_audio`, `transcribe_and_add_subtitles`, `export_srt`, `list_whisper_models` |
  233. | **Screenshot** _(macOS only)_ | `screenshot` |
  234. | **Code Execution** | `execute_resolve_code` |
  235. ## Troubleshooting
  236. ### "Could not connect to DaVinci Resolve"
  237. - Make sure DaVinci Resolve Studio is running
  238. - Check that scripting is enabled in **Preferences > General > External scripting using**
  239. - Verify the `RESOLVE_SCRIPT_LIB` path matches your installation
  240. ### "Failed to import DaVinciResolveScript"
  241. - Check that `PYTHONPATH` in the config points to the correct Modules directory
  242. - On macOS, the default path is `/Library/Application Support/Blackmagic Design/DaVinci Resolve/Developer/Scripting/Modules/`
  243. ### "No active timeline"
  244. - Open a project and make sure a timeline is loaded before using timeline tools
  245. ### Tools not appearing in Claude Desktop
  246. - Make sure `uv` is installed: `uv --version`
  247. - Restart Claude Desktop after editing `claude_desktop_config.json`
  248. - Check the Claude Desktop logs for MCP server errors
  249. ## Important Notes
  250. - **DaVinci Resolve Studio** is required for full scripting API access. The free version has limited scripting support.
  251. - `execute_resolve_code` runs arbitrary Python — review code before executing.
  252. - Some tools require being on a specific page (e.g., thumbnails require the Color page).
  253. - The server connects to whichever project is currently open — switching projects in Resolve is reflected immediately.
  254. ## Disclaimer
  255. **USE AT YOUR OWN RISK.** This software is provided "as is", without warranty of any kind, express or implied. By using Resolve Claude MCP you acknowledge and accept that:
  256. - This is an **unofficial, third-party project** — not created by, affiliated with, endorsed by, or supported by Blackmagic Design or Anthropic.
  257. - It is designed to control DaVinci Resolve Studio through an AI assistant. AI agents can make mistakes: they may **modify, overwrite, or delete** your projects, timelines, clips, render queues, or files on disk.
  258. - The `execute_resolve_code` tool executes **arbitrary Python code** with full access to the Resolve API and your filesystem. Inspect code before allowing execution.
  259. - The `screenshot` tool captures the DaVinci Resolve window (or the full screen as a fallback). **These images are sent to the AI provider** (Anthropic) for analysis. Anything visible in the screenshot — client footage, unreleased material, personal content, notifications, passwords, other apps in the background — may be transmitted. Only use it when you're comfortable with what's on screen, and be aware of your NDAs and privacy obligations.
  260. - **Always work on a backup of your project.** Save often. Use Resolve's built-in project backups (Project Manager → right-click → Backups). Keep media outside the project folder if it matters to you.
  261. - The authors and contributors accept **no liability** for lost work, corrupted projects, missed deadlines, wasted render time, accidental uploads/exports, API charges, or any other damages arising from use of this software.
  262. - You are responsible for reviewing what the AI is about to do before approving tool calls in your MCP client.
  263. If this is production work on a client project, don't let the AI drive unsupervised. Watch the tool calls, keep backups, render proofs.
  264. ## License
  265. MIT — see [LICENSE](LICENSE). The MIT license specifically disclaims all warranties and liability; the Disclaimer section above restates that in plain English.
  266. ## Acknowledgments
  267. Inspired by [BlenderMCP](https://github.com/ahujasid/blender-mcp) by Siddharth Ahuja.
  268. Built with the [Model Context Protocol](https://modelcontextprotocol.io) by Anthropic.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.