OpusClip 4.0 is here. Become a content powerhouse.

The 10 Best Video Editing MCP Servers in 2026

July 28, 2026
·
Updated
November 3, 2026
Three creators with a five-star rating, a list of servers, a Connect button and a YouTube Shorts badge

"Video MCP server" now describes about six different jobs, and most roundups blur them together. A server that generates footage from a prompt, a server that renders JSON into an MP4, a server that indexes a video library for search, and a server that clips a podcast into shorts are not substitutes for each other. They are different layers of the same stack, and picking the wrong layer is the most common reason an agent workflow stalls halfway through.

So this is a map, sorted by what each server's tools actually do. How we compared these servers: we checked every endpoint, tool count, sign-in method and limit on November 3, 2026, against each vendor's own docs, repos and registry listings. We did not run hands-on tests of the other vendors' servers, tool counts change often, and the entries are specific enough (endpoints, named tools, stated limits) that each claim can be checked against the vendors' own pages. If the underlying concept is new, start here instead.

Clipping and repurposing: long video in, posts out

This is the most competitive layer in the stack and the one that changed most in the last year. All three servers below now clip, caption, reframe, and publish from an agent. The differences are in curation quality, how deep the editing goes, and what happens when the first result is not quite right.

OpusClip

Endpoint: https://mcp.opus.pro/mcp, hosted, OAuth sign-in with no API key. Tools: 37 on the MCP server (29 workflow tools plus 8 media tools). Claude.ai users add the Claude Connector instead, which carries the 29 workflow tools. Cursor, Cline, Claude Code, ChatGPT and Codex use the MCP server.

OpusClip takes a long video (from a URL or an upload link), finds the moments most likely to perform, and cuts clips with captions and AI reframing. Its project import accepts links from YouTube, Vimeo, Riverside, Loom, Zoom, StreamYard, Frame.io, Google Drive, and Dropbox, among others, so a recording goes straight from where it already lives into the workflow. Each clip carries a Virality Score from 0 to 99, built on hook, flow, and trend, and the server lists and describes clips per project.

The part that is genuinely uncommon is not the clipping: it is what happens after. edit_clip applies named operations to a rendered clip in one call: caption, emoji, and keyword-highlight toggles; filler-word and pause removal; section trim, split, drop, and reorder; phrase cutting; caption colour, position, and casing; clip dubbing (MCP server only); and undo. It re-renders the preview, and export_clip returns the HD download URL, because list and describe calls return preview URLs only. Of the clipping servers here, it is the one whose public tool list shows section-level edits against a rendered clip. We walk through the actual edits in the editing guide, and the tool reference goes through the tools one by one.

get_transcript returns paragraphs with start and end times and per-word timings, so an agent can find a phrase and compute an exact boundary. Posting, scheduling, queue listing, and unscheduling are all named tools (create_post_task, schedule_publish, list_scheduled_posts, unschedule_publish). OpusClip's Pro social scheduler supports YouTube, TikTok Feed, Instagram Reels, Facebook Page, LinkedIn, X (beta), Pinterest, Threads, and Bluesky. The media tools, MCP server only, add thumbnail, voiceover, music, and video generation, each quoted for free before it spends credits.

Limits worth knowing: API and MCP access are included on Pro (beta), Max, and Business plans (API keys come from the dashboard), and tool calls require one of those plans. Pro (beta) and Max get 15 hours or 900 credits per workspace per month with 4 concurrent projects; Business follows its contract. API projects have a 10-credit minimum. On the Claude Connector, posting, scheduling, unscheduling, and sharing return a link you confirm in OpusClip instead of committing, and dubbing and media generation are not available. OpusClip is listed in the Claude connector directory, the MCP Registry, Smithery, cursor.directory, and the Cline marketplace, and on npm as @opusclip/mcp.

Reap

Endpoint: https://mcp.reap.video/mcp, hosted, OAuth (API keys also accepted). Tools: 30.

The most direct alternative on the agent surface. Reap's site lists 30 tools across six categories: creating projects (upload URLs, clips, captions, transcription, reframe, dubbing), tracking and retrieving results, editing metadata, publishing, reference catalogs, and billing. Its docs say the server works on every plan, with one MCP connection on the Free plan.

Dubbing into 80+ languages is a first-class tool (dub_video) rather than a caption translation, which matters if your distribution is genuinely multilingual. Billing is also agent-accessible: an agent can check plan usage and get a checkout link for extra media credits, and admin keys can get a billing portal link, which is either convenient or alarming depending on your governance.

Its publishing surface is a full six tools, including listing and editing already-scheduled posts. If you read an older roundup saying Reap is API-only for posting, that is out of date.

Where it stops: its editing tools cover metadata (update_clip, update_video) and a hand-off to its web editor (open_in_editor) rather than the timeline. None of its listed tools trims or reorders sections of a rendered clip, so "trim four seconds off the front of clip 3" is a web-editor job rather than something an agent can do against the clip directly.

Submagic

Endpoint: https://api.submagic.co/mcp, hosted, Claude connector sign-in or Bearer API key. Tools: count not published.

Strong product with a sensibly chosen scope. Submagic's docs give example prompts rather than a tool list: creating a project from a URL, generating Magic Clips, checking project status, adding background music, listing caption templates, exporting, and publishing. It is also the only one of the three clipping servers whose docs describe published-post analytics, such as per-profile views, engagement, and publishing stats, so "which of last week's clips actually performed" is answerable in the same session that made them.

The notable difference is auth. Claude users connect through the Claude connector with a sign-in, but every other client passes an existing Submagic API key as a Bearer token, which means a key has to be generated from account settings, pasted, and stored somewhere. That is a small thing for a developer and a real barrier for everyone else, and the same key and credits serve both the REST API and MCP.

Where it stops: the public docs do not publish a definitive tool list, so we give no count, and its example prompts do not include timeline-level edits to a finished clip.

Generation: prompt in, footage out

Agent Opus

Endpoint: https://api.opus.pro/api/agent-mcp, hosted, OAuth (setup page at agent.opus.pro/mcp). Tools: 29.

