Davinc-Resolve-Local-Bridge-MCP

# Davinc-Resolve-Local-Bridge-MCP

<!-- mcp-name: io.github.Airta-Admin/davinc-resolve-local-bridge-mcp -->

<p align="center">
  <img src="images/software-box.png" alt="DaVinci Resolve Local Bridge MCP" width="400">
</p>

<p align="center">
  <strong>Control DaVinci Resolve from any AI assistant — Claude, Cursor, Devin, and more.</strong>
</p>

<p align="center">
  <strong>215 tools. Full API coverage. Works with DaVinci Resolve Free and Studio.</strong>
</p>

---

## What Is This?

**Davinc-Resolve-Local-Bridge-MCP** is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io) server that gives AI assistants full control over DaVinci Resolve. It exposes **215 tools** covering the entire Resolve scripting API — projects, timelines, media, Fusion, color grading, rendering, and more.

### How It Works

```
Your AI Assistant (Claude, Cursor, Devin, etc.)
       │
       │  talks MCP (stdio)
       ▼
  mcp_server/server.py        ← runs on your machine
       │
       │  talks HTTP (localhost:8787)
       ▼
  Bridge-Connection-Script.py ← runs INSIDE DaVinci Resolve
       │                        (Workspace > Scripts menu)
       ▼
  DaVinci Resolve API         ← full read + write access
```

The bridge script runs **inside** DaVinci Resolve's process, giving it full access to the Resolve scripting API — even on the **Free edition** (which blocks external scripting). The MCP server runs as a separate process and proxies tool calls to the bridge over localhost HTTP.

---

## Quick Start

### Prerequisites

- **DaVinci Resolve 18.5+** (Free or Studio)
- **Python 3.10+** on your machine
- An MCP-compatible AI assistant (Claude Desktop, Cursor, Devin, etc.)

### Step 1 — Install the Bridge Script

Run the installer:

```bash
python install.py
```

Or manually copy `bridge/Bridge-Connection-Script.py` to Resolve's scripts folder:

| Platform | Path |
|----------|------|
| **Windows** | `%APPDATA%\Roaming\Blackmagic Design\DaVinci Resolve\Support\Fusion\Scripts\Utility\` |
| **macOS** | `~/Library/Application Support/Blackmagic Design/DaVinci Resolve/Fusion/Scripts/Utility/` |
| **Linux** | `~/.local/share/DaVinciResolve/Fusion/Scripts/Utility/` |

### Step 2 — Install MCP Server Dependencies

```bash
pip install -r requirements.txt
```

### Step 3 — Configure Your AI Assistant

Add the MCP server to your assistant's configuration file. The server path is `mcp_server/server.py` in this repo.

#### Claude Desktop

Edit `claude_desktop_config.json`:

```json
{
  "mcpServers": {
    "davinci-resolve-local-bridge": {
      "command": "python",
      "args": ["C:/path/to/Davinc-Resolve-Local-Bridge-MCP/mcp_server/server.py"]
    }
  }
}
```

#### Cursor

Edit `.cursor/mcp.json`:

```json
{
  "mcpServers": {
    "davinci-resolve-local-bridge": {
      "command": "python",
      "args": ["C:/path/to/Davinc-Resolve-Local-Bridge-MCP/mcp_server/server.py"]
    }
  }
}
```

#### Devin

Edit `mcp_config.json`:

```json
{
  "mcpServers": {
    "resolve-local-bridge": {
      "command": "python",
      "args": ["C:/path/to/Davinc-Resolve-Local-Bridge-MCP/mcp_server/server.py"]
    }
  }
}
```

#### Claude Code

```bash
claude mcp add davinci-resolve-local-bridge -- python C:/path/to/Davinc-Resolve-Local-Bridge-MCP/mcp_server/server.py
```

#### Any MCP Client (generic)

The server uses **stdio transport**. Launch it with:

```bash
python mcp_server/server.py
```

### Step 4 — Start the Bridge Inside DaVinci Resolve

1. **Open DaVinci Resolve**
2. Go to **Workspace → Scripts → Bridge-Connection-Script**
3. Look in the **Console** (Workspace → Console) for:

```
[Resolve Bridge] Connected to Resolve 21.0.4.5
[Resolve Bridge] HTTP server running on http://127.0.0.1:8787
[Resolve Bridge] 215 actions available
```

### Step 5 — Start Using It

Ask your AI assistant:

> "Check if DaVinci Resolve is connected"

The assistant will call the `resolve_status` tool and report back. Then try:

> "Create a new 1920x1080 30fps project called 'My Video' and add a timeline"

---

## Architecture

### Bridge Script (`bridge/Bridge-Connection-Script.py`)

A Python script that runs **inside** DaVinci Resolve via the Workspace > Scripts menu. It:

- Obtains the live `resolve` object from Fusion's globals
- Starts an HTTP server on `127.0.0.1:8787`
- Exposes 3 endpoints:
  - `GET /health` — check if the bridge is alive
  - `GET /actions` — list all available action names
  - `POST /action` — execute an action by name with parameters
- Stays alive with a blocking `serve_forever()` call
- Kills any previous instance on the same port before starting

### MCP Server (`mcp_server/server.py`)

A standalone MCP server that:

- Connects to the bridge over HTTP on localhost
- Auto-discovers all 215 actions from the bridge's `/actions` endpoint
- Exposes each action as an MCP tool with the `resolve_` prefix
- Proxies tool calls to the bridge via `POST /action`
- Stays in sync with the bridge — no manual tool definitions needed

---

## All 215 Tools

The MCP server auto-discovers tools from the bridge. Each tool is prefixed with `resolve_` (e.g., `status` becomes `resolve_status`). Pass parameters as a `params` object.

### Resolve Application (15 tools)

| Tool | Parameters | Description |
|------|-----------|-------------|
| `resolve_status` | — | Check bridge connectivity and get current project/timeline info |
| `resolve_get_version` | — | Get Resolve version info |
| `resolve_get_current_page` | — | Get the active page (edit, cut, color, etc.) |
| `resolve_open_page` | `page` | Switch to a page: edit, cut, fusion, color, fairlight, deliver, media |
| `resolve_get_layout_presets` | — | List available layout presets |
| `resolve_load_layout_preset` | `presetName` | Load a layout preset by name |
| `resolve_get_keyframe_mode` | — | Get current keyframe mode |
| `resolve_set_keyframe_mode` | `keyframeMode` | Set keyframe mode |
| `resolve_get_fairlight_presets` | — | List Fairlight audio presets |
| `resolve_get_burnin_presets` | — | List burn-in presets |
| `resolve_import_render_preset` | `presetPath` | Import a render preset from file |
| `resolve_export_render_preset` | `presetName`, `exportPath` | Export a render preset to file |
| `resolve_open_fusion_page` | — | Switch to Fusion page |
| `resolve_open_edit_page` | — | Switch to Edit page |
| `resolve_open_deliver_page` | — | Switch to Deliver page |

### Project Manager (18 tools)

| Tool | Parameters | Description |
|------|-----------|-------------|
| `resolve_create_project` | `name`, `width`, `height`, `fps` | Create a new project |
| `resolve_load_project` | `name` | Load an existing project |
| `resolve_save_project` | — | Save the current project |
| `resolve_close_project` | — | Close the current project |
| `resolve_delete_project` | `name` | Delete a project |
| `resolve_create_folder` | `folderName` | Create a project folder |
| `resolve_delete_folder` | `folderName` | Delete a project folder |
| `resolve_get_project_list` | — | List projects in current folder |
| `resolve_get_folder_list` | — | List subfolders in current folder |
| `resolve_get_current_folder` | — | Get current folder name |
| `resolve_open_folder` | `folderName` | Open a folder |
| `resolve_goto_root_folder` | — | Navigate to root folder |
| `resolve_goto_parent_folder` | — | Navigate to parent folder |
| `resolve_import_project` | `filePath`, `projectName` | Import a .drp project |
| `resolve_export_project` | `projectName`, `filePath`, `withStillsAndLUTs` | Export a project as .drp |
| `resolve_archive_project` | `projectName`, `filePath`, ... | Archive a project |
| `resolve_get_current_database` | — | Get current database name |
| `resolve_get_database_list` | — | List available databases |

### Project Settings (7 tools)

| Tool | Parameters | Description |
|------|-----------|-------------|
| `resolve_get_project_name` | — | Get current project name |
| `resolve_set_project_name` | `name` | Rename the current project |
| `resolve_get_project_setting` | `key` | Get a project setting by key |
| `resolve_set_project_setting` | `key`, `value` | Set a project setting |
| `resolve_get_project_settings` | — | Get all project settings |
| `resolve_get_project_preset_list` | — | List project presets |
| `resolve_set_project_preset` | `presetName` | Apply a project preset |

### Media Storage (4 tools)

| Tool | Parameters | Description |
|------|-----------|-------------|
| `resolve_get_mounted_volumes` | — | List mounted storage volumes |
| `resolve_get_subfolder_list` | `folderPath` | List subfolders in a path |
| `resolve_get_file_list` | `folderPath` | List files in a folder |
| `resolve_reveal_in_storage` | `path` | Reveal a file in the OS file browser |

### Media Pool (13 tools)

| Tool | Parameters | Description |
|------|-----------|-------------|
| `resolve_import_media` | `paths` (list) | Import media files into the pool |
| `resolve_get_media_pool` | — | List all clips in root folder |
| `resolve_get_root_folder` | — | Get root folder info |
| `resolve_add_sub_folder` | `folderName`, `parentFolderName` | Create a subfolder |
| `resolve_set_current_folder` | `folderName` | Set the current folder |
| `resolve_delete_clips` | `clipNames` (list) | Delete clips from pool |
| `resolve_move_clips` | `clipNames`, `targetFolder` | Move clips to a folder |
| `resolve_relink_clips` | `clipNames`, `folderPath` | Relink clips |
| `resolve_unlink_clips` | `clipNames` | Unlink clips |
| `resolve_export_metadata` | `fileName`, `clipNames` | Export metadata CSV |
| `resolve_get_selected_clips` | — | List selected clips |
| `resolve_set_selected_clip` | `clipName` | Select a clip |
| `resolve_add_timeline_mattes` | `paths` (list) | Add matte files |

### Timeline (21 tools)

| Tool | Parameters | Description |
|------|-----------|-------------|
| `resolve_create_timeline` | `name` | Create a new empty timeline |
| `resolve_create_timeline_from_clips` | `name`, `clipNames` | Create timeline from clips |
| `resolve_list_timelin