Which video editing MCP server is best?

Choose against a concrete delivery brief. Compare the source inputs, required repairs, account access and final handoff. This guide reviews selected documented workflows and does not claim a completed quality or speed benchmark.

Does a larger tool count mean a better editor?

No. A single tool can accept many operations, while another server exposes each operation separately. Catalogs can also depend on configuration and account access. Inspect the required operation and test its result.

Can Valmera MCP return a final exported video?

Valmera MCP supports editing and preview review, but final-export creation remains in Studio. Plan for that handoff when the deliverable is a finished MP4.

Does the Resolve integration require Studio?

The named integration documents direct external scripting for Studio and an in-app bridge for the Free edition. Verify your version and requested operation; this guide did not install or execute that bridge.

Does a locally launched MCP server keep everything offline?

No. The Video Jungle connector runs locally but calls its hosted API. Check the implementation and optional services before assuming media processing stays on your computer.

Will any MCP client work with every server?

Verify the particular client and connector: transport, authentication, organization settings, tool exposure and result handling all matter. Successful discovery is a useful first check, followed by a small end-to-end delivery test.

Are Runway generation MCP and Runway Dev the same connection?

No. The generation connection uses a Runway app account to create media. Runway Dev uses a Developer Portal account for tasks, model routers and documentation. Their server URLs and purposes differ.

Can Riverside MCP export and schedule videos?

Its setup guide documents exports and social scheduling, with gradual beta access on eligible plans. Social accounts must first be connected in Riverside; recording-session scheduling stays in the app.

Why does one Rendley connector prepare a project but not edit it?

Rendley documents two endpoints. /mcp prepares a project and brief that a user must open and submit. /mcp/automation can run the editing workflow and export. They use separate OAuth connections, and editing/export access requires a paid Rendley plan. Check the exact configured URL before assuming a successful connection can finish the video.

Can Rendley MCP use a video attached to an AI chat?

It depends on the client. The attachment must be exposed through a usable download reference or an environment that can read its bytes. Otherwise, Rendley documents direct HTTPS media links or existing Studio project media as alternatives. A file in the project library still needs placement instructions.

Originally published August 4, 2026 · Updated September 9, 2026

Video Editing MCP Servers: 9 Workflows Compared

A video editing MCP server exposes video-related operations as tools an AI assistant can discover and call. The available operations may cover media search, editing, previews, rendering or publishing; a connection alone does not guarantee a finished video.

Start with the output you need. Editing an uploaded recording, preparing a Resolve timeline and publishing a captioned clip have different dependencies and finish lines.

Valmera publishes this comparison and sells one of the products included. The first six records retain their September 8 source-review dates; Runway, Riverside and Rendley were reviewed using official guides on September 9. We did not authenticate to every service, install the local integrations or run a comparative editing benchmark. This is a selection of 9 workflows, not an exhaustive directory.

Compare the connection and the finish line

Documented workflows and delivery boundaries; unordered
Integration and source	Connection	Documented work	Delivery boundary
ValmeraSource reviewed 2026-09-08	Hosted HTTP; OAuth or a minted bearer token.	Project and media tools, timeline edits, previews and visual review.	Final MP4 creation is in Studio; MCP does not initiate that export.
DescriptSource reviewed 2026-09-08	Hosted connector; Descript login, scoped to one Drive.	Imports, Underlord edits, project management and composition targeting.	MCP rendered-file URLs require web-link publishing; direct local export is in the app.
ReapSource reviewed 2026-09-08	Hosted; setup guide requires OAuth and a paid plan with API access.	Clips, captions, reframing, dubbing, transcription and job results.	Documents publishing and scheduling to connected social accounts.
OpenClipSource reviewed 2026-09-08	Hosted HTTP; OAuth with dynamic client registration.	Submission, clips, render status, transcripts and media utilities.	Follow the render operation and inspect the returned clip; check separate publishing support.
Video JungleSource reviewed 2026-09-08	Locally launched Python connector; Video Jungle account and API key.	Search hosted video analysis, assemble edits and prepare local timeline handoff.	Inspect the returned project or edit link; local handoff needs its own finishing path.
Samuel Gursky’s DaVinci Resolve MCPSource reviewed 2026-09-08	Local integration; Studio scripting or the documented Free-edition bridge.	Live Resolve project, timeline, color and render operations.	Check the installed edition, exposed operation, render job and output file.
Runway generation MCPSource reviewed 2026-09-09	Hosted Streamable HTTP; sign in with a Runway app account, without an API key.	Generate images and video using eligible models and account credits; Explore Mode is excluded.	Inspect the generated asset. The connection guide does not establish access to every Agent timeline operation.
RiversideSource reviewed 2026-09-09	Hosted HTTP with sign-in; gradual beta for Grow, Webinar and Business plans.	Search transcripts, create edits and clips, export edits, and publish or schedule social posts.	New edits remain editable; exported files appear in the exports folder. Connect social accounts in the Riverside dashboard first.
Rendley automationSource reviewed 2026-09-09	Hosted HTTP; OAuth or API key. Editing and export require a paid plan.	Cloud editing agent, project media, optional generation, motion graphics and rendering.	Editable project and temporary MP4 or WebM download. The lighter /mcp connector prepares a draft only.