The generation counterpart to the clipping server: text or a script in, a finished video out with AI voiceover, visual styles, and brand assets. Agent Opus's own documentation says video generation through MCP needs a Pro plan or above, while the whoami tool works on any plan so an agent can check access first.

The tool surface splits into project creation (prepare_project then start_project, with get_video to poll), a reusable asset library (logos, products, characters that can anchor any video), voice cloning and voice selection, visual style listing and customization, motion graphics, and posting and scheduling tools. Because both OpusClip and Agent Opus run as hosted MCP servers, an agent can have both connected and chain generate, clip, and schedule in one session.

Limits worth knowing: the help center lists generated videos of up to about 10 minutes in the script, audio, and song modes; voice cloning works from a sample of up to 30 seconds; and Free-plan downloads carry an Agent Opus watermark. Generation spends credits, and projects start only after a prepare step.

RunwayML

Endpoint: https://mcp.runwayml.com/mcp, hosted, sign in with a Runway account, no API key.

Strategically the most interesting server in the stack, because it is a menu rather than a dish. Through one connector, an agent can run generation on Runway's own Gen-4.5 and Gen-4 Turbo and on Kling 3.0, Google Veo 3.1, Seedance 2.5, GPT Image 2, and Nano Banana Pro, with the models available depending on the Runway account plan. Generations draw on Runway credits, the same as the Runway app. Runway runs a separate Dev MCP for API accounts; the generation server is this one.

That aggregation is worth thinking about as a pattern, not just a feature. Runway has made itself the surface through which its own competitors get called, which means an agent asking for "the best available model" reaches Runway first regardless of who wins the model race. If your workflow is "generate a shot," this is the widest single surface.

Replicate

Endpoint: mcp.replicate.com, hosted, authenticated with a Replicate API token through a web sign-in flow, with a local build (npx -y replicate-mcp) also available.

Search, compare, and run across Replicate's model catalog, which includes a text-to-video collection. Replicate's docs say the server supports all of the operations in its HTTP API, so an agent can search and compare models, fetch model metadata, run predictions, and fetch their results. An experimental Code mode, local only, swaps the per-operation tools for two tools: one for searching SDK docs and one for running TypeScript in a sandbox.

The tradeoff against Runway is control versus curation. Replicate gives you a far larger catalog and expects you to know which model you want; Runway gives you a shortlist someone has already vetted. Pick Replicate when model choice is the point.

Avatar and voice

HeyGen

Endpoint: https://mcp.heygen.com/mcp/v1/, hosted, OAuth. Tools: 98 listed in its docs.

The largest documented tool surface in this roundup. The tools span a video agent, avatar videos, templates, voices, audio search, video translation, lip sync, avatars, assets, brand, batches of up to 100, and, new since this post first ran, AI clipping (create_ai_clipping and three companion tools) and filler-word removal. Its docs say usage draws on the credits in an existing HeyGen plan, on every plan.

Directory presence is the more important lesson. HeyGen is in the Cursor marketplace, and Runway is in the ChatGPT plugin directory. OpusClip lists itself in the Claude connector directory, the MCP Registry, Smithery, cursor.directory, and the Cline marketplace, and Twelve Labs has an MCP Registry entry. Registry and store presence is how agent users find a server without someone pasting a URL.

One detail: HeyGen's docs cap HeyGen Video generation through MCP at 5 to 15 seconds, and point to the HTTP API for longer clips. The video agent and avatar video tools are separate from that limit.

Editing and rendering: programmatic composition

Shotstack

Endpoint: https://mcp.shotstack.io/, hosted, OAuth or an x-api-key header, with an mcp-remote bridge for stdio-only clients. Tools: 15.

The real render toolset in this category: an inline Studio canvas, direct render, render status, shareable Studio links, a guide tool for the edit format, six template tools (create, update, list, get, render, delete), and generation tools (list models, quote a price, generate an asset, check status). This is the server to reach for when video is assembled from data rather than captured, such as a personalized video per customer record or a weekly report rendered from a spreadsheet.

Client support is unusually broad: claude.ai, Claude Desktop, Claude Code, ChatGPT, Cursor, VS Code, Codex CLI, Gemini CLI, Windsurf, Zed, JetBrains, Goose, Raycast. Flagged as beta, so expect the tool surface to move.

One correction for anyone who found an older version of this list: Remotion, the open-source programmatic-video framework, shut down its hosted MCP server on October 26, 2026 and now points developers to Remotion Agent Skills (npx remotion skills add). Rendering itself still runs through Remotion's own CLI and renderer packages, not through an MCP server.

Infrastructure and understanding

Mux

Endpoint: https://mcp.mux.com, hosted, OAuth through the Mux dashboard (Basic token credentials for clients without OAuth). Tools: 2.

The infrastructure layer: Mux Video assets, direct uploads, playback IDs and live streams, Mux Data metrics and real-time dimensions, and Mux Robots jobs. Mux's docs say it is built on a Code Mode scheme with just two tools: search_docs for its API docs and execute, where the agent writes TypeScript against the full Mux SDK in an isolated sandbox.

The design is the interesting part. Instead of hundreds of endpoint tools, the agent gets two, which keeps the model's context small and makes multi-step tasks repeatable. That is a pattern worth copying, because agents make better choices with smaller tool lists, and a 40-tool server that dumps everything into context makes the model worse at picking. Mux's docs note that it does not treat destructive operations specially, so a read-only access token is the safe way to connect.

Twelve Labs

Endpoint: https://mcp.twelvelabs.io/jockey/mcp, hosted, OAuth with a TwelveLabs account.

Cross-video understanding through its Jockey agent: build a collection of videos and images, search across it, ask questions, and get text answers that cite the exact clips they draw from, with multi-turn refinement. This is the layer you want when the question is "find every moment in our 400-hour archive where someone mentions pricing" rather than "make me a video." TwelveLabs also lists a separate MCP Registry entry at mcp.twelvelabs.io that takes an API key header.

It pairs naturally with the clipping layer rather than competing with it. Twelve Labs finds the moment across a library; a clipping server turns that moment into something postable.

How to actually choose

