RemixViral for AI agents: ChatGPT, Claude, Cursor and Gemini operate it, you supervise
RemixViral cuts a long video you own into ranked, captioned vertical Shorts. Its MCP server is built for an AI agent to read those results, make faceless Shorts and check credits, while you tag the work, review it and approve. Uploading the source video stays a human step in the web app. Markdown version of this page: /mcp.md.
RemixViral at a glance
- What it is
- RemixViral is an AI clip maker built for AI agents to operate over MCP: you upload a long video you own, your agent reads the ranked, captioned 9:16 Shorts cut from it (with the reason each was picked) and can start faceless Shorts, and you tag the work, review and approve.
- Who it is for
- AI agents and assistants (ChatGPT, Claude, Cursor, Gemini CLI, custom agents) that operate it, and the people who supervise them: podcast, webinar and event teams, agencies and in-house video teams that repurpose recordings they own, plus individual creators and small businesses. The buyer's outcome: your agent does the clip review and Short-making, you approve and audit.
- What it does not do
- No link import (upload only, your own video), no timeline editor, no team seats or shared workspaces, no translation of other people's videos, no free plan, no guarantee of views.
- Price
- From $19/month (Starter, 1,200 credits); Business is $129/month for 10,000 credits. No free plan: monthly plans start with a $5 trial, then the plan price unless you cancel. A clip project costs 50 credits per source video up to 60 minutes, plus 1 credit per extra minute (longest source 120 minutes).
- Integrations
- MCP connector for ChatGPT, Claude, Claude Code, Cursor, Gemini CLI and other MCP clients; REST API with API keys (included in every plan); share to TikTok for clips cut from an uploaded file.
- Human oversight
- The owner approves access on an OAuth consent screen, sees every key and its last use under Dashboard, API keys, can revoke it at any time, and everything the agent creates shows up in the dashboard. When you create an API key yourself you can limit its scopes. Spending is capped by the prepaid credit balance. There is no per-action approval queue: confirmation depends on your MCP client.
- Security basics
- HTTPS/TLS; OAuth 2.1 with PKCE for assistants, or revocable API keys with scopes; MCP tools cannot upload, delete or buy anything. Where data is stored is not published on the site.
- Start in a few steps
- Start a plan, upload one video you own in the web app, connect your agent (see /en/mcp: one URL, sign in, Allow), then ask it for your clips and review what it returns.
- MCP server
- https://remixviral.ai/api/mcp (ChatGPT: https://remixviral.ai/api/mcp/chatgpt); Official MCP Registry name ai.remixviral/clipper.
Agent quickstart
1. Discover
- https://remixviral.ai/llms.txt and https://remixviral.ai/llms-full.txt: product facts, pricing and limits for language models.
- https://remixviral.ai/.well-known/mcp/server-card.json: machine-readable server card (URL, auth, tools, registry name).
- Official MCP Registry: ai.remixviral/clipper (remote server, Streamable HTTP).
- https://remixviral.ai/pricing.md and https://remixviral.ai/mcp.md: plain-markdown pricing and this guide.
2. Authenticate
- OAuth 2.1 with PKCE and dynamic client registration, discovered from https://remixviral.ai/api/mcp (401 with a WWW-Authenticate resource_metadata link). The human owner signs in to RemixViral and presses Allow on the consent screen; RemixViral then creates an API key named "MCP: <client name>" on their account (90-day expiry).
- API key: the owner creates a key at https://remixviral.ai/en/developers and gives it to the agent as Authorization: Bearer <key>. Default scopes: video:create, video:read, credits:read, usage:read.
- There is no self-serve agent signup: an account is created and paid for by a human, and a human approves (OAuth) or creates (API key) the agent's access.
3. Minimal call sequence
| Step | Tool | Example arguments | Returns |
|---|---|---|---|
| Check what the account can afford | get_credit_balance | {} | balance, monthly allocation and plan |
| Find the clip jobs the human uploaded | list_clip_jobs | {} | sources[] with id, status, title |
| Read the ranked clips | get_clip_job | { "id": "<job id>", "includeTranscript": false } | clips ranked best first with startSec, endSec, reason, score, render status |
| Start a faceless Short (spends credits; show the cost to the human first) | create_video | { "topic": "3 tiny habits that change your life", "duration": 30, "language": "en" } | id and status "PENDING"; estimatedCredits |
| Poll until done (every 20-30 seconds) | get_video | { "id": "<video id>" } | status PENDING/GENERATING_*/RENDERING, then COMPLETED with videoUrl, or FAILED with error |
4. Limits, cost, idempotency
- Rate limit: each API key allows 100 requests per hour by default; beyond that the call fails with 429 RATE_LIMIT_EXCEEDED and the reset time in the message.
- At most 3 faceless videos may render at once per account; a fourth call returns 429 TOO_MANY_PENDING_VIDEOS.
- Idempotency: create_video is not idempotent, but an identical request within 10 minutes returns the existing video with deduplicated: true and spends nothing. allowDuplicate: true forces a new one.
- Cost: a faceless Short costs 40 credits with the default voice, checked before anything is queued; reading tools never charge.
- Clip jobs cannot be started by an agent: the human uploads a video they own in the web app. There is no link import.
5. Errors to handle
Over MCP these arrive as a tool result with isError: true and this code; only 401 and 413 are real HTTP statuses at the transport.
| Code | REST status | Meaning | Agent action |
|---|---|---|---|
| UNAUTHORIZED | 401 | Missing, invalid or revoked key or token | Stop and ask the human to reconnect or issue a new key |
| INSUFFICIENT_SCOPE | 403 | The key lacks the scope the tool needs | Tell the human which scope is missing (the error links to the key page) |
| VIDEO_LIMIT_REACHED | 403 | No video allowance or credits left (no active paid plan or balance) | Hand off: a human must start or renew a plan, there is no free plan |
| INSUFFICIENT_CREDITS | 402 | Balance is below the cost; the error states credits needed and available | Report the numbers to the human; do not retry |
| RATE_LIMIT_EXCEEDED | 429 | Per-key hourly limit reached; the message carries the reset time | Wait until the stated reset time, then retry |
| TOO_MANY_PENDING_VIDEOS | 429 | Three videos are already rendering | Poll list_videos and retry after one finishes |
| INVALID_TOPIC / TOPIC_TOO_LONG / INVALID_DURATION / INVALID_ALLOW_DUPLICATE | 400 | Validation error in the arguments | Fix the argument (topic up to 500 characters, duration 30, 60 or 90) and retry once |
| PAYLOAD_TOO_LARGE | 413 | Request body over the size cap | Send a smaller request |
6. Hand off to the human
- After create_video, give the human the video id and, once COMPLETED, the videoUrl, so they can review it.
- When a call fails with UNAUTHORIZED, INSUFFICIENT_SCOPE, VIDEO_LIMIT_REACHED or INSUFFICIENT_CREDITS, stop and tell the human exactly what they need to change; these are not retryable by the agent.
- For a clip job, summarise the ranked clips (times, score, reason) and let the human decide which to use; exporting and posting are done in the web app.
Human oversight: what you can see, approve and revoke
- Approve access
- OAuth consent screen (src/app/api/oauth/authorize): shows the client name and what it can do (create videos, read videos and status, read credit balance and API usage) with Allow and Cancel. Nothing is connected until the owner presses Allow.
- See what is connected
- Dashboard, API keys lists every key with its name (OAuth connections appear as 'MCP: <client>'), scopes and last-used time.
- Revoke
- Revoking a key in Dashboard, API keys cuts the agent off on its next call. Deleting the key has the same effect.
- Limit what a key can do
- Scopes are set per key (video:read, video:create, credits:read, usage:read, and others); a read-only key cannot create videos. Each key has its own request limit.
- Spending cap
- Spending is prepaid credits: create_video is refused up front when the balance is short, and at most three videos can render at once. There is no separate per-key spend cap.
- Review what the agent did
- Videos the agent creates appear in the dashboard's Videos list like any other; API usage per key is recorded and shown in the developer portal's Usage tab.
- Safe-by-default tool hints
- Six tools are annotated readOnlyHint: true. create_video is annotated readOnlyHint: false, destructiveHint: false, idempotentHint: false, so MCP clients that honour the hints ask the human before running it.
- No destructive tools
- The MCP server has no tool that deletes, uploads, buys credits or changes the plan.
Prompts to copy: tag the work, review the result
Paste one into your assistant after connecting. Each asks the agent to show what it did so you can approve it.
Individual creator
- Assign to RemixViral: go through my latest clip job and pick the three best clips. Show me the start and end times, the score and why each was picked, so I can approve them.
- Use RemixViral to get the transcript of my latest clip job and draft a title and a one-line caption for each of its top three clips. List what you drafted so I can review it.
- Check my RemixViral credit balance and plan, and tell me how much of it you used in this chat.
Small business
- Assign to RemixViral: a 30-second faceless Short about three tips for choosing a wedding photographer. Check my balance and tell me the cost first, and only create it after I say yes. Then show me the video id and link.
- Use RemixViral to list my videos that are still rendering and the finished ones with links, so I can review what is ready.
Agency or team
- Assign to RemixViral: across my last five clip jobs, collect the best-scoring clips grouped by topic and show me a table (job, clip, times, score, reason) for the client review.
- Use RemixViral to tell me which clip jobs are not finished yet and what stage each one is in. Do not start anything new.
Developer or agent builder
- Use RemixViral to list the niches, art styles and durations create_video accepts, then summarise them.
- Use RemixViral to create a 60-second faceless Short about how HTTP caching works after I confirm the cost. Poll get_video until it is COMPLETED, then report the videoUrl and the credits it used.
Server details
- Server URL:
https://remixviral.ai/api/mcp(remote, Streamable HTTP, nothing to install) - ChatGPT URL:
https://remixviral.ai/api/mcp/chatgpt - Sign-in: OAuth 2.1 with PKCE, or
Authorization: Bearerwith an API key from the developer portal - Official MCP Registry name:
ai.remixviral/clipper(registry entry) - You need a RemixViral account. There is no free plan; see pricing.
Tools
| Tool | What it does | Credits |
|---|---|---|
| list_clip_jobs | Lists your long-video clip jobs, newest first, with id, status and title. | Read-only, free |
| get_clip_job | Reads one clip job: status, then the clips ranked best first with start and end seconds, the reason each was picked and a score. Optional full transcript. | Read-only, free |
| create_video | Starts a faceless Short from a topic (30, 60 or 90 seconds). Returns an id; the render runs asynchronously. | Spends credits |
| get_video | Status of one video and, when it is done, the playable link. | Read-only, free |
| list_videos | Lists your videos, newest first, with an optional status filter. | Read-only, free |
| list_niches | Lists the niches, art styles, qualities and durations create_video accepts. | Read-only, free |
| get_credit_balance | Your credit balance, monthly allocation and plan. | Read-only, free |
The assistant cannot upload a video, start a clip job, delete anything or buy credits. Clip jobs start when you upload a video you own in the RemixViral web app; there is no link import.
How to connect
What you see on approval: RemixViral asks you to sign in, then shows "Connect <client> to RemixViral?" with the list of what the client can do on your account (create videos, which spends your credits; read your videos and their status; read your credit balance and API usage) and two buttons, Cancel and Allow. Allowing creates an API key named "MCP: <client>" that you can revoke any time in Dashboard, API keys.
ChatGPT
- Turn on developer mode in ChatGPT's settings and create a new custom MCP connector.
- Use the server URL https://remixviral.ai/api/mcp/chatgpt (the ChatGPT version of the server: same tools, with purchase links removed).
- Choose OAuth, sign in to RemixViral and press Allow.
RemixViral is not in ChatGPT's public app directory yet, so it is added by URL.
Claude (apps with custom connectors)
- In the connector settings of a Claude app that accepts a custom remote MCP connector, add https://remixviral.ai/api/mcp.
- Sign in to RemixViral and press Allow on the consent screen.
We have not clicked through every Claude app's settings screen, so the menu names are not listed here; the server URL and the OAuth flow are what matter.
Claude Code
- Install the plugin, or add the server directly with the second command.
- Run /reload-plugins, open /mcp, choose remixviral and authenticate in the browser.
/plugin marketplace add airdropfi/remixviral-claude-plugin
/plugin install remixviral@remixviral-plugins
# or, without the plugin:
claude mcp add --transport http remixviral https://remixviral.ai/api/mcpSource: airdropfi/remixviral-claude-plugin (MIT)
Cursor
- Add the server to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project); the Cursor kit also has a one-click install button.
- Open Settings, then MCP, connect remixviral, sign in and press Allow.
{
"mcpServers": {
"remixviral": { "url": "https://remixviral.ai/api/mcp" }
}
}Source: airdropfi/remixviral-cursor-kit (MIT)
VS Code (Copilot agent mode)
- Put this in .vscode/mcp.json; VS Code prompts for the API key through the input defined here.
{
"inputs": [
{ "type": "promptString", "id": "remixviral-key", "description": "RemixViral API key", "password": true }
],
"servers": {
"remixviral": {
"type": "http",
"url": "https://remixviral.ai/api/mcp",
"headers": { "Authorization": "Bearer ${input:remixviral-key}" }
}
}
}Gemini CLI
- Install the extension, restart Gemini CLI and sign in with /mcp auth remixviral.
gemini extensions install https://github.com/airdropfi/remixviral-gemini-extension
# restart Gemini CLI, then:
/mcp auth remixviralSource: airdropfi/remixviral-gemini-extension (MIT)
Other clients (Windsurf, Cline, custom agents)
Clients that take a remote URL use the same server with an API key; the key name for the URL differs by client (url, serverUrl or httpUrl), so check your client's MCP docs. We have not tested Windsurf or Cline ourselves. A client that only starts local commands can run the npm package instead; it covers the faceless-Short tools, not clip jobs, and its tool names differ from the remote server's.
{
"mcpServers": {
"remixviral": {
"url": "https://remixviral.ai/api/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}{
"mcpServers": {
"remixviral": {
"command": "npx",
"args": ["-y", "@remixviral/mcp-server", "--api-key", "YOUR_API_KEY"]
}
}
}Prefer an API key to OAuth?
Create a key in the developer portal and send it as a Bearer header. The read tools need the video:read scope, create_video also needs video:create, and get_credit_balance needs credits:read.
{
"mcpServers": {
"remixviral": {
"url": "https://remixviral.ai/api/mcp",
"headers": { "Authorization": "Bearer YOUR_API_KEY" }
}
}
}Privacy and data handling
RemixViral receives only what the assistant sends in its tool calls, such as a topic or a clip job id, not the rest of your conversation. The assistant receives the results: clip titles and timestamps, transcripts if it asks, video status and links, and your credit balance. That data is then handled under the assistant provider's own privacy policy. A connection through OAuth creates an API key on your account that you can delete under Dashboard, API keys. Details: privacy policy, AI assistants (MCP).
Frequently Asked Questions
How do I use RemixViral from ChatGPT?▼
Add RemixViral as a custom MCP connector in ChatGPT (developer mode) with the URL https://remixviral.ai/api/mcp/chatgpt and sign in with OAuth. It is not listed in ChatGPT's public directory yet. Then ask ChatGPT to list your clip jobs or show the ranked clips of one job. Anything that spends credits is flagged first.
How do I use RemixViral from Claude?▼
In Claude Code, install the plugin with /plugin marketplace add airdropfi/remixviral-claude-plugin, or add the server with: claude mcp add --transport http remixviral https://remixviral.ai/api/mcp. Then authenticate in /mcp. Other Claude apps that accept a custom remote MCP connector can use the same URL, https://remixviral.ai/api/mcp.
Can an AI assistant clip a video for me through RemixViral?▼
Not by itself. Clipping starts when you upload a video you own in the RemixViral web app; there is no link import and no tool starts a clip job. After that the assistant can read the job, the ranked clips with their timestamps and reasons, and the transcript if you ask for it.
What does it cost to use the MCP connector?▼
Connecting is free, but RemixViral itself has no free plan: you need an account with a paid plan or the paid start offer on the pricing page. Six of the seven tools only read and never charge credits. create_video, which makes a faceless Short from a topic, uses credits from your balance (40 credits with the default voice at the time of writing; the tool states the current cost).
How does sign-in work, and what can the assistant see?▼
Sign-in is OAuth 2.1 with PKCE, or you can paste an API key you created on the developers page. The assistant sees only what its tool calls return: your clip jobs and clips, your videos and their status, and your credit balance. It cannot upload videos, start clip jobs, delete anything or buy credits. You can revoke the connection by deleting its key under Dashboard, API keys.
Is there an official MCP Registry entry?▼
Yes. RemixViral is published in the Official MCP Registry as ai.remixviral/clipper, a remote server at https://remixviral.ai/api/mcp (Streamable HTTP).
More: pricing · RemixViral vs OpusClip · developer portal