Video Editing MCP Servers

Video editing MCP servers are connectors that let an AI agent operate a video editor or video service through the Model Context Protocol. The editor publishes a set of tools, such as "list the bins," "find the clips where the guest talks about pricing," "make a vertical cut" or "render the deliverables," and an agent like Claude Code or Codex calls them. Until 2026, editing software exposed scripting APIs for developers. MCP made the same capabilities available to general-purpose agents through a common interface, and by October 2026 most major editors and many AI-first tools offered one. This page lists what exists as of October 2026, what each connector can and cannot do, and where human approval sits. The landscape changes monthly, so check vendor documentation before relying on any detail.

The Landscape as of October 2026

Product	Connector	What an agent can do	Notes and limits
DaVinci Resolve 21.1 Studio	Native MCP server (September 2026), set up from inside Resolve	Analyze projects, organize media, adjust settings, batch render, create highlight edits from long-form video, remove unwanted clips and render deliverables	Studio edition only. Blackmagic names Claude, Claude Code and ChatGPT Codex as clients. Python scripting also moved to Studio in 21.1.
Adobe Premiere	"Adobe for creativity" connector for Claude (April 2026)	For Premiere: resize and repurpose videos for social platforms	Narrow by design. Premiere's broader AI Assistant (public beta since June 2026) is an in-app, cloud-backed chat panel, not an MCP server.
Descript	Descript MCP, in Claude's connector directory and ChatGPT's app marketplace (June 2026)	Work with Descript projects and its agent co-editor, Underlord	Cloud projects. Descript's API has been in open beta since April 2026.
OpusClip	Hosted MCP server with 29 tools	Clip long videos into shorts and manage projects	Works with Cursor, Cline, Claude Code and ChatGPT/Codex. Read tools run without approval, and every call to a write tool needs approval. Paid plans only.
Eddie AI v4	API and MCP server with 113 tools (September 2026)	Assistant-editor work: logging, selects, rough cuts	Exports Premiere (.prproj), Resolve (.drp) and FCPXML projects, and reaches Avid through an extension.
Kapwing	Kapwing MCP	Work with Kapwing projects from Claude, ChatGPT or Codex	Kapwing says it cannot yet rename projects, access the brand kit, generate videos or edit videos with multiple assets.
Kling 4.0	MCP and CLI access	Batch video generation	A generation service, not an editor, listed on Kling's site for batch generation.
VEED OpenEdit	Agent skills plus a local renderer, not an MCP server	An agent writes the video as HTML and CSS and renders it on the user's machine	The pipeline is open source (Apache-2.0). It was tested with Claude Code, Codex and Gemini CLI and installs with `npx skills add veedstudio/open-edit`.

Two notable absences: Final Cut Pro (12.4, September 2026) has no MCP server or agent interface, and Avid Media Composer 2026.8 added agentic features and expanded automation APIs without an MCP server. Anthropic's Claude for Creative Work launch in April 2026 also included an MCP-based Blender connector, relevant to anyone who edits in Blender's sequencer.

Three Kinds of Connector

The connectors fall into three groups, and the differences matter more than tool counts:

Desktop editor servers. Resolve's server acts on projects and media on the user's own machine. Footage never has to leave it, and the agent can touch everything the editor can, which makes permissions the main question.
Hosted service connectors. Descript, OpusClip, Kapwing and Adobe's connector act on projects in the vendor's cloud under the user's account. They are easy to set up, scoped to what the vendor chose to expose, and dependent on uploading media first.
Skills and local pipelines. Here the agent writes a specification or code and a local renderer produces the video. Examples are VEED's OpenEdit, Remotion's Agent Skills and other tools built on video as code. This uses skills and the command line rather than MCP, and keeps the full edit as a reviewable artifact.

Where Human Approval Sits

MCP itself does not decide what an agent may do without asking. Approval can sit in three places:

In the client. Agents such as Claude Code ask before calling a tool unless the user has allowed it, so a cautious permission setup is the first line of defense.
In the server. OpusClip separates read tools from write tools and requires approval on every write. Better still is a dry-run step that returns what a change would do and requires a second, confirmed call to apply it, the plan-and-apply pattern.
Nowhere obvious. One reviewer of Resolve 21.1 noted the release came with little guidance on permissions or safeguards against destructive operations. With a server that can delete clips and render over files, back up the project first and start with read-only tasks.

Destructive and expensive actions deserve special care: deleting media, overwriting renders, spending generation credits and publishing. The human-in-the-loop rule of thumb applies. Let the agent gather, propose and draft, and keep approval of irreversible steps with a person.

Choosing a Connector

Where does the footage live? Local, large or sensitive footage favors a desktop server or a local pipeline. Cloud-native social video favors hosted connectors.
What edition is required? Resolve's server needs the paid Studio edition, and OpusClip's needs a paid plan.
How much does it expose? A large tool surface is powerful but costs context and invites mistakes. A good agent experience exposes fewer, well-described tools.
Can the result be finished elsewhere? Connectors that export to other editors through timeline interchange avoid lock-in.

Security Notes

An editor's MCP server reads transcripts, file names and on-screen text, all of which can carry prompt injection. A transcript line that reads like an instruction is still just a transcript line, and a well-behaved agent should treat it as data. Run local servers only from vendors you trust and keep them off untrusted networks. Prefer connectors that log every call, so it is clear afterward what the agent changed.

Where It's Headed

Expect connectors to appear in the MCP registry and in client directories, as Descript's already has, and expect more editors to follow Resolve with native servers. The open questions are standard operations across editors, which nobody has proposed yet, and approval models strong enough for professional projects. For the bigger picture of how agents edit, see agentic video editing and the hub page on AI video editing. This page will be reviewed every 60 days.