Sort by the job, not the brand:

  • You have long recordings and need posts. Clipping layer: OpusClip, Reap, or Submagic. All three publish from the agent now, so decide on curation quality, how deep post-clip editing goes (OpusClip's edit_clip covers section-level edits and dubbing, while Reap's edit tools cover metadata plus a web-editor hand-off), whether you need Reap's 80+ language dubbing, and whether OAuth versus an API key matters to whoever is installing it.
  • You need footage that doesn't exist. Generation layer: Runway for model breadth, Replicate for catalog size, Agent Opus for script-to-finished-video.
  • You need a presenter without filming one. HeyGen, on its hosted server.
  • You're composing video from data or templates. Shotstack for a real render toolset; Remotion users now install Agent Skills instead of an MCP server.
  • You're building a product on top of video. Mux for infrastructure, Twelve Labs for search and understanding.
  • You want vertical versions of existing videos. Any of the clipping three will reframe, and OpusClip's reframing outputs 9:16, 1:1, 4:5, and 16:9.

One more decision sits underneath all of these: whether you want an agent driving the tools at all, or a pipeline you write yourself against the same capabilities. We put the two side by side in MCP versus API.

If you are building in code rather than through an agent, three companion roundups cover the other surfaces: the best video editing APIs for developers, the best CLI tools for video editing, and the best social media scheduling APIs.

Three patterns worth noticing

Hosted with OAuth has all but won. Nearly every serious server here is remote and authenticates through a sign-in flow, with API keys still common for headless use: Submagic outside the Claude connector, Shotstack in CI, and Replicate's remote server. Local stdio servers still make sense for developer context, but for agent distribution they are a dead end: too much install friction between "I want this" and "it works."

Publishing stopped being a differentiator this year. A year ago most video servers stopped at the export and left distribution to a second tool. Today all three clipping servers post and schedule from the agent, and two of them expose queue management. If a roundup still tells you posting is rare, check its date.

The new cut line is how deep the editing goes. Every server here can produce a video. Far fewer can change one after it exists. Metadata edits are common; section-level edits against a rendered clip, such as OpusClip's trim, split, reorder, and filler-word removal in one call, are not. That is where this category is competing next, because "the agent made something almost right" is the failure mode every one of these products actually has.

If clipping, editing, and publishing is the job you have, our setup guide gets the OpusClip server running, and the tool reference covers what each tool does.

Frequently asked questions

What is the best MCP server for video editing?

It depends on the job. For turning long recordings into short-form posts, the clipping layer (OpusClip, Reap, Submagic) is the right one, and all three now clip, caption, reframe, and publish from an agent. OpusClip's edit_clip tool handles section-level edits such as trims, splits, reorders, and filler-word removal, across 37 tools on its MCP server. Reap's site lists 30 tools and adds dubbing as a first-class tool. For programmatic composition from templates or data, Shotstack's server has 15 tools, including a real render toolset.

Which video MCP servers can post to social media?

All three in the clipping layer. OpusClip exposes posting, scheduling, queue listing, and unscheduling. Reap lists six publishing tools including listing and editing already-scheduled posts. Submagic publishes from an agent and adds published-post analytics. Agent Opus also lists posting and scheduling tools. Most rendering and infrastructure servers stop at the export.

Does Remotion have an MCP server that renders video?

No. Remotion shut down its hosted MCP server on October 26, 2026 and recommends Remotion Agent Skills (npx remotion skills add) for agents instead. Rendering runs through Remotion's own CLI and renderer packages, and for an agent-driven render server the closest fit in this list is Shotstack.

Are MCP servers for video hosted or do I install them locally?

The serious ones are hosted and remote, and nearly all use OAuth sign-in with nothing to install. Submagic uses a Bearer API key outside its Claude connector, and Replicate's remote server takes a Replicate API token. Local stdio servers still have a place in developer tooling, but install friction makes them a poor fit for agent distribution.

On this page

Use our Free Forever Plan

Find the moment. Skip the scrubbing.

From script to polished video — in one click.

Create and post one short video every day for free, and grow faster.

OpusSearch uses AI to surface the exact clip you need from hours of footage — in seconds, not afternoons.

Agent Opus runs the entire video pipeline for you: research, scriptwriting, storyboarding, motion, voice, and edit. Upload the idea, post the result.

The 10 Best Video Editing MCP Servers in 2026

"Video MCP server" now describes about six different jobs, and most roundups blur them together. A server that generates footage from a prompt, a server that renders JSON into an MP4, a server that indexes a video library for search, and a server that clips a podcast into shorts are not substitutes for each other. They are different layers of the same stack, and picking the wrong layer is the most common reason an agent workflow stalls halfway through.

So this is a map, sorted by what each server's tools actually do. How we compared these servers: we checked every endpoint, tool count, sign-in method and limit on November 3, 2026, against each vendor's own docs, repos and registry listings. We did not run hands-on tests of the other vendors' servers, tool counts change often, and the entries are specific enough (endpoints, named tools, stated limits) that each claim can be checked against the vendors' own pages. If the underlying concept is new, start here instead.

Clipping and repurposing: long video in, posts out

This is the most competitive layer in the stack and the one that changed most in the last year. All three servers below now clip, caption, reframe, and publish from an agent. The differences are in curation quality, how deep the editing goes, and what happens when the first result is not quite right.

OpusClip

Endpoint: https://mcp.opus.pro/mcp, hosted, OAuth sign-in with no API key. Tools: 37 on the MCP server (29 workflow tools plus 8 media tools). Claude.ai users add the Claude Connector instead, which carries the 29 workflow tools. Cursor, Cline, Claude Code, ChatGPT and Codex use the MCP server.

OpusClip takes a long video (from a URL or an upload link), finds the moments most likely to perform, and cuts clips with captions and AI reframing. Its project import accepts links from YouTube, Vimeo, Riverside, Loom, Zoom, StreamYard, Frame.io, Google Drive, and Dropbox, among others, so a recording goes straight from where it already lives into the workflow. Each clip carries a Virality Score from 0 to 99, built on hook, flow, and trend, and the server lists and describes clips per project.

