Connected workflows
Can I edit my own videos with Claude and Shorty?
Shorty provides a remote MCP connector that lets a compatible client such as Claude request edits of your own footage. Connect the Shorty endpoint with OAuth, supply clips and a brief, and request a render. Shorty processes and renders the video; the chat is where you direct the workflow.
In this guide
Understand what the connector does
A conversation can help you decide the story, but a usable video requires an editing and rendering service. Shorty supplies that service through Model Context Protocol. Its documented endpoint is https://mcp.shortyedit.com/mcp and uses Streamable HTTP with OAuth. Client access and connector availability depend on the client and account. Follow the maintained connection documentation linked below.
Start with a narrow, reviewable edit
Use a small set of clips you own and a concrete objective. For example: “Make a vertical product demonstration from these clips. Show the result first, then the action that produces it. Preserve spoken facts and keep the product visible.” An optional reference supplies visual direction. Shorty uses your footage for the new video rather than generating replacement scenes.
Follow the documented tool workflow
The optional choose_reference tool provides a reference. The add_footage tool supplies your source clips and can create a project when no reference was selected. The render tool runs the edit and produces an MP4. If the connection drops, use status to inspect the existing run before starting a duplicate. The documentation also describes a director mode for clients that author and preview a composition.
Check material, credits and permissions
Use local files or supported direct media URLs according to the client’s capabilities. A social platform page is not a direct media file. Uploaded media is stored privately to the account, and service providers process material as described in the privacy policy. Connecting and rendering are separate actions: edits and renders consume credits, and the paywall tool reports the current balance and pricing.
Review before sharing
Ask for the finished result, watch the whole cut and compare it with the brief. Confirm captions, visual accuracy and soundtrack rights. An MCP endpoint does not by itself imply approval or listing in any assistant’s public directory. If you are evaluating whether Shorty is available to your account, use the actual connector settings and current documentation rather than assuming every chatbot can render videos.
Explore the details
Questions, answered
What is the Shorty MCP endpoint?
The documented remote endpoint is https://mcp.shortyedit.com/mcp. It uses Streamable HTTP and OAuth sign-in.
Does Claude itself render the MP4?
Shorty handles the video processing and rendering. The connected assistant directs the workflow through Shorty’s tools.
Can every chatbot use this endpoint?
No. The client must support the required MCP transport and authorization, and account access may vary. Use the maintained connection instructions.
What if a render disconnects?
Use the status tool to inspect the existing durable run and retrieve its result before starting a new edit.
Product sources and editorial notes
This guide is published by Shorty’s operator. Product details are based on the product overview, maintained documentation and current pricing. Comparison guides link to official competitor sources and explain when another workflow fits better. Client availability and prices can change.