Video editing MCP server
Valmera lets an authorized assistant edit uploaded footage through MCP. Describe the changes, let the assistant inspect the source and call supported tools, then review the rendered preview. Create the final MP4 in Valmera Studio.
Use this page to understand the workflow and its limits. The Claude setup guide covers connection steps; the tool reference covers the advertised operations.
Remote MCP endpoint
https://entrepreneur-bot-backend.onrender.com/mcpStreamable HTTP · OAuth discovery · Dynamic client registration · S256 PKCE. The public server card describes the service. It is not a connection test for your account.
Check access before planning the integration
You need a compatible MCP client and a verified Valmera account with an active Pro or Frontier subscription. MCP access is included automatically for Pro and Frontier subscribers. Creator does not include MCP access.
The public shopfront says account creation and uploads are free and editing requires a subscription. Your assistant provider’s plan is separate. Confirm the current Valmera terms and MCP access before purchasing specifically for this integration.
What each part of the workflow does
| Part | Responsibility | Evidence to check |
|---|---|---|
| Your assistant | Interpret the brief, inspect source evidence and choose supported operations | The intended project, source ranges and tool arguments |
| Valmera MCP tools | Read or change project state and start supported review work | Returned project identity, version, status and errors |
| Your MCP client | Authorize the connection, transfer files when needed and present results | Whether the actual preview, frames or download are available |
| Valmera Studio | Open the reviewed project and create its final export | The downloaded MP4, complete runtime, sound, picture and branding |
Source upload bytes go to the destination returned by the upload workflow. Calling an upload tool is not the same as transferring the file. After upload completion, wait for indexing before relying on a transcript or other analysis.
See an actual source-to-export result
Our trim-and-reframe example starts with a 25-second original silent motion graphic. The connected assistant kept three four-second source ranges and selected a centered square crop. Valmera rendered a 12-second review preview; Studio created a 17-second final including the observed five-second end card.
The page supplies both files, the implemented brief and a source-to-output timing table. The export has a small overlaid Valmera mark. This demonstrates one simple cut and crop; it does not establish speech accuracy, client-wide compatibility, typical price or render speed.
Supported editing jobs and useful checks
| Job | Representative tools | Review after the call |
|---|---|---|
| Choose or shorten footage | get_video_info, get_edl, cut_range, keep_segments | Keep the intended meaning and inspect the changed joins. Source seconds and output seconds differ. |
| Add or correct captions | add_captions, set_caption_fixes, set_caption_style | Check spelling, highlight timing, placement and the rendered result. |
| Change the output shape | set_frame, auto_reframe | Confirm what is cropped or padded and whether useful content remains visible. |
| Add media or adjust sound | list_assets, insert_media, add_music, set_volume | Confirm the actual asset, usage rights, placement and audible mix. |
| Review and hand off | render_preview, watch_video, download_url | Confirm the current version and inspect the media the client actually received. |
The current session’s tool schemas determine accepted arguments. Optional acquisition, generation or repair tools should be evaluated from that session’s returned results. A listed name does not guarantee configured services, a usable license, clean reconstruction or successful rendering.
Keep project, version and job state explicit
Copy the project ID from a returned project record. Pass it to project-scoped calls and confirm that each result names the intended project. Opening a project is useful navigation; it should not substitute for an explicit project identifier when the tool requires one.
Read the current edit before a broad restructuring. Local fixes should preserve existing choices where possible. After a change, inspect the returned version and assembled program rather than assuming a previously downloaded preview has updated.
Long work can return a job ID. Follow that job with wait_for_job until its returned state resolves the operation. An observation timeout alone is not a failure or a reason to launch the same edit again. If work is refused because another edit is active, inspect the existing operation before retrying.
Version history and busy-state checks support recovery and coordination. They do not guarantee that every request succeeds or that an assistant’s description matches the pixels. Check the actual returned evidence and final file.
Delivery boundaries
MCP can request review renders and retrieve existing media. It cannot start the public contract’s final-export operation or delegate the edit to Valmera’s in-house agent. Open the reviewed project in Studio to create the final MP4.
The public contract also excludes SRT/VTT import or export, direct social publishing, team collaboration, custom font uploads and AI music generation. Review the current server card and delivery guide for the full boundaries. Preview and final output can differ in resolution, encoding and branding.
Frequently Asked Questions
Connect an eligible account
Follow the setup guide, confirm your project and tools, then begin with a small edit you can inspect.
Read the Claude setup guide →