The part that is genuinely uncommon is not the clipping: it is what happens after. edit_clip applies named operations to a rendered clip in one call: caption, emoji, and keyword-highlight toggles; filler-word and pause removal; section trim, split, drop, and reorder; phrase cutting; caption colour, position, and casing; clip dubbing (MCP server only); and undo. It re-renders the preview, and export_clip returns the HD download URL, because list and describe calls return preview URLs only. Of the clipping servers here, it is the one whose public tool list shows section-level edits against a rendered clip. We walk through the actual edits in the editing guide, and the tool reference goes through the tools one by one.

get_transcript returns paragraphs with start and end times and per-word timings, so an agent can find a phrase and compute an exact boundary. Posting, scheduling, queue listing, and unscheduling are all named tools (create_post_task, schedule_publish, list_scheduled_posts, unschedule_publish). OpusClip's Pro social scheduler supports YouTube, TikTok Feed, Instagram Reels, Facebook Page, LinkedIn, X (beta), Pinterest, Threads, and Bluesky. The media tools, MCP server only, add thumbnail, voiceover, music, and video generation, each quoted for free before it spends credits.

Limits worth knowing: API and MCP access are included on Pro (beta), Max, and Business plans (API keys come from the dashboard), and tool calls require one of those plans. Pro (beta) and Max get 15 hours or 900 credits per workspace per month with 4 concurrent projects; Business follows its contract. API projects have a 10-credit minimum. On the Claude Connector, posting, scheduling, unscheduling, and sharing return a link you confirm in OpusClip instead of committing, and dubbing and media generation are not available. OpusClip is listed in the Claude connector directory, the MCP Registry, Smithery, cursor.directory, and the Cline marketplace, and on npm as @opusclip/mcp.

Reap

Endpoint: https://mcp.reap.video/mcp, hosted, OAuth (API keys also accepted). Tools: 30.

The most direct alternative on the agent surface. Reap's site lists 30 tools across six categories: creating projects (upload URLs, clips, captions, transcription, reframe, dubbing), tracking and retrieving results, editing metadata, publishing, reference catalogs, and billing. Its docs say the server works on every plan, with one MCP connection on the Free plan.

Dubbing into 80+ languages is a first-class tool (dub_video) rather than a caption translation, which matters if your distribution is genuinely multilingual. Billing is also agent-accessible: an agent can check plan usage and get a checkout link for extra media credits, and admin keys can get a billing portal link, which is either convenient or alarming depending on your governance.

Its publishing surface is a full six tools, including listing and editing already-scheduled posts. If you read an older roundup saying Reap is API-only for posting, that is out of date.

Where it stops: its editing tools cover metadata (update_clip, update_video) and a hand-off to its web editor (open_in_editor) rather than the timeline. None of its listed tools trims or reorders sections of a rendered clip, so "trim four seconds off the front of clip 3" is a web-editor job rather than something an agent can do against the clip directly.

Submagic

Endpoint: https://api.submagic.co/mcp, hosted, Claude connector sign-in or Bearer API key. Tools: count not published.

Strong product with a sensibly chosen scope. Submagic's docs give example prompts rather than a tool list: creating a project from a URL, generating Magic Clips, checking project status, adding background music, listing caption templates, exporting, and publishing. It is also the only one of the three clipping servers whose docs describe published-post analytics, such as per-profile views, engagement, and publishing stats, so "which of last week's clips actually performed" is answerable in the same session that made them.

The notable difference is auth. Claude users connect through the Claude connector with a sign-in, but every other client passes an existing Submagic API key as a Bearer token, which means a key has to be generated from account settings, pasted, and stored somewhere. That is a small thing for a developer and a real barrier for everyone else, and the same key and credits serve both the REST API and MCP.

Where it stops: the public docs do not publish a definitive tool list, so we give no count, and its example prompts do not include timeline-level edits to a finished clip.

Generation: prompt in, footage out

Agent Opus

Endpoint: https://api.opus.pro/api/agent-mcp, hosted, OAuth (setup page at agent.opus.pro/mcp). Tools: 29.

The generation counterpart to the clipping server: text or a script in, a finished video out with AI voiceover, visual styles, and brand assets. Agent Opus's own documentation says video generation through MCP needs a Pro plan or above, while the whoami tool works on any plan so an agent can check access first.

The tool surface splits into project creation (prepare_project then start_project, with get_video to poll), a reusable asset library (logos, products, characters that can anchor any video), voice cloning and voice selection, visual style listing and customization, motion graphics, and posting and scheduling tools. Because both OpusClip and Agent Opus run as hosted MCP servers, an agent can have both connected and chain generate, clip, and schedule in one session.

Limits worth knowing: the help center lists generated videos of up to about 10 minutes in the script, audio, and song modes; voice cloning works from a sample of up to 30 seconds; and Free-plan downloads carry an Agent Opus watermark. Generation spends credits, and projects start only after a prepare step.

RunwayML

Endpoint: https://mcp.runwayml.com/mcp, hosted, sign in with a Runway account, no API key.

Strategically the most interesting server in the stack, because it is a menu rather than a dish. Through one connector, an agent can run generation on Runway's own Gen-4.5 and Gen-4 Turbo and on Kling 3.0, Google Veo 3.1, Seedance 2.5, GPT Image 2, and Nano Banana Pro, with the models available depending on the Runway account plan. Generations draw on Runway credits, the same as the Runway app. Runway runs a separate Dev MCP for API accounts; the generation server is this one.

That aggregation is worth thinking about as a pattern, not just a feature. Runway has made itself the surface through which its own competitors get called, which means an agent asking for "the best available model" reaches Runway first regardless of who wins the model race. If your workflow is "generate a shot," this is the widest single surface.

Replicate

Endpoint: mcp.replicate.com, hosted, authenticated with a Replicate API token through a web sign-in flow, with a local build (npx -y replicate-mcp) also available.

Search, compare, and run across Replicate's model catalog, which includes a text-to-video collection. Replicate's docs say the server supports all of the operations in its HTTP API, so an agent can search and compare models, fetch model metadata, run predictions, and fetch their results. An experimental Code mode, local only, swaps the per-operation tools for two tools: one for searching SDK docs and one for running TypeScript in a sandbox.

The tradeoff against Runway is control versus curation. Replicate gives you a far larger catalog and expects you to know which model you want; Runway gives you a shortlist someone has already vetted. Pick Replicate when model choice is the point.

Avatar and voice

HeyGen

