01
Get an API key
Sign in, open Settings → API keys and create a key. It starts with os_ and is shown once, so store it like a password. A key acts as your account: anything it starts uses your minutes, and deleting the key stops it at once.
02
Use it from Claude, Cursor or any MCP client
Claude Code adds the server with one command. Replace the key with your own.
$ claude mcp add --transport http openshorts https://openshorts.io/api/mcp --header "Authorization: Bearer os_your_key"In Cursor, add it to .cursor/mcp.json (or the global MCP settings):
{ "mcpServers": { "openshorts": { "url": "https://openshorts.io/api/mcp", "headers": { "Authorization": "Bearer os_your_key" } } }}Clients that only speak stdio, such as Claude Desktop, can reach it through the mcp-remote bridge:
$ npx mcp-remote https://openshorts.io/api/mcp --header "Authorization: Bearer os_your_key"03
Tools
| Tool | What it does | Arguments |
|---|---|---|
clip_video | Starts a job for one YouTube video. Returns a job id. | url; caption_style (optional) |
get_job | Status and progress. When done: each clip’s title, score, reason, hook line, TikTok and Instagram captions, and download links valid for one hour. | job_id |
list_jobs | Your most recent jobs, newest first. | limit (1–30) |
get_usage | Plan, minutes left this month and minutes left in packs. | — |
Caption styles: default (big uppercase, coral active word), hormozi (words appear as they are spoken), pill (solid box behind the active word), lime (bright green active word box), oneword (one big word at a time), clean (sentence case, soft shadow).
04
A typical run
Ask your assistant something like “clip this podcast into Shorts with pill captions” and paste the link. It calls clip_video, gets a job id, and checks back with get_job. Processing usually takes 10 to 20 minutes for a typical video; the job page on the site shows the same job live.
When the status is done, the assistant has every clip with its score and reason, so it can pick the strongest, download it, and draft the post from the suggested captions.
05
Minutes and limits
API jobs follow your plan, exactly like jobs started in the browser: the same monthly minutes, video length limit, watermark rule and number of videos processing at once. When the monthly minutes run out, minutes from a pack are used next; see pricing.
Each key may make up to 120 requests a minute, which leaves plenty of room for polling a job every few seconds.
06
Hosted or self-hosted
The open source build ships its own MCP server, REST API and CLI, unmetered and without a key, if you run it on your own machine. The self-host guide covers that setup. The hosted server here needs no install and no GPU.
07
API questions
Is there an OpenShorts API?
Yes. OpenShorts.io runs a hosted MCP server at /api/mcp. Create a personal API key in your account settings and any MCP client can submit videos and collect the clips.
What does a video clipping API call cost?
Calls are free; clipping uses minutes from your plan, measured on the length of the source video. A 30-minute video uses 30 minutes. If processing fails, the minutes are returned.
Does it work with Claude Desktop?
Claude Desktop connects to remote servers through a bridge that can send a header, such as mcp-remote. Claude Code and Cursor send the header directly.
Can I upload a file through the API?
Not yet. The hosted tools take YouTube links. To clip a local file, upload it in the workspace, or run the open source build, whose API accepts uploads.
Is this an alternative to the Opus Clip API?
It covers the same core job, turning one long video into captioned vertical clips, through MCP tools with a personal key and no sales call. Compare the outputs on your own footage before you switch.