Blog · Explainers

MCP video editing: how Claude renders real video

MCP (the Model Context Protocol) is the standard way to give Claude tools. A video-editing MCP server gives it tools to receive your files, look inside them and send an edit to a renderer, so Claude makes the decisions and a real video pipeline produces the MP4. You add it in Claude as a custom connector, sign in once, and the tools are there in every chat where you turn it on.

"MCP" sounds like infrastructure, and it is. But the idea behind MCP video editing is simple: Claude decides what the video should be, and a program built for video does the work. MCP is the plug between them.

What MCP is, in one paragraph

The Model Context Protocol is an open standard for connecting AI assistants to outside tools. A service publishes an MCP server, and you add its address to Claude as a connector. From then on Claude can call that server's tools in the middle of a conversation, the same way it would search the web. Each tool describes its inputs, so Claude knows when and how to use it.

What a video MCP server needs to do

A good one covers the whole job, not just the export. Here is how the tools line up in Easy Reels in Claude:

JobToolWhat it does
Get files inmediaOpens an upload panel in the chat, or takes uploads from Claude Code
Look at themmedia (inspect)Returns timestamped frames and a transcript
Know the optionsassetsLists fonts, filters, LUTs, saved adjustments and transitions
Make the videorenderValidates the edit and queues the render
Follow itvideosReports progress and returns the download link
Pick where it goesworkspaceLists and switches Easy Reels workspaces

Without the "look at them" step, a video tool is guessing. That step is what lets Claude cut the right part of a long recording, as cutting a long video into reels with Claude shows.

The edit is a timeline, not a prompt

This is the part people expect to be magic and is the most practical. Claude doesn't send a sentence to a video model and hope. It writes a timeline: an exact list of scenes with their times and settings. A shortened example:

{
  "format": "9:16",
  "scenes": [
    { "media": "m_talk", "in": 723.4, "out": 741.0 },
    { "media": "m_photo", "duration": 3, "motion": "zoom_in",
      "transition": { "type": "fade", "duration": 0.5 } }
  ],
  "texts": [
    { "text": "How we price", "start": 0, "end": 2.5, "font": "bundled:montserrat" }
  ]
}

Because the edit is data, the renderer can check it before spending any time on it: a scene that ends before it starts, a transition longer than its scene, a file that isn't in the chat. Claude gets a precise error it can fix. It also means a change is cheap: "make the photo hold longer" edits one number and renders again.

The output follows the same rules as any vertical video, so vertical video dimensions still applies. Use 9:16 at 1080 × 1920 for Reels, TikTok and Shorts, and 4:5 or 1:1 for the feed.

Where your files go

Two questions to ask any video MCP server: where do the files live, and what can the assistant see?

With Easy Reels in Claude, uploads go to your Easy Reels storage and count toward your plan. Claude can only use the files sent in that chat. Your existing library is not browsed: a library file reaches Claude only when you pick it yourself in the upload panel. Finished videos land in My Generations, like everything else you make in the app.

The look comes from the app

A connector is more useful when it shares the app's toolkit rather than shipping a cut-down copy. Claude can apply the same filters and LUTs as the app, your own uploaded LUTs and saved colour adjustments, and set text in the same 100+ fonts. If you've built a grade you like, ask for it by name. Colour grading short video covers how to pick one.

Connecting it

Claude.ai and Claude Desktop. Settings, Connectors, Add custom connector, then paste:

https://mcp.easyreels.io/mcp

Click Connect, sign in to Easy Reels and choose Allow. In a chat, turn Easy Reels on from the tools menu.

Claude Code. One command in the terminal, then /mcp to sign in:

claude mcp add --transport http easyreels https://mcp.easyreels.io/mcp

Easy Reels in Claude is part of the Ultra plan. See pricing.

Common questions

Is MCP only for developers?

No. Setting up a connector in Claude.ai is a settings screen and a sign-in. The protocol matters to the people building the server; using it is just a chat.

Can Claude render video without an MCP server?

No. Claude has no video encoder of its own. It can plan the edit and write the text, but rendering needs a connected tool.

Does the connector run on my computer?

No. It's a remote server. The rendering happens on Easy Reels' side and the finished video comes back as a link and a player in the chat.

What happens if I change workspaces?

Each connection starts in your Default workspace. Ask Claude to switch ("use the Client A workspace") and the next uploads and renders go there.

Read next