Endpoint: https://mcp.heygen.com/mcp/v1/, hosted, OAuth. Tools: 98 listed in its docs.

The largest documented tool surface in this roundup. The tools span a video agent, avatar videos, templates, voices, audio search, video translation, lip sync, avatars, assets, brand, batches of up to 100, and, new since this post first ran, AI clipping (create_ai_clipping and three companion tools) and filler-word removal. Its docs say usage draws on the credits in an existing HeyGen plan, on every plan.

Directory presence is the more important lesson. HeyGen is in the Cursor marketplace, and Runway is in the ChatGPT plugin directory. OpusClip lists itself in the Claude connector directory, the MCP Registry, Smithery, cursor.directory, and the Cline marketplace, and Twelve Labs has an MCP Registry entry. Registry and store presence is how agent users find a server without someone pasting a URL.

One detail: HeyGen's docs cap HeyGen Video generation through MCP at 5 to 15 seconds, and point to the HTTP API for longer clips. The video agent and avatar video tools are separate from that limit.

Editing and rendering: programmatic composition

Shotstack

Endpoint: https://mcp.shotstack.io/, hosted, OAuth or an x-api-key header, with an mcp-remote bridge for stdio-only clients. Tools: 15.

The real render toolset in this category: an inline Studio canvas, direct render, render status, shareable Studio links, a guide tool for the edit format, six template tools (create, update, list, get, render, delete), and generation tools (list models, quote a price, generate an asset, check status). This is the server to reach for when video is assembled from data rather than captured, such as a personalized video per customer record or a weekly report rendered from a spreadsheet.

Client support is unusually broad: claude.ai, Claude Desktop, Claude Code, ChatGPT, Cursor, VS Code, Codex CLI, Gemini CLI, Windsurf, Zed, JetBrains, Goose, Raycast. Flagged as beta, so expect the tool surface to move.

One correction for anyone who found an older version of this list: Remotion, the open-source programmatic-video framework, shut down its hosted MCP server on October 26, 2026 and now points developers to Remotion Agent Skills (npx remotion skills add). Rendering itself still runs through Remotion's own CLI and renderer packages, not through an MCP server.

Infrastructure and understanding

Mux

Endpoint: https://mcp.mux.com, hosted, OAuth through the Mux dashboard (Basic token credentials for clients without OAuth). Tools: 2.

The infrastructure layer: Mux Video assets, direct uploads, playback IDs and live streams, Mux Data metrics and real-time dimensions, and Mux Robots jobs. Mux's docs say it is built on a Code Mode scheme with just two tools: search_docs for its API docs and execute, where the agent writes TypeScript against the full Mux SDK in an isolated sandbox.

The design is the interesting part. Instead of hundreds of endpoint tools, the agent gets two, which keeps the model's context small and makes multi-step tasks repeatable. That is a pattern worth copying, because agents make better choices with smaller tool lists, and a 40-tool server that dumps everything into context makes the model worse at picking. Mux's docs note that it does not treat destructive operations specially, so a read-only access token is the safe way to connect.

Twelve Labs

Endpoint: https://mcp.twelvelabs.io/jockey/mcp, hosted, OAuth with a TwelveLabs account.

Cross-video understanding through its Jockey agent: build a collection of videos and images, search across it, ask questions, and get text answers that cite the exact clips they draw from, with multi-turn refinement. This is the layer you want when the question is "find every moment in our 400-hour archive where someone mentions pricing" rather than "make me a video." TwelveLabs also lists a separate MCP Registry entry at mcp.twelvelabs.io that takes an API key header.

It pairs naturally with the clipping layer rather than competing with it. Twelve Labs finds the moment across a library; a clipping server turns that moment into something postable.

How to actually choose

Sort by the job, not the brand:

  • You have long recordings and need posts. Clipping layer: OpusClip, Reap, or Submagic. All three publish from the agent now, so decide on curation quality, how deep post-clip editing goes (OpusClip's edit_clip covers section-level edits and dubbing, while Reap's edit tools cover metadata plus a web-editor hand-off), whether you need Reap's 80+ language dubbing, and whether OAuth versus an API key matters to whoever is installing it.
  • You need footage that doesn't exist. Generation layer: Runway for model breadth, Replicate for catalog size, Agent Opus for script-to-finished-video.
  • You need a presenter without filming one. HeyGen, on its hosted server.
  • You're composing video from data or templates. Shotstack for a real render toolset; Remotion users now install Agent Skills instead of an MCP server.
  • You're building a product on top of video. Mux for infrastructure, Twelve Labs for search and understanding.
  • You want vertical versions of existing videos. Any of the clipping three will reframe, and OpusClip's reframing outputs 9:16, 1:1, 4:5, and 16:9.

One more decision sits underneath all of these: whether you want an agent driving the tools at all, or a pipeline you write yourself against the same capabilities. We put the two side by side in MCP versus API.

If you are building in code rather than through an agent, three companion roundups cover the other surfaces: the best video editing APIs for developers, the best CLI tools for video editing, and the best social media scheduling APIs.

Three patterns worth noticing

Hosted with OAuth has all but won. Nearly every serious server here is remote and authenticates through a sign-in flow, with API keys still common for headless use: Submagic outside the Claude connector, Shotstack in CI, and Replicate's remote server. Local stdio servers still make sense for developer context, but for agent distribution they are a dead end: too much install friction between "I want this" and "it works."

Publishing stopped being a differentiator this year. A year ago most video servers stopped at the export and left distribution to a second tool. Today all three clipping servers post and schedule from the agent, and two of them expose queue management. If a roundup still tells you posting is rare, check its date.

The new cut line is how deep the editing goes. Every server here can produce a video. Far fewer can change one after it exists. Metadata edits are common; section-level edits against a rendered clip, such as OpusClip's trim, split, reorder, and filler-word removal in one call, are not. That is where this category is competing next, because "the agent made something almost right" is the failure mode every one of these products actually has.

If clipping, editing, and publishing is the job you have, our setup guide gets the OpusClip server running, and the tool reference covers what each tool does.

Frequently asked questions

What is the best MCP server for video editing?