Download the 9 comparison records as JSON. The download preserves each review date, primary source and delivery boundary. Records describe documentation evidence, not successful authenticated tests.

For clipping, inspect selection and correction controls. For desktop finishing, inspect timeline handoff and render operations. For distribution, inspect the publishing tools and destination accounts. A product can serve more than one of these jobs.

Requirements that change the choice

Descript: choose the Drive and delivery route

Its MCP guidance excludes YouTube URLs as import sources and supports transcript exports including SRT. Signed MP4 or audio URLs come through Descript web-link publishing; a private local-file export without publishing is an app step. The directory connector and custom setup can expose different generative tools. Descript MCP overview.

Reap: use the action server and current setup guide

The documented video-action endpoint is https://mcp.reap.video/mcp. Its connection guide specifies OAuth, a selected workspace and a paid plan with API access. The marketing page still describes API keys and free processing, so these public instructions differ. Confirm eligibility against the setup guide and your account.

The separate documentation MCP exposes documentation search and retrieval, not video processing. Reap also documents publishing and scheduling through connected social accounts.

OpenClip: trace submission through rendering

The published catalog names submit_video, list_clips, render_clip and get_render_status, alongside uploads and media tools. This is a useful sequence to investigate, not a record of our own completed render. Its product documentation also covers caption edits, trims and filler-word removal. Verify which controls and publishing actions your connection exposes. OpenClip MCP catalog.

Video Jungle: local launch, hosted dependency

The reviewed Python package requires Python 3.11 or later and a Video Jungle API key. Its source calls the hosted Video Jungle API; generated-edit handlers return project/edit links. The README describes OpenTimelineIO handoff and a local Resolve Studio workflow. Treat that handoff as a project to finish, not evidence of a checked final encode. Pinned README; reviewed implementation.

DaVinci Resolve: identify the implementation and mode

This comparison covers Samuel Gursky’s integration, not every project named Resolve MCP. Its live Python server uses Resolve scripting. The README also documents a separate optional Node server for offline project-file operations. That does not make every live editing or rendering operation available without Resolve. Check the edition, operating system, scripting connection and optional analysis dependencies. Pinned integration documentation.

Runway: distinguish generation, developer tools and the web editor

The generation connection uses https://mcp.runwayml.com/mcp, Runway app sign-in and Streamable HTTP. Generation consumes credits; Explore Mode is unavailable through this connection. Model access depends on the account.

Runway Dev is a separate Developer Portal connection at https://dev.runwayml.com/mcp, covering task lookup, model routers and documentation. The Runway Agent guide describes uploaded footage, timeline assembly and rendering inside Runway. Those app features alone do not establish which timeline operations an external MCP client can call.

Riverside: check rollout, role and delivery

Its setup guide lists https://mcp.riverside.com/mcp and gradual beta access on Grow, Webinar and Business plans for owners, admins, directors and editors. Edits create a new version; exports go to the exports folder. Scheduling recording sessions and managing podcast hosting remain in Riverside.

The product page describes broad assistant compatibility. The setup guide asks users of other clients to contact support and lists client-specific restrictions. Verify your client, role and rollout access before planning automated delivery.

Rendley: preparation and automation are different connectors

The automation endpoint, https://mcp.rendley.com/mcp/automation, uses Rendley's editing agent to work on media, save an editable project and render an output. The lighter directory connector, https://mcp.rendley.com/mcp, prepares a project and brief. A user must open that draft and submit it before editing begins. Its temporary uploads normally expire after 24 hours unless the prepared project is submitted.

