Start FromWhat Already Works
Every example starts with an input. Revid analyzes it, extracts what matters, and creates something new for you.
Viral Video
Your Version
Give Claude, ChatGPT, Cursor, internal automations, and custom AI agents the same engine behind Revid: write, render, and publish finished videos end to end. Connect the MCP with one-click OAuth sign-in, script it with the CLI, or call the public API directly. And if you would rather build your own Revid on top of it, go ahead. We'll be your backend.
Paste the server URL in Claude, ChatGPT, Cursor, or VS Code and sign in with your Revid account. No API key to copy, scoped tokens with automatic refresh.
Turn scripts, prompts, articles, audio, music, captions, avatars, and ads into short-form videos.
Expose the full Revid creation pipeline through MCP tools with clear resources and structured responses.
Use the MCP wrapper for agent actions or call the same public API directly from your own backend.
All three wrap the same Revid video creation pipeline. Choose based on where your agent or code runs.
Tool-calling agents
Claude, ChatGPT, Cursor, VS Code, and custom agents built on the MCP SDKs. Connect with one-click OAuth or an API key.
Terminal agents, CI jobs, scripts
The revid-cli npm package with stable --json output, exact API payload mode, render polling, exports, and credit estimates.
Backend integrations and products
Call the same video creation API directly from your own code when you want full control over rendering and publishing.
Hosted MCP clients connect with OAuth: paste the server URL, sign in with your Revid account, done. Header-configurable clients can use an API key instead.
https://www.revid.ai/api/mcpChecking your session so we can personalize the examples with your Revid API key.
Keep this key secret. Requests made with it, or with OAuth tokens, consume credits from your Revid account or active workspace.
# Revid MCP OAuth 2.1 details
flow: authorization_code + PKCE (S256)
scope: mcp:use
dynamic client registration: POST https://www.revid.ai/api/oauth/register
authorization endpoint: https://www.revid.ai/api/oauth/authorize
token endpoint: https://www.revid.ai/api/oauth/token
protected resource metadata: https://www.revid.ai/.well-known/oauth-protected-resource
authorization server metadata: https://www.revid.ai/.well-known/oauth-authorization-server
access tokens: 1 hour; refresh tokens: rotating, long-lived
fallback auth: API key via Authorization Bearer, x-revid-api-key, x-api-key, or key headercurl -X POST "https://www.revid.ai/api/public/v3/render" \
-H "Content-Type: application/json" \
-H "key: YOUR_REVID_API_KEY" \
-d '{
"workflow": "voiceover-to-video",
"source": {
"text": "Create a 30-second short video about 3 surprising AI productivity tips."
},
"media": {
"type": "moving-image",
"quality": "pro",
"animation": "soft"
},
"voice": {
"enabled": true,
"voiceId": "cgSgspJ2msm6clMCkdW9"
},
"captions": {
"enabled": true,
"preset": "Wrap 1",
"position": "bottom"
}
}'# Revid MCP quick reference
endpoint: https://www.revid.ai/api/mcp
transport: Streamable HTTP
auth (hosted clients): OAuth 2.1 with PKCE and dynamic client registration; discovery via https://www.revid.ai/.well-known/oauth-protected-resource
auth (header clients): Authorization Bearer, x-revid-api-key, x-api-key, or key header with a Revid API key
primary flow: render_video -> get_project_status -> export_video or publish_now
render docs resource: revid://docs/render
mcp guide resource: revid://docs/mcp
agent-readable docs: https://www.revid.ai/llms.txt, https://www.revid.ai/llm/revid-ai-mcp-server.md
tools: generate_media, render_video, get_project_status, list_projects, calculate_credits, export_video, rename_project, clone_voice, list_characters, create_character, delete_character, schedule_publish, publish_now, buy_credit_packThe MCP wraps Revid's public video API, so agents can estimate, generate, monitor, export, rename, and publish projects without inventing their own video pipeline. Agents can read the `revid://docs/render` resource for the always-current payload reference.
Optionally call `calculate_credits` to estimate cost before rendering.
Call `render_video` with a workflow and source payload, then store the returned `pid`.
Poll `get_project_status` until the response includes `videoUrl`.
Optionally call `export_video`, `schedule_publish`, or `publish_now`.
Agents can choose the workflow that matches the user's intent, then pass only the relevant source, media, voice, caption, music, avatar, and render fields.
The tool names are stable and descriptive, which makes this page easy for humans to scan and easy for AI agents to parse.
Revid handles scripting, visuals, voice, captions, music, rendering, exporting, and social publishing, so your agent can focus on intent, strategy, and iteration.
The `revid-cli` package is the fastest way to give shell-based agents, CI jobs, and local scripts access to Revid video creation. It supports exact API payloads, stable `--json` output, guided human setup, async waiting, exports, credits, docs, and project listing.
npm install -g revid-cli
export REVID_API_KEY="your_revid_api_key"
revid --helprevid create --prompt "A cinematic 30 second product launch video" --wait --json
revid create --payload payload.json --wait --json
revid projects --limit 10 --json
revid status <pid> --json
revid export <pid> --jsonThese examples map directly to Revid MCP and API workflows, from prompts and PDFs to motion transfer and music videos. Use them as a visual reference for what an agent can generate after calling `render_video`.
Every example starts with an input. Revid analyzes it, extracts what matters, and creates something new for you.
Viral Video
Your Version
The Revid MCP is a Streamable HTTP Model Context Protocol server that lets AI agents call Revid video creation tools, including rendering, status polling, exporting, publishing, voice cloning, and character management.
Add https://www.revid.ai/api/mcp as a remote MCP server or custom connector, then sign in with your Revid account when prompted. Revid supports OAuth 2.1 with PKCE and dynamic client registration, so hosted clients connect without pasting an API key.
Not for OAuth-capable clients like Claude, ChatGPT, Cursor, and VS Code: you just sign in with your Revid account. Header-configurable MCP clients, the Revid CLI, and direct API calls use a Revid API key from your account page.
Hosted remote MCP clients authenticate with OAuth 2.1 and PKCE, discovered automatically from the server's well-known metadata. Header-configurable clients can authenticate with a Revid API key using Authorization Bearer, x-revid-api-key, x-api-key, or key headers.
The Revid CLI is the revid-cli npm package. It lets humans, scripts, CI jobs, and AI agents create videos from the terminal using stable JSON output, exact API payload mode, render polling, exporting, and project commands.
Yes. The public API can be called directly from your backend. MCP wraps the same Revid video creation API for agent-native tool calling.
Renders consume credits from your Revid account or active workspace. Agents can call the calculate_credits tool, or the CLI credits command, with their intended payload before rendering to estimate the exact cost.