It depends on the job. For turning long recordings into short-form posts, the clipping layer (OpusClip, Reap, Submagic) is the right one, and all three now clip, caption, reframe, and publish from an agent. OpusClip's edit_clip tool handles section-level edits such as trims, splits, reorders, and filler-word removal, across 37 tools on its MCP server. Reap's site lists 30 tools and adds dubbing as a first-class tool. For programmatic composition from templates or data, Shotstack's server has 15 tools, including a real render toolset.

Which video MCP servers can post to social media?

All three in the clipping layer. OpusClip exposes posting, scheduling, queue listing, and unscheduling. Reap lists six publishing tools including listing and editing already-scheduled posts. Submagic publishes from an agent and adds published-post analytics. Agent Opus also lists posting and scheduling tools. Most rendering and infrastructure servers stop at the export.

Does Remotion have an MCP server that renders video?

No. Remotion shut down its hosted MCP server on October 26, 2026 and recommends Remotion Agent Skills (npx remotion skills add) for agents instead. Rendering runs through Remotion's own CLI and renderer packages, and for an agent-driven render server the closest fit in this list is Shotstack.

Are MCP servers for video hosted or do I install them locally?

The serious ones are hosted and remote, and nearly all use OAuth sign-in with nothing to install. Submagic uses a Bearer API key outside its Claude connector, and Replicate's remote server takes a Replicate API token. Local stdio servers still have a place in developer tooling, but install friction makes them a poor fit for agent distribution.

Creator name

Creator type

Team size

Channels

linkYouTubefacebookXTikTok

Pain point

Time to see positive ROI

About the creator

Don't miss these

How Audacy Drove 1B+ Views by Taking a Tech-Forward Approach to Radio with OpusClip
No items found.

How Audacy Drove 1B+ Views by Taking a Tech-Forward Approach to Radio with OpusClip

How All the Smoke makes hit compilations faster with OpusSearch

How All the Smoke makes hit compilations faster with OpusSearch

Growing a new channel to 1.5M views in 90 days without creating new videos

Growing a new channel to 1.5M views in 90 days without creating new videos

OpusClip 4.0 is here. Become a content powerhouse.

The 10 Best Video Editing MCP Servers in 2026

Three creators with a five-star rating, a list of servers, a Connect button and a YouTube Shorts badge
No items found.
No items found.

Boost your social media growth with OpusClip

Create and post one short video every day for your social media and grow faster.

The 10 Best Video Editing MCP Servers in 2026

Three creators with a five-star rating, a list of servers, a Connect button and a YouTube Shorts badge

"Video MCP server" now describes about six different jobs, and most roundups blur them together. A server that generates footage from a prompt, a server that renders JSON into an MP4, a server that indexes a video library for search, and a server that clips a podcast into shorts are not substitutes for each other. They are different layers of the same stack, and picking the wrong layer is the most common reason an agent workflow stalls halfway through.

So this is a map, sorted by what each server's tools actually do. How we compared these servers: we checked every endpoint, tool count, sign-in method and limit on November 3, 2026, against each vendor's own docs, repos and registry listings. We did not run hands-on tests of the other vendors' servers, tool counts change often, and the entries are specific enough (endpoints, named tools, stated limits) that each claim can be checked against the vendors' own pages. If the underlying concept is new, start here instead.

Clipping and repurposing: long video in, posts out

This is the most competitive layer in the stack and the one that changed most in the last year. All three servers below now clip, caption, reframe, and publish from an agent. The differences are in curation quality, how deep the editing goes, and what happens when the first result is not quite right.

OpusClip

Endpoint: https://mcp.opus.pro/mcp, hosted, OAuth sign-in with no API key. Tools: 37 on the MCP server (29 workflow tools plus 8 media tools). Claude.ai users add the Claude Connector instead, which carries the 29 workflow tools. Cursor, Cline, Claude Code, ChatGPT and Codex use the MCP server.

OpusClip takes a long video (from a URL or an upload link), finds the moments most likely to perform, and cuts clips with captions and AI reframing. Its project import accepts links from YouTube, Vimeo, Riverside, Loom, Zoom, StreamYard, Frame.io, Google Drive, and Dropbox, among others, so a recording goes straight from where it already lives into the workflow. Each clip carries a Virality Score from 0 to 99, built on hook, flow, and trend, and the server lists and describes clips per project.

The part that is genuinely uncommon is not the clipping: it is what happens after. edit_clip applies named operations to a rendered clip in one call: caption, emoji, and keyword-highlight toggles; filler-word and pause removal; section trim, split, drop, and reorder; phrase cutting; caption colour, position, and casing; clip dubbing (MCP server only); and undo. It re-renders the preview, and export_clip returns the HD download URL, because list and describe calls return preview URLs only. Of the clipping servers here, it is the one whose public tool list shows section-level edits against a rendered clip. We walk through the actual edits in the editing guide, and the tool reference goes through the tools one by one.

get_transcript returns paragraphs with start and end times and per-word timings, so an agent can find a phrase and compute an exact boundary. Posting, scheduling, queue listing, and unscheduling are all named tools (create_post_task, schedule_publish, list_scheduled_posts, unschedule_publish). OpusClip's Pro social scheduler supports YouTube, TikTok Feed, Instagram Reels, Facebook Page, LinkedIn, X (beta), Pinterest, Threads, and Bluesky. The media tools, MCP server only, add thumbnail, voiceover, music, and video generation, each quoted for free before it spends credits.

Limits worth knowing: API and MCP access are included on Pro (beta), Max, and Business plans (API keys come from the dashboard), and tool calls require one of those plans. Pro (beta) and Max get 15 hours or 900 credits per workspace per month with 4 concurrent projects; Business follows its contract. API projects have a 10-credit minimum. On the Claude Connector, posting, scheduling, unscheduling, and sharing return a link you confirm in OpusClip instead of committing, and dubbing and media generation are not available. OpusClip is listed in the Claude connector directory, the MCP Registry, Smithery, cursor.directory, and the Cline marketplace, and on npm as @opusclip/mcp.

Reap

Endpoint: https://mcp.reap.video/mcp, hosted, OAuth (API keys also accepted). Tools: 30.

