How to Edit Videos With Claude (via MCP)

By AI Video Generator· Published 27 August 2026

The direct answer to the question people arrive with: Claude cannot edit video on its own. It has no video engine. What it can do is operate video software that exposes an MCP server, which produces a workflow that feels like editing by conversation but is really Claude pressing the buttons for you.

Two tools reviewed on this site support that today. This guide covers what the workflow is actually like, where it genuinely saves time, and where the enthusiasm outruns the reality.

What is actually happening

When you ask Claude to clip a video, nothing about the model touches the footage. Claude reads the list of operations a connected tool has declared — clip, reframe, caption, export — and calls them in a sensible order, passing along what you asked for.

That distinction matters because it sets the ceiling. The output quality is the video tool’s, not Claude’s. Connecting a mediocre generator to a capable assistant produces mediocre video, promptly. What improves is the number of steps between intention and result.

See video editing with MCP for the protocol itself.

What you need

Requirements. Verify current setup steps against vendor documentation — MCP server invocation changes between releases.
	What
An MCP client	Claude Desktop, or another compliant client such as Cursor
A video tool with an MCP server	Shorz or OpusClip among the tools reviewed here
Configuration	One entry in the client's MCP config naming the server
The machine	For desktop tools, the computer running the app must be on

What the workflow looks like

Rather than a fabricated transcript, here is the shape of it honestly described.

You ask for an outcome, not a sequence. “Take the recording in this folder, pull out the three strongest ninety-second segments, caption them and export vertical.” Without MCP that is four interface journeys per clip. With it, it is one instruction and a wait.

It reports back and you correct. The assistant tells you what it produced. You look at it, say the second one starts too early, and it re-cuts. That loop — describe, inspect, adjust — is the actual working pattern, and it is much closer to directing than to editing.

Batches are where it earns its place. One video is barely worth the setup. Thirty is a different proposition: the repetitive part is exactly what the assistant is good at, and the part needing judgement collapses into reviewing a list of outputs.

What it is good at

Repetitive sequences. Same operations, many files. This is the whole case.
Format conversion at volume. Reframing a back catalogue for vertical is tedious and mechanical, which is to say ideal.
Getting to a rough assembly fast. Particularly when the tool can hand off — OpusClip’s XML export lands the assistant’s cuts in Premiere or Resolve as a timeline you finish properly.
Not switching applications. If you already work in Claude, the video tool becomes another thing in reach rather than another window.

What it is not good at

Taste. The assistant will confidently select the wrong ninety seconds. It has no sense of which moment lands, and it will not tell you when it is unsure. Review everything.

Frame-level work. Anything needing precise timing belongs in an editor. The realistic division is MCP for the first pass, an NLE for the finish.

Working while you are away. For a desktop tool the application runs on your machine, so the computer has to be on and unlocked. This is automation, not a cloud service.

Anything the tool cannot already do. MCP exposes existing operations. If the software cannot do something through its own interface, the assistant cannot make it.

Which tool to connect

If your input is existing long footage, connect OpusClip — clipping is what it is for, and the editor export gives the assistant’s work somewhere to go. OpusClip review.

If your input is a script and no footage, connect Shorz, which can generate as well as clip. Note it is Windows-only. Shorz review.

If you are choosing between them properly, Shorz vs OpusClip covers the trade in full — including where Shorz loses.

Common questions

Can Claude edit videos?

Not by itself — Claude has no video engine. Connected over MCP to a tool that exposes one, it can drive that tool: clipping, captioning, reframing and exporting. The video capability is the tool's; Claude supplies the instructions.

Which video tools can Claude control?

Any tool exposing an MCP server. Among those reviewed here, both Shorz and OpusClip do. Shorz can be driven for generation as well as clipping; OpusClip needs existing footage.

Do I need Claude Desktop specifically?

No. MCP is an open standard, so any compliant client works — Cursor is a common alternative. Claude Desktop is simply the most widely used one.

Is editing over MCP faster than doing it manually?

For batches, considerably — the repetitive interface work disappears. For a single video it is usually slower once setup is counted. The saving scales with how many times you repeat the same sequence.

Can Claude decide which parts of a video are interesting?

It will make a selection, and it will be confident about it. Whether the selection is good is another matter — this is the part that still needs your judgement, so treat the output as a draft rather than a result.

Does this work while my computer is off?

Not for desktop tools such as Shorz, where the application runs locally and the machine must be on. Web-based tools are less constrained, but the assistant still has to be running somewhere to issue the instructions.