How to Use Claude / Codex with MCP/CLI for Video Editing (Without Resolve Studio)
Searching for Resolve 21.1 MCP setup with Claude or ChatGPT Codex? Here is the Studio path in brief — then the PilotCut path: BYO agent via terminal MCP/CLI on a local Mac project, free during beta.
The short version
People searching “how to use Claude with MCP for video editing” or “ChatGPT Codex Resolve MCP” are often looking at DaVinci Resolve 21.1’s native MCP server. That path is real — and Studio-only.
If you want agentic editing on a local Mac timeline without buying Resolve Studio for MCP access, PilotCut is built for that job: local MCP + Agent CLI, BYO Claude Code or Codex, free during beta. You still pay your own agent subscription.
Resolve walkthrough we cite: DaVinci Resolve 21.1 BEST New Feature TESTED - AI Editing with Claude and ChatGPT (Team 2 Films). For Studio pricing, Blackmagic lists Studio at $295 USD one-time (taxes/regional vary).
Path A — Resolve Studio 21.1 native MCP (brief)
Per the Team 2 Films demo:
- Install DaVinci Resolve Studio 21.1 (native MCP is not on free Resolve in that video).
- Use an agent that supports Anthropic’s MCP protocol — the demo uses Claude (Pro) + Claude desktop.
- In Resolve: File → Setup AI Assistance, then follow the prompts and permission dialogs.
- Prompt the agent; it calls Resolve’s API, not the GUI. Expect limits where the API has no function (the demo used FFmpeg as a workaround for timecode). Transcription helped rough assembly; IntelliSearch visual data was not exposed to the agent in their account of the feature.
That is a strong path if you already live in Resolve for color, Fusion, Fairlight, and delivery. It is also Studio + agent cost, layered on a deep NLE.
Path B — PilotCut: Claude Code / Codex on a local project
PilotCut is a native macOS, local-first editor. Media and project stay on your Mac. Edit, preview, and render stay local. Prompts, transcript text, and frames an agent is asked to inspect follow that agent’s provider.
High-level setup:
- Install PilotCut from pilotcut.com (free during beta).
- Open or create a local project — your footage lands in a
.pcbundleon the Mac, not an upload-for-edit cloud queue. - Pick your agent in the terminal catalog — featured labels include Claude Code, Codex, Grok Build, GitHub Copilot, OpenCode, and Antigravity. Bring the agent you already pay for.
- Connect via local MCP / Agent CLI — UI, CLI, and agents share one tool registry and project model (40+ tools is a fair shorthand; counts change across releases).
- Give bounded edit jobs — e.g. propose silence/filler cleanup from transcript evidence, tighten a section, prepare a short cut. Prefer propose → commit with dryRun; use peek filmstrip verify before you trust the pass.
- Review with taste, then export full-quality locally. Use FCPXML from the File menu when you need to leave for finishing elsewhere.
“A whole editing pass from a single prompt” means one prompt → many tool calls on the local .pcbundle. It is not text-to-video and not one-click finished video from a prompt alone.
What to ask the agent (examples)
Keep jobs specific and reversible:
- Propose cuts that remove long dead air and filler, preserving breath-safe snaps; do not auto-delete without commit
- Build a first-draft narrative order from transcript structure for a product demo
- Suggest B-roll slots; never delete human markers
- Prepare a vertical-friendly cut of a section, then stop for human review
Avoid vague prompts like “make it better.” Constraints beat vibes.
Resolve Studio MCP vs PilotCut CLI (quick)
| Step | Resolve Studio 21.1 | PilotCut |
|---|---|---|
| License | Studio (~$295 list) | Free during beta |
| Agent | Claude / MCP-capable client | BYO Claude Code, Codex, etc. |
| Wire-up | File → Setup AI Assistance | Local MCP + Agent CLI |
| Project | Resolve project / media pool | Local .pcbundle on Mac |
| Trust | Human review in Resolve | Propose → commit → peek |
| Best when | You need Resolve finishing | You need creator cleanup velocity |
PilotCut is not a full Resolve replacement for color, Fusion, or finishing. Hand off when the deliverable needs that suite.
Why API / MCP in a purpose-built editor helps
Agents that call structured timeline tools spend less effort rediscovering UI state. GUI computer-use can still bridge gaps — Resolve’s own demo mixed API calls with computer control when nodes were missing from the API — but for weekly screen and talking-head work, propose → commit on a shared project model stays easier to inspect and reverse.
Also read:
- Resolve Studio 21.1 native MCP vs PilotCut agent editing
- Bring your own agent: replace stacked point AI video subscriptions
- How to edit videos with AI agents
- ChatGPT for video editing? PilotCut is made for you
Bottom line
Resolve 21.1’s native MCP is a clear “how to use Claude with Resolve” answer — if you have Studio and want agents inside that NLE.
If you searched that phrase because you want Claude Code or ChatGPT Codex editing video via MCP/CLI without a Studio seat, PilotCut is the Mac path: local project, BYO agent, propose → commit, free during beta.
Try PilotCut — free during beta.
Related articles
September 8, 2026
Resolve Studio 21.1 MCP Is Real — The Scripting Gaps Still Block Human-Like Edits
DaVinci Resolve Studio 21.1 ships a native MCP server for Claude, Claude Code, and ChatGPT Codex. Studio-only, ~$295, BYO AI sub — and the Scripting API still cannot freely move, trim, or split like a human. Here is the detailed gap map, and why PilotCut shares the same editing primitives with UI and agent.
13 min read
September 8, 2026
Resolve Studio 21.1 Native MCP vs PilotCut Agent Editing
DaVinci Resolve Studio 21.1 ships a native MCP server for AI agents — Studio-only, plus your Claude or Codex sub. Here is what PilotCut offers instead for agentic editing on a local Mac timeline.
5 min read
April 29, 2026
How to Edit Videos with AI Agents
A practical way to think about agent-assisted video editing: use AI for structure and repetition, then keep human taste in the final pass.
1 min read