The most direct alternative on the agent surface. Reap's site lists 30 tools across six categories: creating projects (upload URLs, clips, captions, transcription, reframe, dubbing), tracking and retrieving results, editing metadata, publishing, reference catalogs, and billing. Its docs say the server works on every plan, with one MCP connection on the Free plan.

Dubbing into 80+ languages is a first-class tool (dub_video) rather than a caption translation, which matters if your distribution is genuinely multilingual. Billing is also agent-accessible: an agent can check plan usage and get a checkout link for extra media credits, and admin keys can get a billing portal link, which is either convenient or alarming depending on your governance.

Its publishing surface is a full six tools, including listing and editing already-scheduled posts. If you read an older roundup saying Reap is API-only for posting, that is out of date.

Where it stops: its editing tools cover metadata (update_clip, update_video) and a hand-off to its web editor (open_in_editor) rather than the timeline. None of its listed tools trims or reorders sections of a rendered clip, so "trim four seconds off the front of clip 3" is a web-editor job rather than something an agent can do against the clip directly.

Submagic

Endpoint: https://api.submagic.co/mcp, hosted, Claude connector sign-in or Bearer API key. Tools: count not published.

Strong product with a sensibly chosen scope. Submagic's docs give example prompts rather than a tool list: creating a project from a URL, generating Magic Clips, checking project status, adding background music, listing caption templates, exporting, and publishing. It is also the only one of the three clipping servers whose docs describe published-post analytics, such as per-profile views, engagement, and publishing stats, so "which of last week's clips actually performed" is answerable in the same session that made them.

The notable difference is auth. Claude users connect through the Claude connector with a sign-in, but every other client passes an existing Submagic API key as a Bearer token, which means a key has to be generated from account settings, pasted, and stored somewhere. That is a small thing for a developer and a real barrier for everyone else, and the same key and credits serve both the REST API and MCP.

Where it stops: the public docs do not publish a definitive tool list, so we give no count, and its example prompts do not include timeline-level edits to a finished clip.

Generation: prompt in, footage out

Agent Opus

Endpoint: https://api.opus.pro/api/agent-mcp, hosted, OAuth (setup page at agent.opus.pro/mcp). Tools: 29.

The generation counterpart to the clipping server: text or a script in, a finished video out with AI voiceover, visual styles, and brand assets. Agent Opus's own documentation says video generation through MCP needs a Pro plan or above, while the whoami tool works on any plan so an agent can check access first.

The tool surface splits into project creation (prepare_project then start_project, with get_video to poll), a reusable asset library (logos, products, characters that can anchor any video), voice cloning and voice selection, visual style listing and customization, motion graphics, and posting and scheduling tools. Because both OpusClip and Agent Opus run as hosted MCP servers, an agent can have both connected and chain generate, clip, and schedule in one session.

Limits worth knowing: the help center lists generated videos of up to about 10 minutes in the script, audio, and song modes; voice cloning works from a sample of up to 30 seconds; and Free-plan downloads carry an Agent Opus watermark. Generation spends credits, and projects start only after a prepare step.

RunwayML

Endpoint: https://mcp.runwayml.com/mcp, hosted, sign in with a Runway account, no API key.

Strategically the most interesting server in the stack, because it is a menu rather than a dish. Through one connector, an agent can run generation on Runway's own Gen-4.5 and Gen-4 Turbo and on Kling 3.0, Google Veo 3.1, Seedance 2.5, GPT Image 2, and Nano Banana Pro, with the models available depending on the Runway account plan. Generations draw on Runway credits, the same as the Runway app. Runway runs a separate Dev MCP for API accounts; the generation server is this one.

That aggregation is worth thinking about as a pattern, not just a feature. Runway has made itself the surface through which its own competitors get called, which means an agent asking for "the best available model" reaches Runway first regardless of who wins the model race. If your workflow is "generate a shot," this is the widest single surface.

Replicate

Endpoint: mcp.replicate.com, hosted, authenticated with a Replicate API token through a web sign-in flow, with a local build (npx -y replicate-mcp) also available.

Search, compare, and run across Replicate's model catalog, which includes a text-to-video collection. Replicate's docs say the server supports all of the operations in its HTTP API, so an agent can search and compare models, fetch model metadata, run predictions, and fetch their results. An experimental Code mode, local only, swaps the per-operation tools for two tools: one for searching SDK docs and one for running TypeScript in a sandbox.

The tradeoff against Runway is control versus curation. Replicate gives you a far larger catalog and expects you to know which model you want; Runway gives you a shortlist someone has already vetted. Pick Replicate when model choice is the point.

Avatar and voice

HeyGen

Endpoint: https://mcp.heygen.com/mcp/v1/, hosted, OAuth. Tools: 98 listed in its docs.

The largest documented tool surface in this roundup. The tools span a video agent, avatar videos, templates, voices, audio search, video translation, lip sync, avatars, assets, brand, batches of up to 100, and, new since this post first ran, AI clipping (create_ai_clipping and three companion tools) and filler-word removal. Its docs say usage draws on the credits in an existing HeyGen plan, on every plan.

Directory presence is the more important lesson. HeyGen is in the Cursor marketplace, and Runway is in the ChatGPT plugin directory. OpusClip lists itself in the Claude connector directory, the MCP Registry, Smithery, cursor.directory, and the Cline marketplace, and Twelve Labs has an MCP Registry entry. Registry and store presence is how agent users find a server without someone pasting a URL.

One detail: HeyGen's docs cap HeyGen Video generation through MCP at 5 to 15 seconds, and point to the HTTP API for longer clips. The video agent and avatar video tools are separate from that limit.

Editing and rendering: programmatic composition

Shotstack

Endpoint: https://mcp.shotstack.io/, hosted, OAuth or an x-api-key header, with an mcp-remote bridge for stdio-only clients. Tools: 15.

The real render toolset in this category: an inline Studio canvas, direct render, render status, shareable Studio links, a guide tool for the edit format, six template tools (create, update, list, get, render, delete), and generation tools (list models, quote a price, generate an asset, check status). This is the server to reach for when video is assembled from data rather than captured, such as a personalized video per customer record or a weekly report rendered from a spreadsheet.

