Inspect a project
Ask which project and timeline are active. Compare the names in Resolve. This is a small, observable first request — not an invitation to reorganise a library.
RESOLVE / MCP / AI ASSISTANTS
MCP in DaVinci Resolve
From a request
to a verified action.
Understand native MCP and third-party bridges, connect an AI assistant, and verify what actually happens in DaVinci Resolve.
01 / REQUEST02 / TOOL03 / VERIFY
COMMAND / INSPECT / VERIFYTEACHING MODEL
YOUR REQUEST
Which project is open right now?
Current projectAction boundaryRead the current state. Do not open or create a different project.
Check in ResolveThe returned name matches the open project in Resolve.
When to stop
No open project → report that state instead of choosing a project.
This page does not connect to Resolve. The diagram shows an intended workflow, not returned tool data.
01
MCP is the connection. Not the editor.
A conversation is the starting point. A real operation still needs an available tool, valid inputs and a result you can inspect.
Model Context Protocol is a standard for connecting AI applications to external data and tools. The assistant interprets your request; its host application manages the connection and approvals; a server exposes operations. Resolve remains the application holding the project. MCP does not itself choose edits or guarantee that a request is understood correctly.[3][5]
01YOU
Define the task
02AI CLIENT
Plan and request
03MCP SERVER
Expose a tool
04RESOLVE
Return actual state
05YOU
Verify the result
02
Three routes. Different responsibilities.
Native MCP, a community bridge and direct scripting are not interchangeable installation instructions.
| Route | What you use | What to check |
|---|---|---|
| Native Resolve MCPBLACKMAGIC DESIGN | The server supplied with Studio 21.1 and later; start with File → Setup AI Assistants.[1][2] | The installed build, detected client and its actual tools. This is the route used in our first-connection guide. |
| Third-party MCP bridgeSEPARATE SOFTWARE | A separately maintained server. It may wrap the Scripting API and add its own helpers. Requirements belong to that project, not to the MCP standard.[3] | Author, code, permissions, dependencies, version and licence. Do not apply its install commands or tool list to the native server. |
| API / PythonDIRECT SCRIPT | An explicit sequence of API operations without a conversation as the primary interface. MCP is not required for this approach. | Inputs, return values, error handling and repeatability. See the existing Python library and your installed Scripting README.Python guides → |
A third-party bridge does not automatically remove Resolve version or edition restrictions. Check that exact implementation; we do not offer a universal Free-edition workaround here.
03
Start with tasks you can independently check.
Prepare an audit
Ask for a report with a defined scope and clearly marked unavailable fields. Decide in advance what you will compare: names, settings, offline-media status or markers.
Automate a repeated task
After validating a small change on disposable material, consider a saved script with explicit parameters. A fresh conversation need not be the interface for every identical batch.
A useful request has boundaries.
Replace “clean up my project” with a named target, an allowed operation, a stopping condition and an expected report. Before any write, ask for a plan and check what the tool or script will touch.
“Use the currently selected timeline. Read its name without switching timelines. If none is selected, stop and tell me. I will check the name in Resolve.”
04
Keep the limits visible.
A tool list, not a magic number
The client can request the current catalogue using tools/list, including pagination where present. Read names, descriptions and input schemas. A tool that executes code can represent many operations; a larger catalogue is not automatically better.
Approval is a decision
Inspect sensitive calls and the proposed script before approving them. A request to “read only” is not an operating-system permission boundary. An assistant with broad tools may still be able to write files or alter a project.
Local does not mean private
A local server describes where the tool runs, not where the model processes its input. Review your client and model provider’s data settings; for the first test, use material without client names or confidential information.
THE FIRST PRACTICAL GUIDE
Make the connection observable.
Native setup, manual fallback, a bounded first request and a checklist that distinguishes configuration from a working Resolve connection.
Open the connection guideA local tools/list reader, input schemas, behaviour hints and result checks.
JSON / LEARNING DESKExplore a catalogue without running toolsStart with clearly labelled fictional examples or paste a redacted result.
FROM CONTRACTS TO TASKS
A task you can actually check.
Five bounded cases: project, Media Pool and timeline reports, render preflight and one marker on a disposable copy. Requests, stopping rules and observation sheets.
Open practical workflowsFAQ
Before you connect
Do I need DaVinci Resolve Studio?
For the native route described here, yes: Blackmagic lists AI-assistant integration for Studio 21.1. Do not assume that a community server supports the free edition on the same release.[1][2]
Do I have to install Python or Node.js first?
Not as a universal MCP prerequisite. Follow the requirements of the chosen server. This guide begins with Resolve’s supplied server; dependencies from a third-party installer are a different route.[1][4]
Will it work with any AI chat window?
The host application needs the relevant MCP transport and permissions. A website chat, a desktop client and a command-line client are different integrations, even when they use the same model. This first guide focuses on Claude Desktop.[3][4]
Does MCP mean an autonomous editor?
No. It supplies an integration mechanism. Task planning, available operations, the model’s decisions and output checks still have to be designed. Do not promise arbitrary editing just because a server connected.[3][5]
Has this exact setup been live-tested here?
No. This publication is based on the cited documentation and the stated review date. The guide includes a local acceptance procedure; the website does not detect your Resolve installation or issue a compatibility certificate.
Eight symptoms, logs, uncertain writes and a recovery checklist. The final part of the current five-guide series.
LOCAL / DIAGNOSTIC WORKSHEETPrepare the next checkRecord what is known and what is uncertain. No automatic repair or permission to change the project.
REFERENCE DESK
Documentation, not assumptions.
Checked on 5 October 2026. Menu labels are kept in English so they can be matched to the documentation. For Blackmagic’s large PDF, the relevant manual page was checked through a publicly available reproduction; the original document is linked below. No live Resolve session was used.
- Blackmagic Design · Resolve 21.1 Reference Manual
Using DaVinci Resolve with AI Assistants, printed p. 4318: native setup and script permissions. Large PDF.
- Blackmagic Design · Support
Version and edition: AI-assistant integration is listed for Studio 21.1. Version 21.1.1 was available at review time.
- Model Context Protocol · Introduction
What MCP standardizes and how an application connects external tools.
- Model Context Protocol · Connect local servers
Claude Desktop: local configuration, restarting, permissions and logs.
- Model Context Protocol · Tools
The tools/list catalogue, input schemas, calls, errors and user control.
- Anthropic · Claude Code MCP
Registering a local stdio server, configuration scope and inspecting the client entry.
- Model Context Protocol · Transports
stdio uses a client subprocess, not a local web-server URL. Specification version 2025-11-25.