MCP server for controlling DaVinci Resolve Studio through the official scripting API, with tools for projects, timelines, media pools, render setup, review markers, grading, Fusion, Fairlight, and source-safe media analysis.
DaVinci Resolve MCP Server can launch or reconnect to Resolve, switch pages, create or open projects, modify timelines, manage media pools, write markers, change render settings, and queue jobs., Extension-authoring tools can install or remove Resolve scripts, Fuses, DCTLs, ACES DCTLs, presets, and page scripts., Source media is intended to remain immutable by default, but operators must still review requests that relink, replace, transcode, proxy, render, export, or create media derivatives., The default server is local stdio, but the local control panel starts a single-user browser server; keep it on trusted local interfaces only., Require confirmation before deleting projects, replacing clips, changing project settings, installing extensions, updating metadata, or queuing renders., Keep Resolve external scripting set to `Local` unless you have a separate remote-control security plan.
Privacy notes
Project names, timelines, clip names, media paths, markers, metadata, render paths, transcripts, thumbnails, analysis artifacts, logs, and Resolve scripting paths can be exposed to the MCP client., Media analysis can produce sidecar files, scratch artifacts, frame paths, transcripts, searchable indexes, and reports that may include private footage details., Host-chat visual analysis can expose selected frame images to the active MCP client or vision-capable model provider., Local logs and analysis reports may contain absolute media paths, project names, clip metadata, speaker text, visual descriptions, and render settings., Store generated analysis artifacts and exports inside approved project or scratch directories and delete them when no longer needed.
Author
Samuel Gursky
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
6 safety and 5 privacy notes across 6 risk areas. Review closely: network access, third-party handling.
6 areas
SafetyNetwork accessDaVinci Resolve MCP Server can launch or reconnect to Resolve, switch pages, create or open projects, modify timelines, manage media pools, write markers, change render settings, and queue jobs.
SafetyExecution & processesExtension-authoring tools can install or remove Resolve scripts, Fuses, DCTLs, ACES DCTLs, presets, and page scripts.
SafetyNetwork accessSource media is intended to remain immutable by default, but operators must still review requests that relink, replace, transcode, proxy, render, export, or create media derivatives.
SafetyGeneralThe default server is local stdio, but the local control panel starts a single-user browser server; keep it on trusted local interfaces only.
SafetyExecution & processesRequire confirmation before deleting projects, replacing clips, changing project settings, installing extensions, updating metadata, or queuing renders.
SafetyNetwork accessKeep Resolve external scripting set to `Local` unless you have a separate remote-control security plan.
PrivacyLocal filesProject names, timelines, clip names, media paths, markers, metadata, render paths, transcripts, thumbnails, analysis artifacts, logs, and Resolve scripting paths can be exposed to the MCP client.
PrivacyLocal filesMedia analysis can produce sidecar files, scratch artifacts, frame paths, transcripts, searchable indexes, and reports that may include private footage details.
PrivacyThird-party handlingHost-chat visual analysis can expose selected frame images to the active MCP client or vision-capable model provider.
PrivacyLocal filesLocal logs and analysis reports may contain absolute media paths, project names, clip metadata, speaker text, visual descriptions, and render settings.
PrivacyData retentionStore generated analysis artifacts and exports inside approved project or scratch directories and delete them when no longer needed.
Disclosure: Community-maintained MIT MCP server for DaVinci Resolve Studio. The server is open source, but using it requires DaVinci Resolve Studio and Blackmagic Design's local scripting API.
Safety notes
DaVinci Resolve MCP Server can launch or reconnect to Resolve, switch pages, create or open projects, modify timelines, manage media pools, write markers, change render settings, and queue jobs.
Extension-authoring tools can install or remove Resolve scripts, Fuses, DCTLs, ACES DCTLs, presets, and page scripts.
Source media is intended to remain immutable by default, but operators must still review requests that relink, replace, transcode, proxy, render, export, or create media derivatives.
The default server is local stdio, but the local control panel starts a single-user browser server; keep it on trusted local interfaces only.
Require confirmation before deleting projects, replacing clips, changing project settings, installing extensions, updating metadata, or queuing renders.
Keep Resolve external scripting set to `Local` unless you have a separate remote-control security plan.
Privacy notes
Project names, timelines, clip names, media paths, markers, metadata, render paths, transcripts, thumbnails, analysis artifacts, logs, and Resolve scripting paths can be exposed to the MCP client.
Media analysis can produce sidecar files, scratch artifacts, frame paths, transcripts, searchable indexes, and reports that may include private footage details.
Host-chat visual analysis can expose selected frame images to the active MCP client or vision-capable model provider.
Local logs and analysis reports may contain absolute media paths, project names, clip metadata, speaker text, visual descriptions, and render settings.
Store generated analysis artifacts and exports inside approved project or scratch directories and delete them when no longer needed.
Prerequisites
DaVinci Resolve Studio 18.5 or newer; the free edition does not support the required external scripting API.
Resolve external scripting set to `Local`.
Python 3.10 or newer, with Python 3.10-3.12 recommended for the broadest Resolve compatibility.
A local MCP client that can launch stdio servers under the same user account that operates Resolve.
Review of which projects, timelines, media pools, scripts, render settings, and media-analysis roots Claude may modify.
Schema details
Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
25 minutes
Difficulty
advanced
Tool listing metadata
Disclosure
Community-maintained MIT MCP server for DaVinci Resolve Studio. The server is open source, but using it requires DaVinci Resolve Studio and Blackmagic Design's local scripting API.
DaVinci Resolve MCP Server connects Claude and other MCP clients to DaVinci
Resolve Studio through Resolve's official scripting API. It provides a default
compound server for lower context usage and an optional granular mode for users
who need one tool per Resolve API method.
Use it when Claude needs supervised local access to Resolve projects, timelines,
media pools, renders, review markers, color workflows, Fusion, Fairlight, or
source-safe media analysis.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, npm metadata, license, security policy, installation guide, media
analysis guide, compound server, and granular server entrypoint for current
setup and behavior details.
Features
Launch or reconnect to DaVinci Resolve Studio.
Manage projects, project folders, databases, settings, presets, and archives.
Import, organize, normalize, relink, and inspect media pool items and bins.
Create, probe, edit, duplicate, move, and validate timelines and timeline
items.
Copy, move, export, and report review markers, flags, and annotations.
Validate render settings and queue render jobs.
Probe and update grading state, CDL payloads, Gallery stills, LUTs, and DRX
workflows.
Create and inspect Fusion compositions and guarded graph connections.
Inspect audio mappings, voice isolation, subtitles, and Fairlight properties.
Run source-safe media analysis jobs and write approved summaries or markers
back into Resolve project metadata.
Use a local browser control panel for status and analysis review.
Installation
Open DaVinci Resolve Studio, enable Local external scripting, then run the npm
setup command:
npx davinci-resolve-mcp setup
The installer detects Resolve paths, creates a managed Python environment, and
can configure supported MCP clients. A manual MCP server command can be launched
through the managed npm wrapper:
Use the default compound server unless you specifically need the full granular
tool surface.
Use Cases
Ask Claude to open a Resolve project and summarize its timelines.
Create an assembly timeline from approved clips.
Detect gaps, overlaps, missing media, or source-frame ranges.
Prepare render settings and validate them before queueing a job.
Copy review markers and export a review report.
Snapshot a grade, validate CDL changes, or export a temporary LUT.
Build a Fusion TextPlus overlay and verify graph connections.
Run source-safe media analysis and review sidecar reports before publishing
metadata back into the Resolve project.
Safety and Privacy
DaVinci Resolve MCP Server controls a local creative application with real
project state. Keep the user confirmation boundary active for destructive or
high-impact operations, and test workflows against duplicate projects before
letting an agent touch production edits.
Treat media paths, frame exports, transcripts, thumbnails, markers, render
settings, and analysis reports as sensitive production artifacts. Store them in
approved scratch or project directories and keep source media immutable unless
the user explicitly requests a specific media-changing operation.
Show that DaVinci Resolve MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/davinci-resolve-mcp-server)
How it compares
DaVinci Resolve MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
MCP server for controlling DaVinci Resolve Studio through the official scripting API, with tools for projects, timelines, media pools, render setup, review markers, grading, Fusion, Fairlight, and source-safe media analysis.
MCP server and CLI for AI image and video generation with gallery search, prompt enhancement, model listing, local preferences, ComfyUI workflows, MeiGen Cloud, and OpenAI-compatible provider support.
MCP and REST server for creating short-form videos from scene text, Pexels search terms, text-to-speech, captions, background music, Whisper captions, FFmpeg, and Remotion rendering.
Official Agentset MCP server that lets Claude retrieve cited knowledge-base results from an Agentset namespace through the `knowledge-base-retrieve` tool, with optional tenant scoping and custom tool descriptions.
✓DaVinci Resolve MCP Server can launch or reconnect to Resolve, switch pages, create or open projects, modify timelines, manage media pools, write markers, change render settings, and queue jobs.
Extension-authoring tools can install or remove Resolve scripts, Fuses, DCTLs, ACES DCTLs, presets, and page scripts.
Source media is intended to remain immutable by default, but operators must still review requests that relink, replace, transcode, proxy, render, export, or create media derivatives.
The default server is local stdio, but the local control panel starts a single-user browser server; keep it on trusted local interfaces only.
Require confirmation before deleting projects, replacing clips, changing project settings, installing extensions, updating metadata, or queuing renders.
Keep Resolve external scripting set to `Local` unless you have a separate remote-control security plan.
✓MeiGen can submit image and video generation jobs to external providers or a local ComfyUI backend.
Image and video generation may spend credits, use paid APIs, or consume local GPU resources depending on the configured provider.
Local reference images can be compressed and uploaded through the configured upload gateway before being sent to API providers.
Video generation can take minutes, may time out at the MCP client, and should not be retried blindly because jobs or credits may already be in progress.
ComfyUI workflow import and modification can run local workflows; review workflow JSON and custom nodes before use.
✓Short Video Maker runs an HTTP server with MCP SSE routes and REST routes for creating and serving generated videos.
The create-short-video tool queues video rendering work that can consume CPU, memory, disk, browser rendering resources, and optional GPU resources.
Generated videos combine user-provided narration text, Pexels search terms, downloaded background clips, local music assets, TTS output, captions, and rendered media.
The server stores generated videos and temporary files under its configured data directory.
Validate scene text, search terms, claims, branding, and rights before publishing generated videos to TikTok, Instagram, YouTube, or other platforms.
✓The MCP server sends Claude's retrieval queries to the Agentset API using the configured API key and namespace.
The `knowledge-base-retrieve` tool can return up to 100 results per call and can rerank results by relevance.
Namespace and tenant selection control which indexed documents are searchable; review them before connecting a shared agent.
API keys should be scoped, rotated, and stored only in the MCP server environment or a secret manager.
Custom tool descriptions can influence when the model calls the retrieval tool, so review them before use in production workflows.
Privacy notes
✓Project names, timelines, clip names, media paths, markers, metadata, render paths, transcripts, thumbnails, analysis artifacts, logs, and Resolve scripting paths can be exposed to the MCP client.
Media analysis can produce sidecar files, scratch artifacts, frame paths, transcripts, searchable indexes, and reports that may include private footage details.
Host-chat visual analysis can expose selected frame images to the active MCP client or vision-capable model provider.
Local logs and analysis reports may contain absolute media paths, project names, clip metadata, speaker text, visual descriptions, and render settings.
Store generated analysis artifacts and exports inside approved project or scratch directories and delete them when no longer needed.
✓API tokens, OpenAI-compatible credentials, provider base URLs, upload gateway URLs, ComfyUI URLs, preferences, recent generations, prompts, model IDs, and output paths can reveal private creative workflows.
Uploaded reference images may become public URLs through the configured upload gateway before generation.
Prompts, reference images, generated image URLs, generated video URLs, saved outputs, and favorite prompts can contain client work, brand plans, product images, personal likenesses, or unreleased campaigns.
Keep secrets in MCP client environment configuration, review generated media before sharing, and remove local outputs when retention is no longer needed.
✓`PEXELS_API_KEY` is sent to the Pexels API when searching for background videos.
Scene text, search terms, generated narration, captions, video IDs, logs, output filenames, and render status can reveal campaign ideas, private scripts, brand plans, or client work.
Generated files remain on disk until removed according to the deployment's data-directory and retention practices.
Pexels requests, model downloads, Docker pulls, npm installs, and platform uploads may expose network metadata to third parties outside the MCP client.
✓Retrieved chunks can include private documents, product specs, policies, support content, internal procedures, historical project information, or customer-specific data.
Retrieval queries, namespace IDs, tenant IDs, document chunks, citations, and tool outputs may be visible to the MCP client, model provider, Agentset logs, and application telemetry.
Tenant IDs are useful for data segregation, but incorrect tenant or namespace configuration can expose the wrong knowledge base.
Do not paste API keys, namespace IDs, tenant IDs, or retrieved private chunks into shared issue reports, screenshots, or repository files.
Prerequisites
DaVinci Resolve Studio 18.5 or newer; the free edition does not support the required external scripting API.
Resolve external scripting set to `Local`.
Python 3.10 or newer, with Python 3.10-3.12 recommended for the broadest Resolve compatibility.
A local MCP client that can launch stdio servers under the same user account that operates Resolve.
Node.js 18 or newer.
MCP client that can launch a local Node stdio server.
Optional MeiGen API token, OpenAI-compatible API key, or local ComfyUI workflow configuration for generation tools.
Provider pricing, credits, model limits, and content policy reviewed before image or video generation.
Node.js or Docker available on the machine that will run the video server.
Pexels API key configured through `PEXELS_API_KEY`.
Enough CPU, memory, and disk for Whisper, Kokoro, FFmpeg, Remotion, temporary files, and rendered videos.
MCP client that can connect to an SSE MCP endpoint.
Agentset account or self-hosted Agentset deployment with a populated namespace.
Agentset API key with access to the namespace Claude should query.
Node.js 18.17 or newer for running the `@agentset/mcp` package.
Namespace ID selected with `--ns` or `AGENTSET_NAMESPACE_ID`.
Install
npx davinci-resolve-mcp setup
Run `npx -y meigen` from an MCP client, or use the upstream plugin/init commands after reviewing provider credentials and generated-media costs.
Run the upstream Docker image or `npx short-video-maker` with `PEXELS_API_KEY` set, then connect an MCP client to the server's `/mcp/sse` endpoint.
Run `npx @agentset/mcp --ns <namespace-id>` with `AGENTSET_API_KEY` set in the MCP server environment.