The authentication guide documents OAuth or an API key. OAuth connections are separate for the two endpoints. Free accounts can connect and inspect account/project information; editing and export require a paid plan. Some generic client examples point to the lighter endpoint, so check the configured URL against the workflow you need.

For local files, the client needs access to the bytes and uploads them directly to storage. Rendley documents multipart handling, up to 50 files per upload batch and up to 20 new files per edit request. Chat attachments work only when the client exposes a usable reference or file environment. Direct HTTPS media URLs and existing project media are alternatives. Library upload alone does not place an asset on the timeline.

An automation run can pause for a plan, a creative choice or work that uses credits. Replies continue the same run; clients supporting MCP elicitation may show a form. The documentation warns that opening Studio during an active or paused edit can take over the session. Cancellation stops later steps while preserving changes already saved.

The automation guide lists H.264 MP4 and VP8 WebM, with requested resolutions through 4K. Download links expire after a few hours. Generation, transformations and rendering may use credits, so inspect the proposed work and the actual output. This is documented delivery support, not our own completed Rendley export.

On September 9, both endpoints returned authentication challenges to unauthenticated requests. Their public resource metadata identified Rendley MCP Automation and Rendley MCP separately. That verifies public endpoint identity and advertised authentication; it does not verify a tool catalog, account entitlement or editing result.

Tool count is not an editing benchmark

In the September 8 source review, Valmera’s public server card reported 134 tools. The pinned Resolve README described 36 compound tools or 353 granular tools depending on its entry mode. Those dated figures describe different packaging and are not comparable measures of editing quality.

Three levels of evidence
Evidence	What it establishes	What remains unproved
Documentation or source review	A published operation, requirement or implementation is present.	That the operation is available in your account or succeeds on your footage.
Authenticated tool discovery	Your selected connection exposes particular tools and input schemas.	That the requested edit, render or upload will succeed.
Completed delivery test	A specific job produced a file or destination you inspected.	General quality, speed, reliability or audience performance across other work.

For an actual connection, follow tools/list pagination and inspect input schemas. Check tool-level errors as well as any separately returned media-job status. Tool annotations are hints whose trust depends on their source. The cited MCP tools specification is the July 28, 2026 revision; use the version your client and server support. These checks do not guarantee successful delivery.

Test one workflow from source to delivery

1
Write one delivery brief
Match the brief to the workflow. For source editing, request a 45–60 second clip with accurate captions, an intact qualification and a specified frame shape. For generation, specify a model-supported shot and reference assets you may use. Define the required file, editable project or destination.
2
Check the actual connection
Record the client, server version or review date, account, workspace and plan. Discover the authenticated tools and inspect their required inputs. Confirm source upload or URL support before starting paid processing.
3
Keep identifiers and job state
Record the source, project, edit version, tool call and any returned job identifier. Follow the documented status operation to completion or failure. After a timeout, check the existing job before resubmitting work that could create duplicates or charges.
4
Request two precise repairs
For source editing, restore the required qualification and correct the chosen name. For a generated shot, revise two concrete details such as composition and motion. Inspect the changes and record whether the assistant completed them, regenerated the asset or needed a manual editor step.
5
Finish the requested handoff
Complete the separate render, download or publishing step where required. Match the output to the accepted edit and play the saved file from beginning to end. Check duration, dimensions, caption timing, audio and branding.
6
Report the observed result
Record hands-on time, elapsed time, failed attempts, actual usage charges and manual steps. Mark unavailable operations separately from failed ones. A successful small trial supports that tested workflow; it does not establish an overall winner.

This is a proposed evaluation, with no fabricated result or winner. For a clipping brief, use the review method and blank clipping worksheet to keep the editorial record.

Where Valmera fits

Use Valmera when you want an assistant to work on uploaded footage through explicit project, editing and preview tools. Check the tool reference and connection notes for the current workflow. Public catalog metadata is not certification of every client or account.

Account creation and uploads are free; indexing and agent editing require a subscription and use credits. Finish the accepted edit with a Studio MP4 export, which re-encodes source media. Valmera does not provide SRT/VTT or editable XML handoff, social scheduling, or final-export creation through MCP. See delivery documentation and current plans.

Explore Valmera’s editing workflow

Check account access, project tools, preview review and the Studio handoff before choosing your connection.

View Valmera MCP

See pricing →