Skip to main content

How to edit a video with Claude Code, step by step (2026)

Claude Code can drive a real video editor through MCP. Here is the setup, the prompts that work, and where you still need to step in.

Written by
The Delivvo team
Published
Updated
Reading time
8 min
A laptop running video editing software beside a phone on a desk
On this page
  1. What Claude Code can and can't do with video
  2. Step 1: install the editor and Node.js
  3. Step 2: connect Claude Code
  4. Step 3: a full example edit
  5. Prompts that work, and prompts that don't
  6. Keep every client's look consistent
  7. Export settings that matter
  8. Limits to plan around
  9. How Delivvo's Cutroom keeps the edit on your machine and the client in the loop
  10. FAQ

To edit a video with Claude Code, connect it to a video editor that exposes its tools over MCP, then describe the edit in plain words. Claude Code calls the editor's tools to cut, caption, reframe and export while you watch the timeline. You check the result and fix anything by hand. This guide uses Cutroom, Delivvo's desktop editor, as the worked example.

What Claude Code can and can't do with video

Claude Code is an agent that reads, plans and calls tools. On its own it has no video timeline, so asking it to "edit my video" only works if it can reach an editor. The Model Context Protocol is the bridge: it is "an open-source standard for connecting AI applications to external systems" (Model Context Protocol), and Anthropic introduced it in November 2024 so AI tools could connect to the places work actually happens (Anthropic, 2024).

There are two kinds of MCP video tools. Some wrap a command-line tool such as ffmpeg and hand back a finished file. Others drive a real editor, so every change appears on a timeline you can see and undo. The second kind suits client work, because you need to adjust the result, not only accept or reject it.

Step 1: install the editor and Node.js

Install Cutroom on Windows 10 or 11, or on macOS 12 or later on an Apple Silicon or Intel Mac, from delivvo.io/cutroom. It costs $12 a month or $99 a year.

Connecting an AI agent needs Node.js on your computer. Use a long-term support release; the Node.js project advises that "production applications should only use Active LTS or Maintenance LTS releases" (Node.js). Cutroom tells you if Node.js is missing when you try to connect.

Step 2: connect Claude Code

Open Cutroom's Connect AI screen and pick Claude Code. Cutroom sets up the connection in one click.

If you prefer to see what that does, Claude Code's own documentation shows how a local MCP server is added: claude mcp add <name> -- <command> registers a server that runs on your machine, and the --scope option decides whether it loads for one project or all of them. Inside a Claude Code session, /mcp shows which servers are connected (Claude Code docs). Once Cutroom appears there, Claude Code can see its tools.

A video editor color grading footage on a multi-monitor editing timeline
A video editor color grading footage on a multi-monitor editing timeline

Step 3: a full example edit

Here is a realistic job: a 12 minute talking-head recording that needs to become a tidy landscape video and a 45 second vertical clip with captions.

Start a project and bring in the footage.

Create a new project called "March update", import the file on my desktop called march-raw.mp4, and transcribe it.

Cutroom transcribes on your machine, so the audio isn't uploaded.

Clean up the talk.

Remove silences longer than half a second and the filler words "um" and "uh". Show me the list before you apply it.

Asking for the list first keeps you in control. Accept everything, or skip the cuts that remove a natural pause.

Make it look finished.

Add captions in the bold white style, level the loudness for YouTube, and add a title card with "March update" for the first three seconds.

Make the vertical version.

Duplicate the timeline as a 9:16 version. Keep my face in frame. Pick the strongest 45 seconds about the new pricing and cut it down to that.

Export.

Export the landscape version for YouTube and the vertical version for Reels and Shorts.

Before calling the job done, the agent renders frames from the export, reads them back and checks the audio for clipping and cut-off words. You still watch it. Anything you dislike is a normal clip, effect or caption on the timeline that you can change or undo.

Prompts that work, and prompts that don't

Good prompts are specific about the outcome and leave the mechanics to the agent:

  • Name the target. "A 45 second vertical clip for Reels" beats "make it shorter."
  • Give a rule for judgement calls. "Keep pauses before a punchline" tells the agent what not to cut.
  • Ask to see before applying. For anything destructive, such as cutting silence across a long file, ask for a list first.
  • Refer to the transcript. "Start the clip at 'here is what changed'" is precise in a way timestamps often aren't.

Prompts that tend to disappoint are vague taste requests with no reference, such as "make it more cinematic." Give a reference or a concrete setting instead: a colour look, a pace, a caption style.

Keep every client's look consistent

When you edit for several clients, the slowest part is often remembering each one's fonts, colours and caption style. Save them once and refer to them by name. In Cutroom each project carries a brand kit with colours, fonts and a logo, and your library keeps the caption styles, fonts and presets you reuse, so a prompt like "use the Northwind caption style from my library" applies the right look every time.

The same idea works for recurring formats. If a client gets a weekly video with the same intro, lower third and end card, describe it once as a reusable preset, then ask the agent to "build this week's episode with the weekly preset." You review the new parts instead of rebuilding the same frame every Monday, and the client sees a series that looks like one series.

Export settings that matter

Match your export to where the video is going. For YouTube, Google recommends an SDR upload bitrate of about 8 Mbps for 1080p at standard frame rates and 35 to 45 Mbps for 4K (YouTube Help). Cutroom's export presets cover YouTube, Shorts and Reels, TikTok, LinkedIn, X, the web and a ProRes master, so you rarely need to set these by hand.

Limits to plan around

Agent-driven editing is fast at the repetitive work and still needs a human for taste:

  • It doesn't know your client. Brand rules, words to avoid and the client's favourite take need to be in the prompt or fixed by hand.
  • Generation costs money elsewhere. If you ask for generated images, voice or video, that runs on the provider whose key you added and bills to your account with them.
  • Long files take time. Transcribing an hour of footage locally depends on your computer's speed.
  • You still review. The agent checks its work, and you are still the one who sends it to the client.

For a wider view of the field, see every video editing MCP server in 2026, and for what the tool itself is, what Cutroom is.

How Delivvo's Cutroom keeps the edit on your machine and the client in the loop

Cutroom does the editing on your computer, and Delivvo carries the job from the client's brief to the final payment.

  1. Edit locally with your own agent. Cutroom's MCP server gives Claude Code more than 120 editing tools. Your footage stays on your machine, and you use your own Claude account, so there is no AI bill from Delivvo.
  1. Every AI change stays editable. Captions, graphics, cuts and grades are normal items on the timeline, the Activity tab lists every step, and any step can be undone.
  1. Quote the work before you start. In Delivvo, send the client a quote with your editing packages, the contract and the deposit on one page. They pay through your own Stripe, PayPal or Square, and Delivvo takes 0%.
  1. Deliver through the client portal. Upload the finished landscape and vertical versions to the client's Delivvo portal. They sign in with a one-time code, review and approve, and the final invoice sits next to the files.
  1. Pay only for what you use. Cutroom is $12 a month or $99 a year, billed separately from Delivvo plans, with one login for both. There is no per-export fee and no credit meter on the local editing, so a heavy month of client videos costs the same as a quiet one. The only usage costs are the ones you choose to run on your own AI provider, such as generated images or voice, and those bill to your account with that provider rather than through Delivvo.

See the full feature list on the Cutroom page.

FAQ

Can Claude Code edit videos?

Not on its own. Claude Code can drive a video editor that exposes its tools over MCP, such as Cutroom, and do the edit through that editor while you watch.

Do I need to know how to code to edit video with Claude Code?

No. You describe the edit in plain words. Cutroom sets up the Claude Code connection in one click, and you only need Node.js installed.

Does my video get uploaded when Claude Code edits it?

Not to Delivvo. The editing and transcription in Cutroom run on your computer. The agent reads frames and audio to check its work, and anything you ask it to generate goes to your own provider.

Which other AI agents can do the same?

Any agent with MCP support, including Claude Desktop, OpenAI Codex, Gemini CLI, Cursor, Windsurf, VS Code and Cline.

Delivvo runs the whole client cycle for service businesses, from the first inquiry to the quote, contract, deposit, invoice and delivery, and Cutroom lets Claude Code edit the video on your own machine. Clients pay you directly through your own gateway, and Delivvo takes 0%. See Cutroom

Written by

The Delivvo team

Delivvo runs the client cycle for service businesses: inquiry, quote, contract, deposit and delivery. Payments go straight to your own account.

More about Delivvo

Your inquiry link is free.

Free plan. No card needed.