Can the Codex CLI control DaVinci Resolve directly?

Not on its own. Codex CLI is a command-line agent: it writes and runs code, but it has no way to click a button inside Resolve's window. Resolve ships a Python/Lua scripting API, so a script Codex writes has something real to call into, but that's still Codex operating Resolve from outside, one API call at a time, not holding a timeline it can see.

Is there a codex davinci resolve MCP server?

Community MCP servers that wrap Resolve's scripting API so an agent can call it as a tool exist, built by third parties, not Resolve or OpenAI. Check what a specific one actually exposes, which calls and which permissions, before pointing it at a real project.

Is the Codex CLI different from ChatGPT for this?

In Shoty they're the same agent under the hood: picking ChatGPT in the model picker runs the official Codex CLI on your machine. The difference above is Codex CLI alone in a terminal, writing scripts against Resolve's API with no project it can see, versus Codex CLI holding an actual timeline through Shoty's tools.

Can Codex write DaVinci Resolve scripts?

Yes, and that's where it's genuinely strong. Codex is a coding agent, so a script aimed at Resolve's Python/Lua API, adding a clip, nudging a cut, triggering a render, is something it drafts well. Running it, confirming it did what you asked and fixing it when it didn't is still on you, since a terminal agent has no eyes on Resolve's panels.

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

Edit on a timeline the agent can read and write directly, then export a format Resolve imports: EDL, FCPXML or OpenTimelineIO. In Shoty, the agent behind the ChatGPT (Codex CLI) option edits the project over a local MCP server, and the cut leaves in one of those formats for Resolve to open.

Codex DaVinci Resolve: What the CLI Can Script, Not See

A sofa against a plain wall. A beat later the wall is a rooftop at dusk, the person on the sofa and the camera's slow push untouched. That's the clip above, and it's close to what "codex davinci resolve" searches are actually asking: can a terminal coding agent make Resolve do that?

What Codex can reach inside Resolve today

DaVinci Resolve ships a real Python/Lua scripting API, deeper access than most editors expose. Point the Codex CLI at it and you get a genuinely useful tool: it can draft a script that adds a clip, nudges a cut point, or kicks off a render, because writing code against a documented API plays to exactly what a coding agent is built for.

What that script can't do is see. Codex CLI has no way to look inside Resolve's window, check that the edit it just pushed landed where it meant to, or notice a clip is one frame off. Community MCP servers that wrap Resolve's scripting API close part of that gap, letting Codex call Resolve functions as tools instead of hand-writing script files, but they're built by third parties, not Resolve or OpenAI, so check what calls and permissions a given one actually exposes before trusting it with a real project. Either way, it's still Codex operating Resolve from outside.

The three things a finished edit needs

Seeing the shot, not guessing from a filename or a script's own assumptions about what's in frame.
Acting on the real timeline, placing and trimming clips in the project itself, not in a file a script hopes applies cleanly.
Generating or fixing a shot and placing the result back, instead of leaving a rendered file for you to drag onto a track.

A script that calls Resolve's API from a terminal can be well written and still miss all three, because nothing in that loop reads the result back.

The route that gives Codex a real timeline

Shoty is a desktop video editor (Mac and Windows) with an agent chat built in. Pick ChatGPT · my subscription in the model picker and Shoty runs the official Codex CLI on your machine, signed in with your own OpenAI account, with no fee from Shoty for the agent.

Each turn, Shoty opens a local MCP server and hands Codex 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 Codex reads and edits a structure the way it reads and edits code, rather than calling Resolve's scripting API one function at a time.
When the cut is done, Shoty exports it as EDL, FCPXML or OpenTimelineIO, the formats DaVinci Resolve, Premiere Pro and Final Cut Pro all open for the finish.

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

1. Hand Codex the part it's actually good at

Write a batch of clean, numbered filenames for these clips so the project reads in order, then cut the dead air out of the first five minutes.

2. Name what must not change on a VFX fix

Replace the wall behind the sofa in shot 2 with a rooftop at dusk. Keep the person, their pose and the camera's push exactly as they are.

3. Export for Resolve

Export this project as an EDL for DaVinci Resolve.

If you still want to script inside Resolve after the import, for something like Resolve FX automation or a Fusion node setup, its Python/Lua API is there and separate from this workflow.

Where this still needs you

Judging the cut. Codex can draft and execute fast; which beat lands is still an editor's call, and the Shoty timeline is always open to trim by hand.
Approving generated shots. Anything sent to a video model costs credits, so set the run mode to review if you want to sign off before it renders.
Resolve-native work. Magic Mask, the Fusion page, and anything that needs Resolve Studio stay exactly where they are; Shoty hands off a timeline, it doesn't replace Resolve's own tools.

Download the free Shoty editor and pick ChatGPT (Codex CLI) from the model picker. For the Claude Code version of the same setup, see Claude Code DaVinci Resolve, or for Premiere Pro, Codex Premiere Pro.