Can Claude Code control DaVinci Resolve directly?

Not by itself. Claude Code is a command-line agent; it has no built-in way to click inside Resolve's window. Resolve does ship a Python/Lua scripting API, so a script Claude writes has somewhere to plug in, but that's Claude scripting the app from outside, not reading and editing a timeline the way it edits code.

Is there a claude code davinci resolve MCP server?

Community MCP servers that wrap Resolve's scripting API exist, built by third parties, not Resolve or Anthropic. Check what a given one actually exposes (which API calls, which permissions) before pointing it at a real project.

Is there a claude code davinci resolve skill I should install?

A Claude Code skill can package prompts and steps for working with Resolve's scripting API, but it still runs through that API, with the same limits. It doesn't give Claude a timeline it can see and edit directly.

How do I get a Claude-edited cut into DaVinci Resolve?

Edit on a timeline the agent can actually read and write, then export a format Resolve imports: EDL, FCPXML or OpenTimelineIO. In Shoty, Claude Code edits the project directly over a local MCP server, and the cut leaves as one of those formats for Resolve to open.

Does this need a Claude API key?

No, if you're using Shoty. It runs the official Claude Code CLI on your machine, signed in with your own Claude account, and never sees the token. Anthropic's own plan limits and policies still apply.

Claude Code DaVinci Resolve: What Works Today, and the Real Route

"Cut the dead air out of this interview and get it into DaVinci Resolve." Say that to Claude Code in a chat window and, today, you get a script to run against Resolve's scripting API or an explanation of where its panels are. Say the same thing while Claude is holding an actual timeline, and the cuts happen, then the project lands in Resolve as an EDL. Same instruction, different result, because of what's on the other end of it.

Can Claude Code actually drive DaVinci Resolve?

Honestly: not on its own. Claude Code is a command-line agent. It reads and writes files and runs commands; it has no way to click a button inside Resolve's window. The paths people use to bridge that gap, for Resolve specifically:

Resolve's own Python/Lua scripting API. Resolve ships this, so a script Claude writes has something real to call into: add a clip, move a cut, trigger a render. It's the deepest access any of Claude's usual hosts gets to in this comparison.
Community MCP servers that wrap that scripting API so Claude can call it as a tool instead of writing raw script files. These are built by third parties, not Resolve or Anthropic, so check what a given one actually exposes before trusting it with a real project.
Having Claude write the script, and you run it inside Resolve's console. This keeps Claude out of the editing loop; it hands you homework instead of doing the edit.

None of these give Claude a timeline it can see, reason about, and edit the way it edits code. The scripting API is real and useful, but it's still Claude operating Resolve from outside, one API call at a time, rather than holding the project the way it holds a codebase.

The route that gives Claude a real timeline

Shoty is a desktop video editor (Mac and Windows) with an agent chat built in. Pick Claude · my subscription in the model picker and the shape of the problem changes:

Shoty runs the official claude CLI on your machine, signed in with your own Claude account. It never sees your token and charges no fee for the agent.
For each turn, Shoty opens a local MCP server and hands Claude tools: look at a frame, read and update the timeline, generate a shot, export. Every call shows up in the chat.
The timeline is a text format (.shoty), so Claude reads and edits a structure, the same way it reads and edits code, instead of calling a scripting API one function at a time.
When the cut is done, Shoty exports it as EDL, FCPXML or OpenTimelineIO. That file is what DaVinci Resolve, Premiere Pro or Final Cut Pro opens for the finish.

Claude never touches Resolve directly in this flow. It edits a project Resolve can later read, which sidesteps the scripting API entirely for the part Claude is actually doing.

1. Do the cut in Shoty, not in Resolve

Ask for the rough cut, a VFX fix, the subtitle pass, whatever Claude is good at, while the project is still in Shoty.

Cut the dead air out of the first five minutes, keep room tone under the cuts, and add burned-in English subtitles.

2. Name what must not change

The clip above swaps the background behind the people on the sofa for a rooftop at dusk, keeping them, their motion and the camera move exactly as they were. That's the instruction pattern for any VFX fix before export:

Replace the background behind the two people with a rooftop at dusk. Keep them, their motion and the camera move exactly as they are.

3. Export for Resolve

Export this project as an EDL for DaVinci Resolve.

FCPXML and OpenTimelineIO work too; Resolve reads all three. If you also want to keep scripting inside Resolve after the import, its Python/Lua API is still there and separate from this workflow.

4. Finish where you already work

Color and mix happen in Resolve like they always have. Shoty's job ends at the cut and the AI shots; Resolve's part of the job doesn't change.

Where this still needs you

Picking the beat. Claude finds every pause fast; which one actually lands is still an editor's call, and you can always grab the Shoty timeline and trim by hand.
Reviewing generated shots. Anything Claude sends to a video model costs credits, so set the run mode to review if you want to approve shots before they render.
Round-trips. If Resolve-side notes mean a shot needs to change again, that change happens back in Shoty, not by re-scripting Resolve.

Download the free Shoty editor and connect Claude Code from the model picker. For the general case across any host, see how to edit video with Claude, or for the same question about Premiere Pro, Claude Code Premiere Pro.