Skip to main content
Automate your OpusClip workspace from Claude.ai: browse projects and clips, pull transcripts, organize collections, edit clips, export HD downloads, and prepare posts for your connected social accounts — all from natural-language prompts. OpusClip is listed in the Claude connector directory at claude.ai/directory/opusclip — add it from there in one click.
Nothing is published without your confirmation. On this connector, posting, scheduling, cancelling a scheduled post, and sharing a project do not happen when the agent calls the tool. Each call returns a link you open in OpusClip, where you review the exact request and confirm it yourself. See Publishing requires your confirmation.
The Claude Connector does not support media generation. It exposes no image, video, or audio generation tools, and the generation options of the workflow tools — clip dubbing, for example — are not available here either. If you need thumbnail generation or dubbing, or you are configuring an IDE or CLI host such as Cursor, Cline, or Claude Code, use the MCP Server instead.
Any OpusClip account can complete the OAuth flow and view the tool catalog. Calling a tool requires Pro Beta, Max, or Business plan access; without it, the host returns an upgrade prompt. See Limitations for the plan caps.

​
Install

Open OpusClip in the Claude connector directory and click Add, then complete the OAuth sign-in. You can also reach it from Settings → Connectors in Claude.ai by searching for OpusClip. Start a new conversation and try List my recent OpusClip projects. Adding an endpoint by hand as a custom connector is not the route here. If your host is not Claude.ai, or you need generation tools, use the MCP Server at https://mcp.opus.pro/mcp — it carries the full tool catalog. If you belong to more than one OpusClip org, you pick the org on the OAuth consent screen while connecting. That choice is fixed for the life of the connection: there is no tool that switches orgs mid-conversation. To work in a different org, disconnect the connector and reconnect, choosing that org on the consent screen. Ask the agent to run whoami to see which org it is currently acting in.

​
Publishing requires your confirmation

Four tools on this connector never commit anything on their own: Calling one returns status: "requires_approval", committed: false, and an approval_url. Opening that link in OpusClip shows you the exact request — the clip, the account, the time, and the caption the agent wrote — and the action runs only after you confirm it there, in your own signed-in session. What this means in practice:
  • The agent cannot post on your behalf. Not by mistake, not in the background, not while you are away from the conversation.
  • A batch costs one confirmation. If the agent prepares several posts, it can combine them into a single link, and confirming once runs all of them.
  • The link is yours alone. It works only for the account that made the request, signed in. Forwarding it to a colleague does nothing.
  • Ignoring the link is how you decline. There is no reject button to hunt for. Links expire on their own — one hour for an immediate post, up to the scheduled time for a scheduled one, twenty-four hours for sharing and cancelling — and an expired link has no effect.
  • Credits are spent when you confirm, not when the agent calls the tool.
This is separate from the approval prompt Claude itself shows before running a write tool. That prompt is your host asking whether the agent may make the call; this confirmation is OpusClip asking whether the action may actually happen. Both apply to the four tools above.
The MCP Server at mcp.opus.pro behaves differently: there the same four tools commit directly, because you configured that endpoint yourself rather than reaching it through a listed connector.

​
Tool catalog

The connector exposes the 28 tools below — 26 workflow tools plus two deprecated no-op signposts kept for compatibility.
  • opusclip_whoami — identity check for the connected org
  • opusclip_get_usage — show the org’s current API usage against its cap
  • opusclip_list_projects — list recent clip projects
  • opusclip_list_clips — list clips inside a project
  • opusclip_describe_clip — fetch a single clip’s detail (transcript, layout, render status)
  • opusclip_list_collections — list collections
  • opusclip_list_clips_in_collection — list clips inside a collection
  • opusclip_list_brand_templates — list brand templates
  • opusclip_list_social_accounts — list connected social accounts
  • opusclip_list_scheduled_posts — list scheduled and recent posts (returns the schedule_id that unscheduling requires)
  • opusclip_get_transcript — fetch a project’s source-video transcript
  • opusclip_get_social_copy_job — fetch a social copy job
  • opusclip_submit_project — clip a video from YouTube, Vimeo, Google Drive, Dropbox, Zoom, Loom, and other supported sources · consumes credits
  • opusclip_create_upload_link — get a signed URL to upload a local video
  • opusclip_edit_clip — apply named editing operations in one call: caption and emoji toggles, filler-word and pause removal, section trim / split / drop / reorder, phrase cut and caption fix, caption styling, text overlays, emoji placement, and undo · one preview re-render per call · see Editing a clip
  • opusclip_create_censor_job — bleep or mask flagged content · consumes credits
  • opusclip_create_collection — create a collection
  • opusclip_add_clip_to_collection — add a clip to a collection
  • opusclip_export_clip — get one clip’s HD download URL (ready / rendering / unavailable)
  • opusclip_export_collection — get HD download URLs for every clip in a collection
  • opusclip_duplicate_clip — copy a clip to <title> (Copy); free, no re-render
  • opusclip_create_social_copy_job — generate platform-specific social copy
  • opusclip_share_project — request making a project publicly viewable · returns an approval link
  • opusclip_create_post_task — request posting a clip to a connected social account · returns an approval link
  • opusclip_schedule_publish — request scheduling a clip for a future time · returns an approval link
  • opusclip_unschedule_publish — request cancelling a scheduled post · returns an approval link
  • opusclip_get_editing_script — deprecated; returns no editing script, only a pointer to opusclip_edit_clip
  • opusclip_apply_editing_script — deprecated; applies nothing and re-renders nothing, only a pointer to opusclip_edit_clip