Client support is unusually broad: claude.ai, Claude Desktop, Claude Code, ChatGPT, Cursor, VS Code, Codex CLI, Gemini CLI, Windsurf, Zed, JetBrains, Goose, Raycast. Flagged as beta, so expect the tool surface to move.

One correction for anyone who found an older version of this list: Remotion, the open-source programmatic-video framework, shut down its hosted MCP server on October 26, 2026 and now points developers to Remotion Agent Skills (npx remotion skills add). Rendering itself still runs through Remotion's own CLI and renderer packages, not through an MCP server.

Infrastructure and understanding

Mux

Endpoint: https://mcp.mux.com, hosted, OAuth through the Mux dashboard (Basic token credentials for clients without OAuth). Tools: 2.

The infrastructure layer: Mux Video assets, direct uploads, playback IDs and live streams, Mux Data metrics and real-time dimensions, and Mux Robots jobs. Mux's docs say it is built on a Code Mode scheme with just two tools: search_docs for its API docs and execute, where the agent writes TypeScript against the full Mux SDK in an isolated sandbox.

The design is the interesting part. Instead of hundreds of endpoint tools, the agent gets two, which keeps the model's context small and makes multi-step tasks repeatable. That is a pattern worth copying, because agents make better choices with smaller tool lists, and a 40-tool server that dumps everything into context makes the model worse at picking. Mux's docs note that it does not treat destructive operations specially, so a read-only access token is the safe way to connect.

Twelve Labs

Endpoint: https://mcp.twelvelabs.io/jockey/mcp, hosted, OAuth with a TwelveLabs account.

Cross-video understanding through its Jockey agent: build a collection of videos and images, search across it, ask questions, and get text answers that cite the exact clips they draw from, with multi-turn refinement. This is the layer you want when the question is "find every moment in our 400-hour archive where someone mentions pricing" rather than "make me a video." TwelveLabs also lists a separate MCP Registry entry at mcp.twelvelabs.io that takes an API key header.

It pairs naturally with the clipping layer rather than competing with it. Twelve Labs finds the moment across a library; a clipping server turns that moment into something postable.

How to actually choose

Sort by the job, not the brand:

  • You have long recordings and need posts. Clipping layer: OpusClip, Reap, or Submagic. All three publish from the agent now, so decide on curation quality, how deep post-clip editing goes (OpusClip's edit_clip covers section-level edits and dubbing, while Reap's edit tools cover metadata plus a web-editor hand-off), whether you need Reap's 80+ language dubbing, and whether OAuth versus an API key matters to whoever is installing it.
  • You need footage that doesn't exist. Generation layer: Runway for model breadth, Replicate for catalog size, Agent Opus for script-to-finished-video.
  • You need a presenter without filming one. HeyGen, on its hosted server.
  • You're composing video from data or templates. Shotstack for a real render toolset; Remotion users now install Agent Skills instead of an MCP server.
  • You're building a product on top of video. Mux for infrastructure, Twelve Labs for search and understanding.
  • You want vertical versions of existing videos. Any of the clipping three will reframe, and OpusClip's reframing outputs 9:16, 1:1, 4:5, and 16:9.

One more decision sits underneath all of these: whether you want an agent driving the tools at all, or a pipeline you write yourself against the same capabilities. We put the two side by side in MCP versus API.

If you are building in code rather than through an agent, three companion roundups cover the other surfaces: the best video editing APIs for developers, the best CLI tools for video editing, and the best social media scheduling APIs.

Three patterns worth noticing

Hosted with OAuth has all but won. Nearly every serious server here is remote and authenticates through a sign-in flow, with API keys still common for headless use: Submagic outside the Claude connector, Shotstack in CI, and Replicate's remote server. Local stdio servers still make sense for developer context, but for agent distribution they are a dead end: too much install friction between "I want this" and "it works."

Publishing stopped being a differentiator this year. A year ago most video servers stopped at the export and left distribution to a second tool. Today all three clipping servers post and schedule from the agent, and two of them expose queue management. If a roundup still tells you posting is rare, check its date.

The new cut line is how deep the editing goes. Every server here can produce a video. Far fewer can change one after it exists. Metadata edits are common; section-level edits against a rendered clip, such as OpusClip's trim, split, reorder, and filler-word removal in one call, are not. That is where this category is competing next, because "the agent made something almost right" is the failure mode every one of these products actually has.

If clipping, editing, and publishing is the job you have, our setup guide gets the OpusClip server running, and the tool reference covers what each tool does.

Frequently asked questions

What is the best MCP server for video editing?

It depends on the job. For turning long recordings into short-form posts, the clipping layer (OpusClip, Reap, Submagic) is the right one, and all three now clip, caption, reframe, and publish from an agent. OpusClip's edit_clip tool handles section-level edits such as trims, splits, reorders, and filler-word removal, across 37 tools on its MCP server. Reap's site lists 30 tools and adds dubbing as a first-class tool. For programmatic composition from templates or data, Shotstack's server has 15 tools, including a real render toolset.

Which video MCP servers can post to social media?

All three in the clipping layer. OpusClip exposes posting, scheduling, queue listing, and unscheduling. Reap lists six publishing tools including listing and editing already-scheduled posts. Submagic publishes from an agent and adds published-post analytics. Agent Opus also lists posting and scheduling tools. Most rendering and infrastructure servers stop at the export.

Does Remotion have an MCP server that renders video?

No. Remotion shut down its hosted MCP server on October 26, 2026 and recommends Remotion Agent Skills (npx remotion skills add) for agents instead. Rendering runs through Remotion's own CLI and renderer packages, and for an agent-driven render server the closest fit in this list is Shotstack.

Are MCP servers for video hosted or do I install them locally?

The serious ones are hosted and remote, and nearly all use OAuth sign-in with nothing to install. Submagic uses a Bearer API key outside its Claude connector, and Replicate's remote server takes a Replicate API token. Local stdio servers still have a place in developer tooling, but install friction makes them a poor fit for agent distribution.

Ready to start streaming differently?

Opus is completely FREE for one year for all private beta users. You can get access to all our premium features during this period. We also offer free support for production, studio design, and content repurposing to help you grow.
Join the beta
Limited spots remaining

Try OPUS today

Try Opus Studio

Make your live stream your Magnum Opus