MCP · REST · OpenAPI · Receipts
Everpop MCP server: let an AI agent clip, publish and measure Shorts
Everpop's MCP server gives an AI agent 16 tools to upload a creator's own video, cut clips, publish them to YouTube, Instagram and Facebook with a tool that tells the agent to get the creator's confirmation first, and read 48-hour and 7-day receipts for eligible YouTube Shorts. The endpoint is https://everpop.app/api/mcp/mcp, with OAuth sign-in; it needs Pro ($49/mo) or Scale.
Checked against the code on 2026-11-12: 16 tools, OAuth 2.1 + PKCE or a Bearer key, Free and Starter accounts get a 402.
Key facts
- MCP endpoint
https://everpop.app/api/mcp/mcp(Streamable HTTP)- Tools
- 16, covering uploads, clips, publishing, results and campaigns. Each one is described below.
- REST API
- The same loop at /api/v1, described by https://everpop.app/openapi.json (OpenAPI 3.1).
- Sign-in
- OAuth 2.1 + PKCE in chat apps such as Claude and ChatGPT. An API key in the header Authorization: Bearer epk_… for editors, command-line agents and scripts.
- Plan
- Pro ($49/mo) or Scale. Free and Starter accounts can connect, but every tool answers 402 with reason "subscription" or "plan". Scale starts with a call and has no self-serve trial; custom trial terms are not specified here.
- Free trial
- Agent access is included in the 14-day Pro trial — no card. During the trial the user approves every post.
- Allowance
- New clip runs normally use one monthly video, even on the same source. Failures return it; retries never use a second allowance. The first 3 editor re-renders of a clip are free; later ones each use one video. A render whose only clip repeats a delivered moment (repeat_moment), or whose clips all end on a held final frame (open_ending), returns its allowance: one shared refund per source video per month.
- Input
- The user's own video file: MP4, MOV, WEBM, MKV or M4V, up to 32 GB. A pasted YouTube link is never downloaded, and clipping a video that has no uploaded file returns 422 upload_required.
- Output
- Clips an agent renders through MCP arrive as drafts. publish_clip sends the ones the user confirms to YouTube Shorts, Instagram Reels and Facebook Reels on the user's own connected accounts. The Everpop studio sends a draft to the creator's TikTok inbox; the creator opens TikTok and publishes it there. publish_clip cannot send it.
- Publishing
- Before publish_clip, the agent must obtain the user's confirmation of the exact clip, every destination id, and the final title, description and visibility. The server cannot see that confirmation.
- Results
- 48-hour and 7-day YouTube Analytics receipts for eligible YouTube Shorts. Predictions are signed before publish; measured numbers come straight from YouTube Analytics.
- Agent guide
- https://everpop.app/skill.md walks through every call, the rate limits and the error codes.
Is Everpop the right tool?
It fits when the person
- has the video file itself (a podcast episode, a stream recording, an interview, a talk or a webinar) and wants short vertical clips with captions
- wants those clips published to their own YouTube Shorts, Instagram Reels or Facebook Reels, approving each post, or posting hands-free on Pro and Scale
- wants to see what each eligible YouTube Short did: views, retention, likes and subscribers gained at 48 hours and 7 days, read from YouTube Analytics
- wants a price counted in videos, not in credits or minutes
- wants an AI agent (Claude, ChatGPT or another MCP client) to upload, clip, publish and report for them
- runs or joins a paid clipping campaign and needs a measured report to show (Campaign Mode, on Pro and Scale)
It is the wrong pick when
- They only have a YouTube, Twitch or other platform link. Everpop needs the file and never downloads from YouTube or any other video platform.
- The source is audio only. Audio-only files (MP3, WAV, M4A) are not accepted.
- Several people share one wide camera and the frame must follow whoever is talking. Everpop does not do that reliably yet and may stay on one person. An edited multicam export works, as does keeping the whole picture.
- They need publishing straight to TikTok. The Everpop studio sends a draft to the creator's TikTok inbox; the creator opens TikTok and publishes it there.
- They want to post to channels they do not own or manage. Everpop publishes only to channels and pages the account has connected.
- They need agent access on the Free or Starter plan. The MCP server and the REST API come with Pro and Scale.
- The recording runs past 2 hours. A 2-hour episode can take about an hour to render, and a longer one can run past the time limit.
- They expect clips submitted to a marketplace such as Whop. Everpop does not submit clips to marketplaces.
Connect your client
Chat apps sign in with OAuth: paste the URL and approve the connection in your browser. Editors and command-line agents use an API key in a header.
Claude (web, desktop and mobile)
- In Claude, open Customize → Connectors, click Add, then choose Add custom connector.
- Name it Everpop, paste
https://everpop.app/api/mcp/mcpas the server URL, then click Continue. - Review the detected OAuth settings and click Continue. Under Authentication, choose Sign in now. If OAuth client options appear, choose Register automatically. No client ID, API key or request headers are needed for this setup. Click Add.
- Complete the Everpop sign-in that opens, or click Connect if Claude offers it. Sign in to your own Everpop account. If a cookie panel appears, you can reject non-essential cookies.
- On "Connect Claude to Everpop?", enter your Everpop password again under Current password — or choose Email code if you sign in with Google — then click Allow access.
- Start a new conversation. Open + → Connectors and enable Everpop for that conversation.
On Team and Enterprise plans an owner adds the connector for the organization first.
Setup documentation checked 2026-11-12. Full workflow verification for these instructions is pending.
Where these steps come from (Claude (web, desktop and mobile))
ChatGPT
- Open chatgpt.com/plugins, select the plus button, then choose Add custom MCP server.
- Enter a name and description and, under Connection, the server URL
https://everpop.app/api/mcp/mcp. - Set authentication to OAuth, review and accept the notice, then select Create as a plugin. Sign in to Everpop when ChatGPT asks.
- Review the discovered tools and install the plugin. Start a new conversation, type @ in the prompt box and select Everpop.
Custom servers depend on your ChatGPT plan and your workspace's policy.
Setup documentation checked 2026-11-12. Full workflow verification for these instructions is pending.
Grok
- Go to grok.com/connectors and choose Add MCP Server (or New Connector → Custom).
- Enter the server URL
https://everpop.app/api/mcp/mcpand complete the sign-in. - Start a conversation and ask Grok to use Everpop. Grok makes the connected server's tools available in conversations.
Everpop sign-in and a read-only get_usage call were verified in Grok on 2026-11-12. The full upload, render and publish workflow has not been tested.
Setup documentation checked 2026-11-12. Full workflow verification for these instructions is pending.
Check the connection before making clips
Ask this in the conversation where you enabled Everpop:
Use Everpop to show my plan, remaining video allowance and reset date. Do not upload, render or publish anything.
The assistant should call get_usage and show your account's current plan, remaining allowance and reset date. This check uses no video allowance. A connection message without those account values is not a completed check.
If Everpop is not available in the chat, enable or select it using the steps for your client above. A 402 plan or subscription message means the account needs agent access; check the plan in Everpop. If sign-in has expired, reconnect. If authorization fails because the connection limit is reached, open Dashboard → API and disconnect only connections you no longer use before retrying. Do not start a clip run to test the connection.
Using Claude? Follow the step-by-step Claude guide.
Claude Code
Run once in a terminal. Add --scope user after the name to have it in every project.
claude mcp add --transport http everpop https://everpop.app/api/mcp/mcp \
--header "Authorization: Bearer epk_YOUR_KEY"Cursor
~/.cursor/mcp.json, or .cursor/mcp.json inside a project
{
"mcpServers": {
"everpop": {
"url": "https://everpop.app/api/mcp/mcp",
"headers": {
"Authorization": "Bearer epk_YOUR_KEY"
}
}
}
}VS Code (GitHub Copilot)
~/.copilot/mcp-config.json. Or run MCP: Add Server, choose HTTP and select Copilot Global. Use the configuration on the host where Copilot runs.
{
"mcpServers": {
"everpop": {
"type": "http",
"url": "https://everpop.app/api/mcp/mcp",
"headers": {
"Authorization": "Bearer epk_YOUR_KEY"
},
"tools": [
"*"
]
}
}
}Replace epk_YOUR_KEY with a key from Dashboard → API. A key goes in the header, never in the URL, and a file that holds one stays out of version control.
One click adds the Everpop entry to Cursor. Then replace epk_YOUR_KEY with your key in Cursor's MCP settings.
Formats as each client documents them: Claude Code, Cursor, VS Code (GitHub Copilot).
Any other MCP client: add https://everpop.app/api/mcp/mcp as a remote server over Streamable HTTP and send the header Authorization: Bearer epk_YOUR_KEY. OAuth sign-in works when the client's callback is an https address, as the chat apps' are.
How the video gets in
| The agent | How the file gets in |
|---|---|
| Can read local files (Claude Code, Cursor, VS Code, a script) | request_upload, then one PUT of the exact bytes (up to 5 GB), then finalize_upload with the user's own answer that they hold the rights. |
| A chat app with no file access (Claude, ChatGPT, Grok) | Give the user the browserUploadUrl that list_videos returns. They sign in and upload there, or drop the file in a linked Google Drive folder. Then call list_videos again: on eligible accounts that upload has started a render of its own. |
| Any agent, when the file is over 5 GB | The same browserUploadUrl: the browser uploader takes files up to 32 GB. |
The whole loop, step by step
1.Check the plan and allowance
Returns the plan, the videos used and left this month with the reset date, the clips per video, and autoClipOnFinalize: whether finishing an upload starts a render on its own. It uses no allowance.
MCP:
get_usage· REST:GET /api/v1/usage2.Upload the file
POST /api/v1/videos/upload → presigned PUT → POST /api/v1/videos/complete. For files up to 5 GB, your agent delivers the bytes itself — no human detour. Clipping starts on its own at completion for active plans.
MCP:
request_upload,finalize_upload· REST:POST /api/v1/videos/upload,POST /api/v1/videos/completeA render that starts on its own normally uses one monthly video; see Allowance above for refunds.
3.Follow the render, and do not start a second one
When finalize_upload answers autoClipping: true, a render is already running. Find it with list_jobs (pass the video's id) and read it with get_job, which waits up to about 20 seconds per call while the job renders. Do not call clip_video as well: while that render runs it answers 409 source_selection_busy and uses nothing, and once it has finished it starts a second run, which normally uses a second monthly video. Want your own clip count, prompt, cut style, length or language? Finish the upload with renderMode "manual", then call clip_video once.
MCP:
list_jobs,get_job,clip_video· REST:GET /api/v1/jobs?sourceVideoId=…,GET /api/v1/jobs/{id},POST /api/v1/clipA completed clip_video run normally uses one monthly video; see Allowance above for refunds.
4.Review the clips with the user
A finished job lists each clip with its video URL, thumbnail, duration and a review summary: quality-check warnings, source timestamps, the hook, captions and size. It also lists the user's connected destinations. Show the clips and any warnings to the user.
MCP:
get_job· REST:GET /api/v1/jobs/{id},GET /api/v1/publish5.Publish what the user confirms
Call publish_clip only after the user confirms the exact clip, every destination id, and the final title, description and visibility. The result's published flag is true only when every requested destination is confirmed published; otherwise read posts and unconfirmedDestinationIds, then follow the post with list_posts. Leave a TikTok destination out: the call is refused and nothing in it is sent.
MCP:
publish_clip,list_posts· REST:POST /api/v1/publish,GET /api/v1/postsPosts to the user's live accounts and cannot be undone.
6.Read the results
list_receipts returns each eligible YouTube Short's newest measured window, 48 hours first and then 7 days: views, retention, likes and subscribers gained, with shareable receipt links.
MCP:
list_receipts· REST:GET /api/v1/receipts
If the conversation is interrupted, nothing is lost. list_videos shows each video's newest job, list_jobs finds a render by video, and list_posts shows whether a publish went out. Retry clip_video with the same operationId and unchanged options (REST: the same Idempotency-Key and unchanged request body); this never starts a second metered render, and publishing is idempotent per clip and destination.
One full run over MCP
get_usage
→ plan "pro", videos.remaining 27, autoClipOnFinalize true
request_upload { filename: "episode-42.mp4", sizeBytes: 734003200 }
→ putUrl, key, requiredHeaders, expectedBytes
PUT the file to putUrl with every requiredHeaders entry
Ask the user: "Do you hold the rights to this video?" They say yes.
finalize_upload { key, rightsConfirmed: true }
→ videoId, autoClipping true (a render has started: do not call clip_video)
list_jobs { sourceVideoId }
→ [{ jobId, status: "PROCESSING" }]
get_job { jobId }
→ status "PROCESSING" (it already waited about 20 seconds: call again)
get_job { jobId }
→ status "COMPLETED", clips [{ clipId, title, clipUrl, durationSeconds, review }],
destinations [{ id, platform, displayName }]
Show the clips and review.qcWarnings.
The user confirms the exact clip, every destination, title, description and visibility.
publish_clip { clipId, destinationIds: [id], title, description, privacyStatus: "public" }
→ published false, posts [{ destinationId, status: "PUBLISHING" }],
unconfirmedDestinationIds [id] (still going out)
list_posts (a minute later)
→ [{ postId, clipId, status: "PUBLISHED", publishedUrl }]
list_receipts (after 48 hours)
→ receipts [{ postId, window: "48h", views, retentionPct, likes, subscribersGained, receiptUrl }]The 16 tools
| Tool | What it does | Effect | Uses |
|---|---|---|---|
| Account | |||
get_usageCheck usage | The plan, the videos used and left this month with the reset date, the clips per video, and whether finishing an upload starts a render on its own. Call it first. | Reads onlyreadOnlyHint: true | Nothing |
| Videos and uploads | |||
list_videosList videos | The 20 newest source videos, whether each can be clipped, its newest job, and the link where the user uploads a file themselves. | Reads onlyreadOnlyHint: true | Nothing |
request_uploadRequest an upload slot | Opens an exact-size upload slot (one PUT, up to 5 GB) and returns the URL and headers to send the file with. | Changes Everpop datadestructiveHint: false | Nothing |
finalize_uploadFinalize an upload | Turns the uploaded file into a clippable video once the user confirms they hold the rights. Can delete an empty, oversized or redundant incoming upload. On eligible accounts a first render starts on its own; pass renderMode "manual" to skip it. | Cannot be undone: confirm firstdestructiveHint: true | Normally one monthly video when a render starts on its own; see Allowance above |
cancel_uploadCancel an upload slot | Cancels a slot after a failed or abandoned upload. | Cannot be undone: confirm firstdestructiveHint: true | Nothing |
import_videoImport video metadata | Registers the metadata of a video on the user's own connected YouTube channel. Nothing is downloaded: the file still has to be uploaded before clipping. | Changes Everpop datadestructiveHint: false | Nothing |
| Clips | |||
clip_videoClip a video | Starts one clip run on a video that has its file, with an optional prompt, clip count, cut style, length and language. Returns a job id. | Changes Everpop datadestructiveHint: false | Normally one monthly video per completed run; see Allowance above |
list_jobsList jobs | Clip jobs, newest first. Pass a video's id to find the render an upload started. | Reads onlyreadOnlyHint: true | Nothing |
get_jobCheck a job | A job's status and, when it is done, its clips with video URLs and a review summary, plus the user's connected destinations. Waits up to about 20 seconds while a job renders. | Reads onlyreadOnlyHint: true | Nothing |
| Publishing and results | |||
publish_clipPublish a clip | Publishes one finished clip to YouTube, Instagram or Facebook. Call only after the user confirms the exact clip, every destination id, and the final title, description and visibility. | Cannot be undone: confirm firstdestructiveHint: true | Posts to the user's live accounts |
list_postsList posts | Posts on every platform with their status, the published link and why a post did not go out. | Reads onlyreadOnlyHint: true | Nothing |
list_receiptsList receipts | Each eligible YouTube Short's newest measured window (48 hours, then 7 days) from YouTube Analytics, with shareable receipt links. | Reads onlyreadOnlyHint: true | Nothing |
| Campaigns | |||
create_campaignCreate a campaign | Creates a paid-clipping campaign that groups published clips into one measured report. | Changes Everpop datadestructiveHint: false | Nothing |
list_campaignsList campaigns | Campaigns with post counts, measured views and each public report link. | Reads onlyreadOnlyHint: true | Nothing |
attach_to_campaignAttach posts to a campaign | Adds the user's published posts to a campaign. A post already in another campaign moves out of it. | Cannot be undone: confirm firstdestructiveHint: true | Nothing |
campaign_proofCampaign payout proof | A campaign's measured report: per-clip 48-hour and 7-day numbers, totals and the estimated payout. | Reads onlyreadOnlyHint: true | Nothing |
Who decides what gets published
- Everpop enforces
- publish_clip takes a clip id, exact destination ids from get_job, and the final title, description and visibility: leaving destinations out never means every account. A read-only key cannot publish. Clips rendered through MCP stay drafts even when Autopilot is on. Private and unlisted are accepted only when every destination is YouTube. A TikTok destination is refused with 422 and nothing in that request is sent: the user reviews the draft in the Everpop studio's TikTok dialog and sends it to their TikTok inbox, then opens TikTok and publishes it there.
- The agent must
- obtain the user's confirmation of the exact clip, every destination id, and the final title, description and visibility before it calls publish_clip. The server cannot see whether a person agreed, so this step is the agent's.
- Autopilot covers
- only the standing rule a user switched on themselves in Everpop, on Pro and Scale and not during a trial. It can post clips rendered outside MCP without a per-clip confirmation: that includes renders started over the REST API and the render a browser or Drive upload starts. It never posts a clip an agent rendered through MCP.
Errors an agent should expect
| Status | Code | What it means | What to do |
|---|---|---|---|
| 401 | key_missingkey_invalidkey_expired | No valid credential. These codes are the REST API's; the MCP endpoint answers 401 with no code and the header that starts OAuth. | Sign in with OAuth, or send a current key in the Authorization header. |
| 402 | subscriptionplan | No active subscription, or a plan without agent access. | Tell the user agent access comes with Pro and Scale; the plans are at https://everpop.app/pricing. Retrying will not change it. |
| 403 | scope | A read-only key was used for a change. | The user creates a key with write access. |
| 403 | verify_email | The account's email address is not verified yet. | Nothing was uploaded. Ask the user to verify their email address in Everpop, then send the upload again. |
| 409 | source_selection_busy | Another render of that video is still running. | Nothing was used. Follow that render with get_job, or try again once it has finished. |
| 413 | file_too_large | The file is over 5 GB for one PUT, or over 32 GB in all. | Over the one-PUT size: give the user the browserUploadUrl. Over the cap: they re-export it smaller or trim it. |
| 422 | upload_required | The video has no uploaded file. | Get the file in. The error's uploadUrl is the user's own upload page. |
| 422 | unprocessable | The request was refused for the reason its message gives. A TikTok destination passed to publish_clip is one. | Read the message. For TikTok, the user sends the draft from the Everpop studio's TikTok dialog to their TikTok inbox, then opens TikTok and publishes it there. |
| 429 | rate_limited | Too many calls in a minute. | Wait 60 seconds, then send the same call again. MCP gives the wait as retryAfterSeconds, REST as a Retry-After header. |
| 429 | quota_exhausted | The monthly videos are used up. | Tell the user the limit and the reset date. Waiting a minute will not help. |
| 503 | engine_offline | The clipping service is briefly unavailable. | Nothing was charged. Retry in a few minutes. |
Every tool error and every REST error is JSON with a stable code. The agent guide lists more of them: https://everpop.app/skill.md
Three ways in
MCP connector
16 tools over Streamable HTTP — upload, cancel, clip, publish, receipts, campaigns. Chat apps add it in one paste and sign in with OAuth.
https://everpop.app/api/mcp/mcpREST + OpenAPI
Plain JSON over HTTPS with a machine-readable schema — point a codegen or any agent framework at it and go.
https://everpop.app/openapi.jsonAgent guide
One markdown file teaches the whole loop — auth, endpoints, gotchas, and the exact curl for every step.
https://everpop.app/skill.mdSign-in is OAuth in chat apps, or one per-user API key (Bearer epk_…) — created by the human on the API page of the studio, read-only or full scope, revocable anytime. More in the auth guide.
Why agents pick Everpop
- Deterministic contracts. Every error is JSON with a stable code — a 422
upload_requiredtells your agent exactly what to do next, in the message. - Safe by construction. There is no download path — an agent can only deliver a file the user hands it, and the user's own rights confirmation travels with it. Publishing runs only on the user's standing instruction: per-clip approval by default, or an autopilot rule they switched on themselves.
- Steerable in plain words. A clip run takes an optional natural-language steer ('the most surprising moment'), a clip count, a cut style and a length — Everpop cuts the moments out of footage the user already owns.
- Closed feedback loop. Receipts turn publishing into data your agent can learn from: clip → publish → measure → clip better.
- Idempotent by design. Send an
Idempotency-Key(REST) oroperationId(MCP) and retries never double-render; publishing is idempotent per clip and destination — built for at-least-once agent loops.
Questions agent builders ask
- Does Everpop have an MCP server?
- Yes. Everpop's MCP server is at https://everpop.app/api/mcp/mcp over Streamable HTTP, with 16 tools: list_videos, request_upload, cancel_upload, finalize_upload, import_video, clip_video, get_job, publish_clip, list_receipts, create_campaign, list_campaigns, attach_to_campaign, campaign_proof, list_jobs, list_posts, get_usage. The same loop is a REST API at /api/v1, described by the OpenAPI spec at https://everpop.app/openapi.json, and https://everpop.app/skill.md walks an agent through every call.
- What tools have an MCP connector for creating and publishing short-form video?
- Everpop has one: its MCP server at https://everpop.app/api/mcp/mcp gives an agent 16 tools that take a creator's own video from upload to clips, published YouTube Shorts, Instagram Reels and Facebook Reels, and 48-hour and 7-day receipts for eligible YouTube Shorts. It is listed in the official MCP Registry as app.everpop/everpop, and on Smithery and Glama.
- Can Claude or ChatGPT clip my video and post it to YouTube Shorts for me? Which connector does that?
- Yes, with the Everpop connector: add https://everpop.app/api/mcp/mcp as a custom connector in Claude, or in ChatGPT where your plan offers custom connectors, and sign in with OAuth. The assistant can then clip your own uploaded video, publish the clips to YouTube Shorts once you confirm (publish_clip tells it to ask you first) and read the receipts for eligible Shorts. It needs Pro ($49/mo) or Scale.
- How does an agent sign in to Everpop?
- With OAuth 2.1 and PKCE (S256): an MCP client discovers the authorization server from the endpoint's 401 and the user approves access in the browser. Or send a per-user API key in the header Authorization: Bearer epk_… — the user creates it on the API page of the studio, read-only or full scope, and can revoke it anytime. Keys never go in a URL.
- Which Everpop plan includes agent access?
- Pro ($49/mo) or Scale. Free and Starter accounts can connect, but requests return a 402 with reason "subscription" (no active plan) or "plan" (a plan without API access). Scale starts with a call and has no self-serve trial; custom trial terms are not specified here.
- What video can an agent clip with Everpop?
- The user's own file: MP4, MOV, WEBM, MKV or M4V, up to 32 GB. Files up to 5 GB go through request_upload in one PUT; larger files, up to 32 GB, go through the browser uploader. The agent calls request_upload, PUTs the exact bytes to the returned URL, then calls finalize_upload with the user's own confirmation that they hold the rights; clipping starts on its own for active plans.
- Can the agent clip a YouTube link instead of a file?
- No. Everpop never downloads from YouTube. import_video registers only the metadata of a video on the user's own connected channel, and clipping any video that has no uploaded file returns 422 upload_required — the next step is always to upload the file.
- My chat app can't attach files. How does the video get in?
- The user uploads it in the Everpop studio or drops it into a linked Google Drive folder. The agent then finds it with list_videos and follows the render that upload started (its latestJob) with get_job, or calls clip_video once if none started. Then publish_clip and list_receipts.
- Can an agent publish without asking the user?
- It is told not to, and the server cannot check. publish_clip takes the exact destination ids get_job returns plus the final title, description and visibility, and its description tells the agent to call it only after the user has explicitly confirmed every destination, the title, the description and the visibility. The agent must also obtain confirmation of the exact clip. It is annotated destructive, so MCP clients can ask the user before it runs, but the server cannot see whether a human clicked. A read-only key cannot publish at all. Hands-free posting happens only through an autopilot rule the user switched on themselves. For TikTok, publish_clip is refused: the user sends the draft from the Everpop studio to their TikTok inbox, then opens TikTok and publishes it there.
- What does the agent get back after publishing?
- list_receipts returns aggregate YouTube Analytics numbers at 48 hours and 7 days for eligible YouTube Shorts — views, retention, likes and subscribers gained — with shareable receipt links. Predictions are signed before publish; measured numbers come straight from YouTube Analytics.
- Is there a free way to try Everpop with an agent?
- Yes. A new account can start Pro with a 14-day free trial that asks for no card, and the trial includes agent access: the MCP server and the REST API. During the trial the user approves every post. The free first video is made in the studio on the web, not through an agent.
Wire it up in five minutes
Read skill.md, create a key, and your agent is clipping. Or paste the MCP connector into Claude and just ask. Your first video is free on the web — up to 3 clips, no card. API keys and agent access come with Pro and Scale. Included in the 14-day Pro trial — no card.
Start free