Editing scripts were retired as a surface; opusclip_edit_clip is the only editing route. These two names remain so an agent holding an older tool list is redirected instead of hitting a hard error.
list_clips and describe_clip return preview URLs only — the HD download URL comes from export_clip (one clip) or export_collection (a collection).

​
Editing a clip

opusclip_edit_clip is the entire editing surface. It takes a list of named operations, applies them in order, and re-renders the preview once — so batching related edits into a single call is cheaper and faster than one call per change (“remove the filler words and turn the captions off” is two ops, one render). Removal ops shorten the clip; video, captions, and audio stay in sync. dub is the one operation this connector does not carry — it is voice generation, and it lives on the MCP Server. Ask before editing. Pass dryRun: true and the tool reports what the batch would do, saving and rendering nothing. With an empty ops array it becomes a capability query — what does this clip actually have? — which is the cheapest way for an agent to orient before it proposes an edit. See the result without waiting for the render. Every result carries an editor_deep_link. Opening it shows the edited clip straight away, because the web editor rebuilds its preview from the saved edit rather than waiting on the render. The rendered preview follows asynchronously: the result returns render_pending: true, and describe_clip reports when it clears. No HD render is started — HD renders on demand at export_clip. Undo has a 72-hour window. undo must be the only operation in the call, and calling it twice redoes. It is refused if the clip changed after that edit — a save from the web editor, for example — so newer work is never discarded.

​
Try it

Get clips from a video
Clip this YouTube video and give me the top 5 best clips https://youtube.com/watch?v=...
Inline edits
Cut the filler words out of clip 3 and make the captions yellow.
What could you change about clip 2? Don’t edit it yet.
Publish
Schedule my latest clip to post tomorrow at 9am.
The agent prepares the schedule and hands back a confirmation link. Open it, check the clip, account, time, and caption, and confirm — the post is scheduled at that moment, not before.

​
Troubleshooting

Sign in with the same identity provider used to create the OpusClip account (email, Google, or Apple).
The org does not have the API entitlement. Pro Beta and Max orgs receive it automatically. Otherwise, contact sales.
The one you picked on the OAuth consent screen when you connected. It is fixed for the life of the connection, and no tool can switch it. To act in a different org, disconnect the connector and reconnect, choosing that org while signing in. whoami reports the current one.
Check whether it handed you an approval link. Nothing is posted, scheduled, or shared until you open that link and confirm. If the link has expired, ask the agent to make the request again — it will return a fresh one.
Hosts refresh tokens automatically. If refresh fails persistently, remove the connector and re-add it.
403 indicates the monthly cap (15h / 900 credits per workspace) has been hit. The cap resets on the first day of the next month (UTC). 429 indicates the concurrent-project limit (4) has been hit and clears as in-flight projects finish. See Limitations.
Tools consume credits and inherit the Pro Beta & Max caps (15h monthly, 10-credit per-project floor, 4 concurrent projects). For the four tools that need your confirmation, credits are spent when you confirm, not when the agent calls the tool. See Limitations.

​
What’s next

  • Using Cursor, Cline, Claude Code, or another MCP host? See the MCP Server.
  • Prefer an API-key code package? See the Skill.
  • Need higher limits? Contact sales.