/ Annuaire / Playground / davinci-resolve-mcp
● Communauté samuelgursky ⚡ Instantané

davinci-resolve-mcp

par samuelgursky · samuelgursky/davinci-resolve-mcp

Drive DaVinci Resolve from chat — build timelines, adjust transforms, add keyframes, export renders — all 324 scripting APIs exposed.

davinci-resolve-mcp gives any MCP client full control of DaVinci Resolve Studio via Resolve's local scripting API. 27 compound tools cover projects, media pools, timelines, keyframes, color, Fusion comps, and rendering. Requires Resolve Studio (not free edition) because the free build lacks scripting.

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

davinci-resolve.replay ▶ prêt
0/0

Installer

Choisissez votre client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "davinci-resolve": {
      "command": "uvx",
      "args": [
        "davinci-resolve-mcp"
      ],
      "_inferred": true
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "davinci-resolve": {
      "command": "uvx",
      "args": [
        "davinci-resolve-mcp"
      ],
      "_inferred": true
    }
  }
}

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "davinci-resolve": {
      "command": "uvx",
      "args": [
        "davinci-resolve-mcp"
      ],
      "_inferred": true
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "davinci-resolve": {
      "command": "uvx",
      "args": [
        "davinci-resolve-mcp"
      ],
      "_inferred": true
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "davinci-resolve",
      "command": "uvx",
      "args": [
        "davinci-resolve-mcp"
      ]
    }
  ]
}

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json
{
  "context_servers": {
    "davinci-resolve": {
      "command": {
        "path": "uvx",
        "args": [
          "davinci-resolve-mcp"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

claude mcp add davinci-resolve -- uvx davinci-resolve-mcp

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : davinci-resolve-mcp

Build a rough cut from a script + footage folder

👤 Video editors doing talking-head content ⏱ ~20 min intermediate

Quand l'utiliser : You have 2 hours of B-roll and a 3-page script and don't want to start in a black timeline.

Prérequis
  • DaVinci Resolve Studio 18.5+ open — Purchase once ($295) — free edition has no scripting API
  • Resolve preferences: System > General > External scripting using: Local — Restart Resolve after flipping it
  • MCP installed via the universal installer — git clone samuelgursky/davinci-resolve-mcp && python install.py
Déroulement
  1. Create project and import media
    Create a new project 'EP04_RoughCut', 1080p24, and import every .mov in ~/Footage/EP04 into a Media Pool folder called 'B-roll'.✓ Copié
    → Project open with folder populated
  2. Build a timeline keyed to script beats
    Create a new timeline. For each paragraph in ~/Footage/EP04/script.md, add a 6-second marker on track V2 labeled with the first 5 words.✓ Copié
    → Timeline with beat markers
  3. Drop B-roll at each marker
    At each marker, pick the closest-matching B-roll clip by filename keyword and place it on V1 at that marker.✓ Copié
    → Cut assembles visibly

Résultat : A rough cut you can refine manually, built in 5 minutes instead of an hour.

Pièges
  • Filename-based matching is noisy — Rename clips with descriptive prefixes, or use Resolve's built-in Voice Isolation / transcription for smarter matching
  • Resolve is sluggish while MCP tools run on huge projects — Work in a smaller 'assembly' project; conform to the big project later
Combiner avec : filesystem

Batch-apply a color preset across an entire timeline

👤 Colorists doing assistant work ⏱ ~15 min intermediate

Quand l'utiliser : You want to stamp a base LUT + saturation bump across 60 clips before starting hand grading.

Déroulement
  1. Inspect timeline structure
    List every clip in the active timeline with in/out and source filename.✓ Copié
    → Clip inventory
  2. Apply preset
    For every clip, apply Power Grade 'EP04_Base' as the first node.✓ Copié
    → Thumbnails update
  3. Flag clips that look wrong
    Which clips look significantly outside the normal range after the preset? Suggest per-clip adjustments.✓ Copié
    → Short list of clips needing manual attention

Résultat : A consistent base grade applied in seconds, with manual-attention flags.

Export multiple deliverables from one timeline

👤 Editors delivering to YouTube + Instagram + broadcast ⏱ ~10 min beginner

Quand l'utiliser : Same cut, three export specs, don't want to click through the render page three times.

Déroulement
  1. Queue all three renders
    Queue renders for active timeline: YouTube 1080p H.264 to ~/Exports/yt.mp4, Instagram 1080x1350 to ig.mp4, ProRes 422 HQ to broadcast.mov.✓ Copié
    → 3 jobs in the render queue
  2. Start and monitor
    Start all queued jobs and report when done.✓ Copié
    → Completion status per job

Résultat : A multi-format delivery in one chat turn.

Combiner avec : filesystem

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

davinci-resolve + filesystem

Read a script/EDL from disk and cut against it

Read ~/Project/EP04/edl.txt and build a matching timeline in the current Resolve project.✓ Copié
davinci-resolve + after-effects

Finish VFX in AE then conform back into Resolve

After AE renders are done at ~/renders/vfx/, replace the corresponding placeholder clips in Resolve's timeline with the new files.✓ Copié

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
resolve action: str, params?: object App-level: pages, layout, render presets free (local)
project_manager action, params Create/open/delete projects, databases, cloud free
project action, params Timelines, render pipeline, settings, LUTs free
media_pool action, params Import, organize clips and timelines free
timeline action, params Tracks, markers, items, generators free
timeline_item action, params Per-clip properties, Fusion comps, versions, CDL free
timeline_item_transform item_id, pan?, tilt?, zoom?, rotation? Reposition/resize a clip free
timeline_item_keyframes item_id, property, frame, value Animate any keyframeable property free
gallery action, params Stills and Power Grades free
fusion_comp action, params Build/modify Fusion node graphs free

Coût et limites

Coût d'exécution

Quota d'API
No network — everything is local scripting API
Tokens par appel
Most responses 200-800 tokens; timeline dumps can hit 5k on big edits
Monétaire
DaVinci Resolve Studio one-time ~$295 (required). MCP itself is free/MIT.
Astuce
The cost is Resolve Studio and your render time; API calls are free. Ask for scoped lists (1 timeline, 1 track) not entire project dumps.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : No credentials — local scripting only
Sortie de données : None. All API calls stay within Resolve.
Ne jamais accorder : Remote network exposure of the MCP — keep it local

Dépannage

Erreurs courantes et correctifs

No connection to DaVinci Resolve

Resolve must be running and 'External scripting using: Local' enabled; restart Resolve after flipping.

Vérifier : Preferences > System > General shows Local
Free edition: scripting disabled

The free edition does not expose the scripting API. Upgrade to Studio.

Python version mismatch on macOS

Installer prefers Python 3.10-3.12. Use pyenv install 3.11.9 and re-run install.py.

Vérifier : python3 --version
Operations time out on a 4K project

Resolve's scripting API is single-threaded and queues behind UI updates. Minimize Resolve's viewer panels during large batch ops.

Alternatives

davinci-resolve-mcp vs autres

AlternativeQuand l'utiliserCompromis
Adobe Premiere MCPs (community)Your pipeline is Premiere, not ResolveLess mature MCP ecosystem for Premiere
After Effects MCPYou're doing motion graphics, not edit/colorDifferent stage of the pipeline
Raw Python + Resolve APIYou want total control and don't need AINo MCP = no chat interface

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills