OpenClip + Claude MCP Integration | Video Editing from Claude - OpenClip
OpenClipOpenClip
Get started
Claude Integration

OpenClip + Claude MCP Integration

This is the setup reference for Claude: connect the OpenClip MCP server in Claude web, Claude Desktop, or Claude Code, sign in once with OAuth, and Claude gains twenty-eight video tools, from submit_video to generate_ugc. Setup takes about five minutes; no API key is involved.

Claude
AI assistant

Prerequisites

  • An OpenClip account with an active subscription
  • Claude on the web, Claude Desktop, or Claude Code

Setup Steps

1

Add the connector in Claude

In Claude web or Desktop, open Settings, then Connectors, and choose "Add custom connector". Paste the OpenClip server URL, https://openclip.app/mcp. It is one public URL, the same for every account; your identity comes from the sign-in, not the address.

2

Or add it in Claude Code

In a terminal, run: claude mcp add --transport http openclip https://openclip.app/mcp and then /mcp inside Claude Code to start the sign-in. The same server powers both paths, so tools behave identically in the app and the CLI.

3

Sign in with your OpenClip account

Claude opens an OAuth 2.1 authorization flow: sign in to OpenClip, approve access, and the connection is bound to your account and team with a scoped mcp:use token. There is no API key to create, paste, or rotate.

4

Run a first job

Ask Claude to turn a video into clips: it calls submit_video with your URL, polls get_video_status while OpenClip processes, presents the detected moments from list_clips, and renders your picks with render_clip. See the Claude workflow guide for a full worked session.

Features

Every Claude surface

One server covers Claude web, Claude Desktop, and Claude Code. Connect where you work; the tool surface is identical everywhere.

OAuth, not API keys

Dynamic client registration means Claude sets itself up and you just approve a sign-in. Access is revocable per user without touching anyone else's connection.

Twenty-eight real tools

Submission (submit_video, create_upload), monitoring (get_video_status, get_render_status), review (list_clips, get_transcript), output (render_clip, list_caption_presets), and account tools (get_account, get_usage).

Brief in plain language

Give Claude the audience, platform, and clip goal in one message. It maps your intent onto the right tool sequence without you learning any syntax.

Untrusted content isolation

Moment titles and transcripts come from the video and arrive marked as untrusted content, so Claude treats them as data for your review, never as instructions.

Repeatable via agents

Ask Claude to save your preferences with create_agent (caption preset, tracker, branding) and every future episode gets identical treatment.

Frequently Asked Questions

It lets Claude operate OpenClip's clipping pipeline through MCP: submit long videos, monitor processing, review detected viral moments, render captioned vertical clips, and pull transcripts, all from a conversation.

No. The connection is OAuth 2.1: you sign in with your normal OpenClip account from inside Claude and approve access once. Revoking is equally simple: remove the connector.

https://openclip.app/mcp for every account and every Claude surface. There is no per-workspace URL; your team binding comes from the OAuth sign-in.

Paste a podcast or webinar URL and ask Claude for five clips for your platform of choice. The full worked example in our Claude workflow guide shows the exact conversation and what comes back.

Edit videos from Claude with OpenClip

Add the connector, sign in once, and ask Claude for your first batch of captioned clips.

Get Started Free

Related Pages