davinci-resolve-mcp MCP — Anwendungsfälle, Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

27 tools covering 324 of 324 Resolve API methods (100%)
Universal installer auto-configures Claude Desktop/Code, Cursor, VS Code, Windsurf, Zed, JetBrains
Timeline manipulation: tracks, markers, clips, generators, titles
Per-clip transform, crop, composite, retime, keyframes
Fusion node-graph API for motion-graphics automation

Live-Demo

In der Praxis

davinci-resolve.replay ▶ bereit

0/0

Installieren

Wählen Sie Ihren 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
    }
  }
}

Öffne Claude Desktop → Settings → Developer → Edit Config. Nach dem Speichern neu starten.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "davinci-resolve": {
      "command": "uvx",
      "args": [
        "davinci-resolve-mcp"
      ],
      "_inferred": true
    }
  }
}

Cursor nutzt das gleiche mcpServers-Schema wie Claude Desktop. Projektkonfiguration schlägt die globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "davinci-resolve": {
      "command": "uvx",
      "args": [
        "davinci-resolve-mcp"
      ],
      "_inferred": true
    }
  }
}

Klicken Sie auf das MCP-Servers-Symbol in der Cline-Seitenleiste, dann "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "davinci-resolve": {
      "command": "uvx",
      "args": [
        "davinci-resolve-mcp"
      ],
      "_inferred": true
    }
  }
}

Gleiche Struktur wie Claude Desktop. Windsurf neu starten zum Übernehmen.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "davinci-resolve",
      "command": "uvx",
      "args": [
        "davinci-resolve-mcp"
      ]
    }
  ]
}

Continue nutzt ein Array von Serverobjekten statt einer Map.

~/.config/zed/settings.json

{
  "context_servers": {
    "davinci-resolve": {
      "command": {
        "path": "uvx",
        "args": [
          "davinci-resolve-mcp"
        ]
      }
    }
  }
}

In context_servers hinzufügen. Zed lädt beim Speichern neu.

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

Einzeiler. Prüfen mit claude mcp list. Entfernen mit claude mcp remove.

Anwendungsfälle

Praxisnahe Nutzung: davinci-resolve-mcp

Build a rough cut from a script + footage folder

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

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

Voraussetzungen

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

Ablauf

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'.✓ Kopiert

→ Project open with folder populated
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.✓ Kopiert

→ Timeline with beat markers
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.✓ Kopiert

→ Cut assembles visibly

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

Fallstricke

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

Kombinieren mit: filesystem

Batch-apply a color preset across an entire timeline

👤 Colorists doing assistant work ⏱ ~15 min intermediate

Wann einsetzen: You want to stamp a base LUT + saturation bump across 60 clips before starting hand grading.

Ablauf

Inspect timeline structure

List every clip in the active timeline with in/out and source filename.✓ Kopiert

→ Clip inventory
Apply preset

For every clip, apply Power Grade 'EP04_Base' as the first node.✓ Kopiert

→ Thumbnails update
Flag clips that look wrong

Which clips look significantly outside the normal range after the preset? Suggest per-clip adjustments.✓ Kopiert

→ Short list of clips needing manual attention

Ergebnis: 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

Wann einsetzen: Same cut, three export specs, don't want to click through the render page three times.

Ablauf

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.✓ Kopiert

→ 3 jobs in the render queue
Start and monitor

Start all queued jobs and report when done.✓ Kopiert

→ Completion status per job

Ergebnis: A multi-format delivery in one chat turn.

Kombinieren mit: filesystem

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

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.✓ Kopiert

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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
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

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: No network — everything is local scripting API
Tokens pro Aufruf: Most responses 200-800 tokens; timeline dumps can hit 5k on big edits
Kosten in €: DaVinci Resolve Studio one-time ~$295 (required). MCP itself is free/MIT.
Tipp: 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.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No credentials — local scripting only

Datenabfluss: None. All API calls stay within Resolve.

Niemals gewähren: Remote network exposure of the MCP — keep it local

Enable 'External scripting using: Local' — never 'Network' unless you own the network end-to-end.
The MCP has full project control; don't run experiments on the project you're delivering today.

Fehlerbehebung

Häufige Fehler und Lösungen

No connection to DaVinci Resolve

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

Prüfen: 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.

Prüfen: 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.

Alternativen

davinci-resolve-mcp vs. andere

Alternative	Wann stattdessen	Kompromiss
Adobe Premiere MCPs (community)	Your pipeline is Premiere, not Resolve	Less mature MCP ecosystem for Premiere
After Effects MCP	You're doing motion graphics, not edit/color	Different stage of the pipeline
Raw Python + Resolve API	You want total control and don't need AI	No MCP = no chat interface

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen