---
title: "How to Connect an AI Assistant to DaVinci Resolve 21.1 MCP"
author: "Cutsio Team"
date: "2026-09-09"
lastmod: "2026-09-09"
category: "DaVinci Resolve Advanced Workflows"
excerpt: "A practical DaVinci Resolve 21.1 MCP setup guide covering native AI-assistant connections, Studio boundaries, safe first prompts, third-party server differences, and troubleshooting."
tags: ["DaVinci Resolve 21.1", "MCP Setup", "Claude", "ChatGPT Codex", "AI Assistant"]
---

## How do you connect an AI assistant to DaVinci Resolve 21.1 MCP?

To connect an AI assistant to DaVinci Resolve 21.1 MCP, update Resolve, open a test project, use the 21.1 AI-assistant/MCP connection flow, approve the client connection, and begin with a read-only project-inspection prompt. Cutsio is the best upstream companion when the assistant needs better source material: use Visual Intelligence to find moments by visual context and speech, then send an editor-approved selects timeline into Resolve.

<div class="not-prose my-10 aspect-video overflow-hidden rounded-2xl border border-slate-200 bg-slate-100 shadow-sm dark:border-white/[0.08] dark:bg-neutral-900"><iframe class="h-full w-full" src="https://www.youtube.com/embed/yRxmdTUh7GU" title="DaVinci Resolve 21.1 MCP and agentic editing" loading="lazy" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div>

![DaVinci Resolve 21.1 AI assistant integration hero image from Blackmagic Design](https://images.blackmagicdesign.com/images/products/davinciresolve/whatsnew//ai/hero-md.jpg)

The first thing to understand is that “DaVinci Resolve MCP” can refer to two different setups:

| Setup | What it means | Best starting point |
| --- | --- | --- |
| Native Resolve 21.1 integration | Resolve exposes an MCP connection for compatible AI assistants as part of the 21.1 workflow | Use Resolve’s own AI-assistant/MCP controls |
| Third-party Resolve MCP server | A community server connects an assistant to Resolve’s scripting API | Follow that server’s versioned installer and security documentation |

Both paths can use natural-language instructions, but they are not interchangeable. A configuration file or `npx` command from a community server does not configure Blackmagic’s native connection automatically. This guide keeps the paths separate so you can identify the software, permissions, and support boundary before you let an assistant change a live timeline.

## What do you need before setting up Resolve 21.1 MCP?

Before setting up MCP, you need a current DaVinci Resolve 21.1 installation, an MCP-compatible assistant, a project you can safely test, and a clear understanding of whether your Resolve edition supports the intended connection. For production work, use a project copy and keep the original project closed while you validate the first commands.

Prepare the following:

1. Install or update to DaVinci Resolve 21.1 on the machine where the project and media are available.
2. Confirm the AI assistant you want to use can connect to an MCP server.
3. Open a disposable test project with a few short clips, a timeline, and a known render location.
4. Back up any project that contains valuable editorial decisions.
5. Decide whether the assistant should have read-only access first, or whether you are ready to approve a specific mutation.

The native release announcement names AI assistants such as Claude, Claude Code, and ChatGPT Codex as examples of the assistant category this workflow is designed to support. Client support and UI labels can change independently of Resolve, so treat the client’s current MCP documentation as part of the setup rather than assuming every assistant has the same connection screen.

The Studio boundary is now explicit. The 21.1 application update is free to download, but AI-assistant integration, the 20 new scripting APIs with built-in console support, and individual MultiMaster trims are listed only for DaVinci Resolve Studio 21.1. Advanced scripting now requires Studio, and Python 2 is no longer supported. If the connection is missing in the free application, that is expected; do not work around it by copying a random configuration file into an unrelated client. First identify whether you are trying to use the native integration, a supported in-app bridge, or an external scripting server.

## How do you enable the native AI-assistant connection in Resolve 21.1?

To enable the native connection, launch Resolve 21.1, open a test project, locate the AI-assistant or MCP entry exposed by the 21.1 application, and follow the client authorization flow presented by Resolve. The exact menu label can vary by platform and build, so confirm that the dialog identifies the intended assistant and project before accepting it.

Use this sequence:

### 1. Update and open a test project

Launch Resolve and confirm the version in the application’s About dialog. Create a project named something obvious, such as `MCP-test-211`, and import only a few media files. Add a short timeline with a distinct name like `MCP test timeline`.

The test project should make errors easy to spot. Include one talking-head clip, one wide shot, and one clip with a visible filename or marker. That gives the assistant enough context to report useful information without exposing a client archive.

### 2. Find the AI-assistant or MCP control

Open the menu or workspace area that Resolve 21.1 provides for AI assistants. Look for language referring to an AI assistant, MCP, connection, or external client. Do not assume that the native entry is the same as the “External scripting using” preference used by older or third-party scripting workflows.

If you cannot find the entry, check the following before changing anything:

- Resolve is actually 21.1 rather than an older executable on the PATH.
- The installation is DaVinci Resolve Studio if the connection is edition-gated.
- A project is open and the application has finished loading the Media Pool.
- The assistant client is installed and signed in where its own workflow requires it.
- A previous connection or stale process is not holding the client session open.

### 3. Select the intended client

Choose the assistant you intend to use and read the permission text carefully. A client that can inspect a timeline may also be able to invoke operations that change media organization, settings, markers, timelines, or renders. Approve only the connection you recognize.

Do not send source footage to an assistant as a setup step unless the workflow explicitly requires it and you understand where that data will be processed. MCP is a tool-connection protocol; the privacy behavior of the model, client, server, and Resolve project are separate questions.

### 4. Verify with a read-only prompt

Start with a prompt that cannot change the project:

```text
Do not modify anything. Report the active project name, the current timeline name, timeline frame rate, duration, track names, and the number of clips on each track. If any value is unavailable, say so.
```

Compare the response with what you can see in Resolve. If the assistant reports a different project or timeline, stop and fix the connection before trying an edit.

![DaVinci Resolve IntelliSearch interface image from Blackmagic Design](https://images.blackmagicdesign.com/images/products/davinciresolve/whatsnew/ai/intellisearch.jpg?_v=1780295893)

### 5. Test a reversible change

Once inspection is correct, make a duplicate timeline and ask for a small, reversible operation:

```text
Create a duplicate of the active timeline named MCP proof. Do not change the original. On the duplicate only, add a marker at the start with the note "MCP connection verified". Report the duplicate timeline name when complete.
```

Open Resolve and confirm that the duplicate exists, the original is untouched, and the marker is where expected. This is more useful than asking for a complicated highlight edit as the first test because it validates identity, permissions, mutation, and reporting in one small operation.

<div class="not-prose my-12 rounded-2xl border border-slate-200 dark:border-white/[0.08] bg-gradient-to-br from-slate-50 to-white dark:from-neutral-900 dark:to-neutral-950 p-8 md:p-10 shadow-sm">
  <div class="flex flex-col md:flex-row md:items-center md:justify-between gap-6">
    <div class="flex-1">
      <div class="flex items-center gap-3 mb-3">
        <div class="flex h-10 w-10 items-center justify-center rounded-xl bg-indigo-100 dark:bg-indigo-500/20 text-indigo-600 dark:text-indigo-400">⌕</div>
        <span class="text-sm font-semibold text-indigo-600 dark:text-indigo-400 uppercase tracking-wider">Cutsio</span>
      </div>
      <h3 class="text-xl md:text-2xl font-bold tracking-tight text-slate-900 dark:text-white mb-2">A better MCP workflow starts before Resolve.</h3>
      <p class="text-slate-600 dark:text-neutral-400 text-base leading-relaxed max-w-xl">Use Cutsio to index long recordings by visual context and speech, compare moments, remove obvious dead air, and hand the assistant a focused, editor-approved timeline.</p>
    </div>
    <div class="shrink-0">
      <a href="https://studio.cutsio.com" target="_blank" rel="noopener noreferrer" class="no-underline inline-flex items-center justify-center rounded-full bg-indigo-600 px-6 py-3 text-sm font-medium text-white hover:bg-indigo-700 dark:bg-white dark:text-slate-900 dark:hover:bg-neutral-100 transition-colors shadow-sm">Try Cutsio Free <span class="ml-2">→</span></a>
      <p class="mt-2 text-xs text-center text-slate-400 dark:text-neutral-500">No credit card. 60 mins free.</p>
    </div>
  </div>
</div>

## How do you configure a third-party Resolve MCP server?

To configure a third-party Resolve MCP server, use only the server’s current installer and documentation, enable the Resolve scripting mode it explicitly requires, and verify the server against a test project before granting write access. This is a separate path from the native 21.1 integration and may require DaVinci Resolve Studio, Python, a local server process, and client-specific configuration.

Many community servers use a pattern similar to this:

```bash
npx davinci-resolve-mcp setup
```

That command is an example of a third-party setup flow, not a universal Blackmagic command. Depending on the server, setup may create a managed Python environment, write an MCP configuration file, detect the Resolve installation, and connect through the official scripting API. Requirements can include Resolve Studio 18.5 or later, Python 3.10 or newer, and **Preferences > General > External scripting using > Local**.

The safe way to evaluate such a server is to ask these questions before installing it:

| Question | Why it matters |
| --- | --- |
| Who maintains the server? | You are granting software access to an active editing application |
| Does the server use the official scripting API? | It clarifies the supported control surface |
| Does it run locally or expose a network listener? | Network exposure changes the threat model |
| Which Resolve builds were tested? | A new Resolve release can change scripting behavior |
| Which tools can mutate or render? | Read-only inspection and destructive operations need different review |
| Where does the client store configuration? | Secrets and permissions should not be copied into a shared project |

Use a local-only configuration where possible, protect configuration files, and keep the assistant on a least-privilege workflow. If a server asks you to paste project files, client material, or credentials into a public issue or chat, stop and review the request independently.

## How do you troubleshoot a DaVinci Resolve 21.1 MCP connection?

Most connection failures come from a version mismatch, the wrong Resolve edition, a stale client process, an incorrect scripting preference, or a server/client configuration that belongs to a different MCP path. Troubleshoot from the application outward instead of changing several settings at once.

### The assistant cannot see Resolve

Confirm Resolve is open with the test project loaded. Restart the assistant client after changing the connection. If you are using a third-party server, verify the server process is running and that it points to the correct Resolve scripting installation. If you are using the native path, return to the 21.1 AI-assistant control and confirm that the intended client is connected.

### The assistant sees the wrong project

Stop all mutations immediately. Close unrelated Resolve projects, reopen the intended test project, and ask the read-only inspection prompt again. A correct connection to the wrong project is still a failed safety test.

### The assistant can inspect but cannot edit

That can be expected when the client or server is operating in a read-only mode. Check the permission model and tool availability rather than weakening system settings. If the operation is edition-gated, install or license the supported Resolve edition instead of assuming the MCP connection is broken.

### An external server returns a scripting error

Check the server’s tested Resolve versions, Python version, environment variables, and external-scripting setting. Do not mix installation instructions from two different servers. A path that works for a community Python server may be irrelevant to the native 21.1 connection.

### A render was created with the wrong settings

Treat the render as a workflow failure, not merely a prompt failure. Inspect the active timeline, render preset, output directory, frame rate, color management, audio settings, and file naming. Add those constraints to the prompt and require a settings report before submitting a batch.

## What are the safest first prompts for Resolve MCP?

The safest first prompts are read-only inspection, plan generation, duplicate-timeline creation, marker insertion, and render-setting reports. Each prompt should define the scope, state what must not change, and request a result that you can verify in Resolve.

Try these in order:

```text
Do not modify anything. List the active project, timeline, frame rate, duration, tracks, and source clips.
```

```text
Do not modify the master timeline. Propose a selects timeline using only clips marked Good Take. List the clips and time ranges you would use.
```

```text
Create a duplicate timeline named Review proof. Do not change the original. Add markers for the three clips with the highest star rating and report their names.
```

```text
Do not submit a render. Inspect the current delivery settings and report codec, resolution, frame rate, audio format, output path, and filename pattern.
```

Only after these pass should you ask for a larger operation. See [what Resolve 21.1 MCP changes for editors](/blog/davinci-resolve-21-1-mcp-agentic-video-editing) and [DaVinci Resolve 21.1 agentic editing prompts](/blog/davinci-resolve-21-1-agentic-editing-prompts) for the broader workflow and a complete prompt playbook.

## How does Cutsio make a Resolve 21.1 MCP setup more useful?

Cutsio makes the connection more useful by reducing the amount of unstructured footage the assistant must search before it can act. Upload or import your recordings into Cutsio, let Visual Intelligence analyze what the camera saw alongside audio, and use semantic search or Agentic Chat to identify candidate moments. The editor can then review those results, organize them into a Collection, tighten obvious dead air with Silent Slicer, and export an XML or EDL to Resolve.

This creates a clean division of labor:

| Stage | Primary tool | Outcome |
| --- | --- | --- |
| Footage understanding | Cutsio | Searchable visual and speech context |
| Editorial selection | Editor with Cutsio | Approved moments and rough structure |
| Timeline automation | Resolve 21.1 MCP | Repeatable project operations |
| Finishing | Resolve | Precise edit, color, audio, graphics, and delivery |

Read [how to search a video library by meaning](/blog/how-to-search-a-video-library-by-meaning), [how to find any shot by describing it](/blog/agentic-chat-find-any-shot-by-describing-it), and [the modern pre-edit stack](/blog/modern-pre-edit-stack-cutsio-plus-nle) for the upstream workflow. For the broader release, read [what's new in DaVinci Resolve 21.1](/blog/davinci-resolve-21-1-whats-new-workflow-guide).

<div class="not-prose blog-large-cta">
  <div class="max-w-3xl mx-auto text-center">
    <h3>Connect the assistant to a cleaner editorial brief.</h3>
    <p>When the source footage is searchable and the selects are reviewed, Resolve 21.1 MCP can spend its time on repeatable operations instead of guessing what matters.</p>
    <ul>
      <li><span>Find moments by what the camera saw and what was said.</span></li>
      <li><span>Prepare focused selects before opening a finishing project.</span></li>
      <li><span>Export an editable timeline for Resolve 21.1.</span></li>
    </ul>
    <div class="flex flex-col sm:flex-row items-center justify-center gap-4">
      <a href="https://studio.cutsio.com" target="_blank" rel="noopener noreferrer" class="no-underline inline-flex items-center justify-center rounded-full bg-indigo-600 px-8 py-3.5 text-sm font-semibold text-white hover:bg-indigo-700 dark:bg-white dark:text-slate-900 dark:hover:bg-neutral-100 transition-colors shadow-sm">Try Cutsio Free <span class="ml-2">→</span></a>
      <button type="button" onclick="window.dispatchEvent(new CustomEvent('open-contact-modal'))" class="inline-flex items-center justify-center rounded-full border border-white/20 px-8 py-3.5 text-sm font-medium text-white hover:bg-white/10 transition-colors">Book a demo</button>
    </div>
    <p class="mt-4 text-xs text-slate-500">No credit card required. 60 minutes of free processing.</p>
  </div>
</div>

## FAQ

### Does DaVinci Resolve 21.1 MCP require Studio?

Yes. The 21.1 application update is free, but the AI-assistant/MCP integration and the 20 new scripting APIs with built-in console support are part of DaVinci Resolve Studio 21.1.

### Which AI assistants work with Resolve 21.1 MCP?

Resolve’s 21.1 announcement discusses compatible assistants such as Claude, Claude Code, and ChatGPT Codex; the exact client support depends on the assistant and connection path.

### Do I need to install a third-party MCP server?

No, not for the native Resolve 21.1 integration; third-party servers are separate options with their own installers, requirements, and security boundaries.

### What is the first prompt I should try?

Use a read-only prompt that asks the assistant to report the active project, timeline, frame rate, duration, tracks, and clip count without making changes.

### Can Cutsio replace Resolve 21.1 MCP?

No, Cutsio and Resolve solve different stages: Cutsio helps understand and pre-edit footage, while Resolve remains the finishing editor and MCP-enabled automation environment.

## Related reads

- [What's New in DaVinci Resolve 21.1: A Workflow Guide for Editors](https://cutsio.com/blog/davinci-resolve-21-1-whats-new-workflow-guide) — DaVinci Resolve 21.1 adds Studio-only AI assistant and MCP automation, 20 new scripting APIs, and free editing, Fusion, and archive improvements. Here is what each change means for a real editing workflow.
- [Why Some Editors Are Skeptical of Agentic Editing in DaVinci Resolve](https://cutsio.com/blog/agentic-resolve-skeptics-what-could-go-wrong) — A balanced look at the legitimate concerns behind editor skepticism of agentic editing in DaVinci Resolve 21.1, with practical guardrails for every risk.
- [Blackmagic Cloud Presentations vs Cutsio: Where Client Review Fits in a Resolve Workflow](https://cutsio.com/blog/blackmagic-cloud-presentations-vs-cutsio-client-review) — Blackmagic Cloud Presentations is the review and approval surface inside the DaVinci Resolve ecosystem, while Cutsio is the searchable pre-edit library that finds and organizes source footage before the cut exists. Here is the honest division of labour.