Connect over MCP

OpenClip's full remote MCP server exposes 32 tools for clipping, uploads, captions for any short video, media utilities, UGC, account usage, and Brand management. It works in Claude, Cursor, Perplexity, and other clients that support remote MCP servers. Two curated endpoints serve app directories: ChatGPT exposes 13 tools for clipping, documentation search, and short-video captions. Claude exposes 27 tools, adding media editing, transcription, upload-based clipping, usage, and saved agent management. See MCP tools for every scope.

The full server supports two authentication methods. Pick one.

Option 1: OAuth (recommended)

The primary endpoint is:

https://openclip.app/mcp

It uses OAuth 2.1 with dynamic client registration, so there is no key to copy. Paste the URL into your client and sign in with your OpenClip account when prompted.

Claude Desktop / claude.ai: Settings → Connectors → Add custom connector → paste https://openclip.app/mcp → Connect → sign in.

Claude Code:

claude mcp add --transport http openclip https://openclip.app/mcp
# then run /mcp to sign in

Cursor (.cursor/mcp.json):

{
  "mcpServers": {
    "openclip": { "url": "https://openclip.app/mcp" }
  }
}

Cursor runs the OAuth flow when it first connects. Other clients with a "custom connector" or "remote MCP server" option work the same way: paste the URL, sign in.

ChatGPT app endpoint

The OpenClip app for ChatGPT connects to:

https://openclip.app/mcp/app

It uses the same OAuth sign-in as the full server and exposes 13 tools: account details, documentation search, video submission and listing, processing and render status, clip listing and rendering, caption presets, supported providers, transcripts, upload creation, and whole-video captioning.

For an attached ChatGPT video up to three minutes, select it with the file parameter of create_upload. ChatGPT expects the attachment reference and supplies the download metadata automatically. OpenClip imports the bytes and returns uploaded: true; then call caption_video. For other local files, create_upload returns uploaded: false and a presigned URL. The client must PUT the actual bytes before captioning. Creating that upload record alone does not transfer the file. The ChatGPT endpoint does not expose complete_upload. For URL-based clipping, use submit_video; for full upload/clipping workflows and other utilities, use the full MCP server.

The ChatGPT app explains missing credits, inactive subscriptions, and failed payments without checkout links or subscription buttons. A video in pending_credits is paused, so stop polling until its account restriction has been resolved. The full MCP server retains its normal billing recovery links.

Completed videos can have zero detected clips. For previews or rendering, choose a completed video with available clips and confirm the result of list_clips. Clips appear in source order, so compare virality_score when choosing the highest-scoring moment. Rendering stays within your team's visible clips and may replace that moment's existing final render.

Claude endpoint

OpenClip's Claude connector and plugin connect to:

https://openclip.app/mcp/claude

It uses the same OAuth sign-in as the full server and exposes 27 tools. Alongside clipping, captioning, and documentation search, it supports transcription, video/image editing, format conversion, thumbnail extraction, credit usage, and saved processing agents. In Claude on the web, desktop, and mobile, video status, clip, and render results appear as an interactive card with playable clip previews and a render button. Claude Code shows the same results as text.

To add it yourself, go to Settings → Connectors → Add custom connector in Claude, paste https://openclip.app/mcp/claude, and sign in. AI UGC tools and background removal remain available only on the full server at https://openclip.app/mcp.

create_upload on Claude and the full MCP server accepts video, audio, and image files. It returns uploaded: false and a presigned PUT URL; a client with authorized file access must transfer the actual bytes before processing. Claude apps without file transfer should use existing OpenClip media or upload through the matching tool at openclip.app. The video id also identifies audio/image uploads; pass it as file to image editing. Uploading alone starts no processing.

For paid video clipping, call complete_upload after PUT. For transcription, media utilities, or whole-video captions, skip complete_upload and call the chosen tool directly. Audio and image files cannot start the clipping pipeline. Use list_agents to find a saved agent and pass its id as agent to submit_video. Call describe_agent_settings before changing advanced settings; logo uploads require a separate PUT followed by set_agent_logo.

Like the ChatGPT app, the Claude endpoint explains missing credits and failed payments without checkout links. A pending_credits video stays paused until the account restriction is resolved in OpenClip.

Option 2: Bearer token

For header-only or programmatic clients that can't run an OAuth flow, use the token endpoint:

https://openclip.app/mcp/key

Generate a token at https://openclip.app/settings/connect ("Generate MCP token"). It is shown once, so store it safely. Send it as an Authorization: Bearer header on every request.

Claude Code:

claude mcp add --transport http openclip https://openclip.app/mcp/key \
  --header "Authorization: Bearer <token>"

Cursor (.cursor/mcp.json):

{
  "mcpServers": {
    "openclip": {
      "url": "https://openclip.app/mcp/key",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

Scopes

All four endpoints require the mcp:use scope. OAuth tokens for /mcp, /mcp/app, and /mcp/claude request it automatically, and bearer tokens minted for /mcp/key include it. A token without it is rejected with a 403.

Verify the connection

Ask your assistant to call get_account. It returns your account email, team, and remaining credits. If that works, the connection is good; try "turn this YouTube video into clips" next.

Agent Skills

Skills teach your agent how to drive OpenClip well: the async polling loops, the upload gotchas, and the per-tool parameter reference. There are two ways to install them.

skills CLI (recommended)

npx skills add OpenClip-App/agent-skills

This pulls the full published set from OpenClip-App/agent-skills and works with Claude Code, Codex, Cursor, and 70+ other agents. Alongside the umbrella openclip skill you get focused ones for clipping, captions, transcription, media conversion, video editing, thumbnails, background removal, repurposing, and UGC ads. Install only the ones you want.

Claude Code can install the skills and wire up the MCP server in one step instead:

/plugin marketplace add OpenClip-App/agent-skills
/plugin install openclip@openclip

Zip download

If you would rather not use Node, download the bundle at https://openclip.app/mcp/skill. It is a zip containing the umbrella skill's SKILL.md and reference.md. Unzip it into your agent's skills directory (for Claude Code: .claude/skills/openclip/).

Notes

• Processing is asynchronous. Your agent submits work, then polls status tools; nothing is pushed to it.
• The clipping pipeline needs credits, funded by a subscription or a running trial. A submission from a team with neither is accepted and parked: submit_video returns a pending_credits status instead of failing, and the video processes once the team is entitled. The full server's media utilities (transcribe, convert, edit, thumbnails, background removal) are free with just an account. caption_video uses no credits and follows the Quick Captions export allowance.
• Manage or revoke your MCP token any time at https://openclip.app/settings/connect.