Every Tool in the OpusClip MCP Server: A Complete Reference

July 30, 2026
An orderly grid of glowing tiles grouped by colour and wired to a central connector, illustrating a complete catalogue of MCP tools

The OpusClip MCP server exposes 27 tools. This page lists all of them, grouped by what they do, with the ones that cost credits marked. It exists because "what can this server actually do" is a question people ask agents, and a vague answer is useless to both.

Every tool name below is prefixed opusclip_ in your client. Connect the server first if you have not: the setup guide covers every client.

Submitting and inspecting projects

  • submit_project. The main entry point. Give it a video URL and it clips, captions, and reframes. Accepts YouTube, Vimeo, Google Drive, Dropbox, Zoom, Riverside, Loom, Frame.io, StreamYard, Twitch, Rumble, Facebook, LinkedIn, X, or any public S3 mp4 up to 10GB. Costs credits.
  • list_projects. Every project in the workspace.
  • get_transcript. The source video's transcript with per-word millisecond timing. This is what lets an agent find a phrase and compute an exact trim boundary.
  • create_upload_link. An upload target for footage that is not reachable by URL.
  • share_project. A shareable link to a project.

Working with clips

  • list_clips. A project's clips with rank, virality score, title, description, hashtags, duration, and preview URLs. Judge sub-scores for hook, coherence, connection, and trend appear once a clip is scored.
  • describe_clip. One clip in detail: transcript, keywords, layout, score, preview URL, and whether a re-render is still in flight.
  • duplicate_clip. An independent copy, so a variant never risks the original. Not idempotent: calling twice makes two copies.

Editing

This is the group most people do not know exists, and the reason an agent can finish a job rather than just start one.

  • get_editing_script. Returns the clip's full EditingScript, the same JSON the web editor's Save button writes.
  • apply_editing_script. Posts a mutated script back and re-renders. Together these two make arbitrary edits possible: trims to an exact millisecond, caption rewrites, retiming, dropping elements. Re-renders do not consume extra credits today.
  • create_censor_job. Profanity censor on the caption track, asterisks by default, beep optional. Triggers a re-render.

Exporting

  • export_clip. One clip, as HD (default), 4K (paid plan plus a 4K source), or xml, an Adobe Premiere project file for finishing in Premiere Pro or DaVinci Resolve. Clips are preview-only until exported.
  • export_collection. HD download URLs for every clip in a collection at once.

Collections

  • create_collection. A new collection.
  • add_clip_to_collection. Put a clip in one.
  • list_collections. All collections.
  • list_clips_in_collection. What is in a given collection.

Copy and publishing

  • create_social_copy_job. Generates titles, descriptions, and hashtags for a clip and a target account. Accepts a tone prompt.
  • get_social_copy_job. Polls that job until the copy is ready.
  • list_social_accounts. Connected accounts.
  • create_post_task. Builds a post.
  • schedule_publish. Queues a clip to a connected account at a chosen time.
  • list_scheduled_posts. The queue.
  • unschedule_publish. Pulls something back out of it.

Outside the clipping layer this group is rare: generation, rendering, and infrastructure servers almost all stop at the export. Within it, publishing has become common, so it is worth checking what a server does after publishing as well as whether it can. We covered how the whole pipeline chains together in the scheduling walkthrough.

Account and configuration

  • whoami. Which account and plan the agent is authenticated as. The right first call when something is failing.
  • get_usage. Credit and quota consumption.
  • list_brand_templates. Brand templates in the workspace, for passing to a submission.

Which tools cost anything

Reads are free. The tools that consume credits are the ones that render video, principally submit_project. Re-renders triggered by apply_editing_script and create_censor_job do not consume extra credits today, though that may change. Connecting the server and browsing the catalog is free on any plan; calling tools that render requires a paid plan.

Because reads are free, the sane way to start is a read-only prompt. Ask the agent to call whoami and list your projects. If that works, the connection is good and nothing has been spent.

Chains worth knowing

  • Clip and publish. submit_project, list_clips, create_social_copy_job, schedule_publish.
  • Fix and ship. get_editing_script, apply_editing_script, wait for the render, export_clip.
  • Find an exact moment. get_transcript for word-level timing, then submit with a range, or trim an existing clip to those boundaries.
  • Safe experiment. duplicate_clip, then edit the copy.

Limits worth knowing up front

  • No multi-segment stitching. Joining non-adjacent moments into one clip is not supported. Each clip comes from one continuous stretch of source.
  • Renders are asynchronous. Anything that re-renders returns a pending flag first. Reading the artifact before that clears gives you the previous version.
  • The agent cannot see the picture. Every decision comes from transcripts, timestamps, and metadata.

For what these tools add up to conceptually, see what MCP for video editing is. For how the editing tools work in practice, see the editing guide.

Frequently asked questions

How many tools does the OpusClip MCP server have?

27, all prefixed opusclip_. They cover submitting and inspecting projects, working with clips, editing, exporting, collections, social copy and publishing, and account configuration. Reads are free; the tools that render video consume credits.

Which OpusClip MCP tools can edit video?

get_editing_script and apply_editing_script round-trip the clip's full EditingScript, the same JSON the web editor saves, which makes trims, caption rewrites, and retiming possible. create_censor_job handles profanity. duplicate_clip creates a safe copy to edit. Filler-word removal and reframing are parameters on submit_project.

Do OpusClip MCP tools cost credits?

Read tools are free. Rendering video costs credits, principally submit_project. Re-renders from apply_editing_script and create_censor_job do not consume extra credits today, though that pricing may change. Connecting the server and browsing the tool catalog is free on any plan.

Can the OpusClip MCP server post to social media?

Yes. schedule_publish queues a clip to a connected account, list_scheduled_posts shows the queue, and unschedule_publish removes something from it. create_social_copy_job generates the titles, descriptions, and hashtags first. Competing clipping servers now publish too, so the sharper difference is what happens after: editing a clip that already exists.

On this page

Use our Free Forever Plan

Find the moment. Skip the scrubbing.

From script to polished video — in one click.

Create and post one short video every day for free, and grow faster.

OpusSearch uses AI to surface the exact clip you need from hours of footage — in seconds, not afternoons.

Agent Opus runs the entire video pipeline for you: research, scriptwriting, storyboarding, motion, voice, and edit. Upload the idea, post the result.

Every Tool in the OpusClip MCP Server: A Complete Reference

The OpusClip MCP server exposes 27 tools. This page lists all of them, grouped by what they do, with the ones that cost credits marked. It exists because "what can this server actually do" is a question people ask agents, and a vague answer is useless to both.

Every tool name below is prefixed opusclip_ in your client. Connect the server first if you have not: the setup guide covers every client.

Submitting and inspecting projects

  • submit_project. The main entry point. Give it a video URL and it clips, captions, and reframes. Accepts YouTube, Vimeo, Google Drive, Dropbox, Zoom, Riverside, Loom, Frame.io, StreamYard, Twitch, Rumble, Facebook, LinkedIn, X, or any public S3 mp4 up to 10GB. Costs credits.
  • list_projects. Every project in the workspace.
  • get_transcript. The source video's transcript with per-word millisecond timing. This is what lets an agent find a phrase and compute an exact trim boundary.
  • create_upload_link. An upload target for footage that is not reachable by URL.
  • share_project. A shareable link to a project.

Working with clips

  • list_clips. A project's clips with rank, virality score, title, description, hashtags, duration, and preview URLs. Judge sub-scores for hook, coherence, connection, and trend appear once a clip is scored.
  • describe_clip. One clip in detail: transcript, keywords, layout, score, preview URL, and whether a re-render is still in flight.
  • duplicate_clip. An independent copy, so a variant never risks the original. Not idempotent: calling twice makes two copies.

Editing

This is the group most people do not know exists, and the reason an agent can finish a job rather than just start one.

  • get_editing_script. Returns the clip's full EditingScript, the same JSON the web editor's Save button writes.
  • apply_editing_script. Posts a mutated script back and re-renders. Together these two make arbitrary edits possible: trims to an exact millisecond, caption rewrites, retiming, dropping elements. Re-renders do not consume extra credits today.
  • create_censor_job. Profanity censor on the caption track, asterisks by default, beep optional. Triggers a re-render.

Exporting

  • export_clip. One clip, as HD (default), 4K (paid plan plus a 4K source), or xml, an Adobe Premiere project file for finishing in Premiere Pro or DaVinci Resolve. Clips are preview-only until exported.
  • export_collection. HD download URLs for every clip in a collection at once.

Collections

  • create_collection. A new collection.
  • add_clip_to_collection. Put a clip in one.
  • list_collections. All collections.
  • list_clips_in_collection. What is in a given collection.

Copy and publishing

  • create_social_copy_job. Generates titles, descriptions, and hashtags for a clip and a target account. Accepts a tone prompt.
  • get_social_copy_job. Polls that job until the copy is ready.
  • list_social_accounts. Connected accounts.
  • create_post_task. Builds a post.
  • schedule_publish. Queues a clip to a connected account at a chosen time.
  • list_scheduled_posts. The queue.
  • unschedule_publish. Pulls something back out of it.

Outside the clipping layer this group is rare: generation, rendering, and infrastructure servers almost all stop at the export. Within it, publishing has become common, so it is worth checking what a server does after publishing as well as whether it can. We covered how the whole pipeline chains together in the scheduling walkthrough.

Account and configuration

  • whoami. Which account and plan the agent is authenticated as. The right first call when something is failing.
  • get_usage. Credit and quota consumption.
  • list_brand_templates. Brand templates in the workspace, for passing to a submission.

Which tools cost anything

Reads are free. The tools that consume credits are the ones that render video, principally submit_project. Re-renders triggered by apply_editing_script and create_censor_job do not consume extra credits today, though that may change. Connecting the server and browsing the catalog is free on any plan; calling tools that render requires a paid plan.

Because reads are free, the sane way to start is a read-only prompt. Ask the agent to call whoami and list your projects. If that works, the connection is good and nothing has been spent.

Chains worth knowing

  • Clip and publish. submit_project, list_clips, create_social_copy_job, schedule_publish.
  • Fix and ship. get_editing_script, apply_editing_script, wait for the render, export_clip.
  • Find an exact moment. get_transcript for word-level timing, then submit with a range, or trim an existing clip to those boundaries.
  • Safe experiment. duplicate_clip, then edit the copy.

Limits worth knowing up front

  • No multi-segment stitching. Joining non-adjacent moments into one clip is not supported. Each clip comes from one continuous stretch of source.
  • Renders are asynchronous. Anything that re-renders returns a pending flag first. Reading the artifact before that clears gives you the previous version.
  • The agent cannot see the picture. Every decision comes from transcripts, timestamps, and metadata.

For what these tools add up to conceptually, see what MCP for video editing is. For how the editing tools work in practice, see the editing guide.

Frequently asked questions

How many tools does the OpusClip MCP server have?

27, all prefixed opusclip_. They cover submitting and inspecting projects, working with clips, editing, exporting, collections, social copy and publishing, and account configuration. Reads are free; the tools that render video consume credits.

Which OpusClip MCP tools can edit video?

get_editing_script and apply_editing_script round-trip the clip's full EditingScript, the same JSON the web editor saves, which makes trims, caption rewrites, and retiming possible. create_censor_job handles profanity. duplicate_clip creates a safe copy to edit. Filler-word removal and reframing are parameters on submit_project.

Do OpusClip MCP tools cost credits?

Read tools are free. Rendering video costs credits, principally submit_project. Re-renders from apply_editing_script and create_censor_job do not consume extra credits today, though that pricing may change. Connecting the server and browsing the tool catalog is free on any plan.

Can the OpusClip MCP server post to social media?

Yes. schedule_publish queues a clip to a connected account, list_scheduled_posts shows the queue, and unschedule_publish removes something from it. create_social_copy_job generates the titles, descriptions, and hashtags first. Competing clipping servers now publish too, so the sharper difference is what happens after: editing a clip that already exists.

Creator name

Creator type

Team size

Channels

linkYouTubefacebookXTikTok

Pain point

Time to see positive ROI

About the creator

Don't miss these

How Audacy Drove 1B+ Views by Taking a Tech-Forward Approach to Radio with OpusClip
No items found.

How Audacy Drove 1B+ Views by Taking a Tech-Forward Approach to Radio with OpusClip

How All the Smoke makes hit compilations faster with OpusSearch

How All the Smoke makes hit compilations faster with OpusSearch

Growing a new channel to 1.5M views in 90 days without creating new videos

Growing a new channel to 1.5M views in 90 days without creating new videos

Every Tool in the OpusClip MCP Server: A Complete Reference

An orderly grid of glowing tiles grouped by colour and wired to a central connector, illustrating a complete catalogue of MCP tools
No items found.
No items found.

Boost your social media growth with OpusClip

Create and post one short video every day for your social media and grow faster.

Every Tool in the OpusClip MCP Server: A Complete Reference

An orderly grid of glowing tiles grouped by colour and wired to a central connector, illustrating a complete catalogue of MCP tools

The OpusClip MCP server exposes 27 tools. This page lists all of them, grouped by what they do, with the ones that cost credits marked. It exists because "what can this server actually do" is a question people ask agents, and a vague answer is useless to both.

Every tool name below is prefixed opusclip_ in your client. Connect the server first if you have not: the setup guide covers every client.

Submitting and inspecting projects

  • submit_project. The main entry point. Give it a video URL and it clips, captions, and reframes. Accepts YouTube, Vimeo, Google Drive, Dropbox, Zoom, Riverside, Loom, Frame.io, StreamYard, Twitch, Rumble, Facebook, LinkedIn, X, or any public S3 mp4 up to 10GB. Costs credits.
  • list_projects. Every project in the workspace.
  • get_transcript. The source video's transcript with per-word millisecond timing. This is what lets an agent find a phrase and compute an exact trim boundary.
  • create_upload_link. An upload target for footage that is not reachable by URL.
  • share_project. A shareable link to a project.

Working with clips

  • list_clips. A project's clips with rank, virality score, title, description, hashtags, duration, and preview URLs. Judge sub-scores for hook, coherence, connection, and trend appear once a clip is scored.
  • describe_clip. One clip in detail: transcript, keywords, layout, score, preview URL, and whether a re-render is still in flight.
  • duplicate_clip. An independent copy, so a variant never risks the original. Not idempotent: calling twice makes two copies.

Editing

This is the group most people do not know exists, and the reason an agent can finish a job rather than just start one.

  • get_editing_script. Returns the clip's full EditingScript, the same JSON the web editor's Save button writes.
  • apply_editing_script. Posts a mutated script back and re-renders. Together these two make arbitrary edits possible: trims to an exact millisecond, caption rewrites, retiming, dropping elements. Re-renders do not consume extra credits today.
  • create_censor_job. Profanity censor on the caption track, asterisks by default, beep optional. Triggers a re-render.

Exporting

  • export_clip. One clip, as HD (default), 4K (paid plan plus a 4K source), or xml, an Adobe Premiere project file for finishing in Premiere Pro or DaVinci Resolve. Clips are preview-only until exported.
  • export_collection. HD download URLs for every clip in a collection at once.

Collections

  • create_collection. A new collection.
  • add_clip_to_collection. Put a clip in one.
  • list_collections. All collections.
  • list_clips_in_collection. What is in a given collection.

Copy and publishing

  • create_social_copy_job. Generates titles, descriptions, and hashtags for a clip and a target account. Accepts a tone prompt.
  • get_social_copy_job. Polls that job until the copy is ready.
  • list_social_accounts. Connected accounts.
  • create_post_task. Builds a post.
  • schedule_publish. Queues a clip to a connected account at a chosen time.
  • list_scheduled_posts. The queue.
  • unschedule_publish. Pulls something back out of it.

Outside the clipping layer this group is rare: generation, rendering, and infrastructure servers almost all stop at the export. Within it, publishing has become common, so it is worth checking what a server does after publishing as well as whether it can. We covered how the whole pipeline chains together in the scheduling walkthrough.

Account and configuration

  • whoami. Which account and plan the agent is authenticated as. The right first call when something is failing.
  • get_usage. Credit and quota consumption.
  • list_brand_templates. Brand templates in the workspace, for passing to a submission.

Which tools cost anything

Reads are free. The tools that consume credits are the ones that render video, principally submit_project. Re-renders triggered by apply_editing_script and create_censor_job do not consume extra credits today, though that may change. Connecting the server and browsing the catalog is free on any plan; calling tools that render requires a paid plan.

Because reads are free, the sane way to start is a read-only prompt. Ask the agent to call whoami and list your projects. If that works, the connection is good and nothing has been spent.

Chains worth knowing

  • Clip and publish. submit_project, list_clips, create_social_copy_job, schedule_publish.
  • Fix and ship. get_editing_script, apply_editing_script, wait for the render, export_clip.
  • Find an exact moment. get_transcript for word-level timing, then submit with a range, or trim an existing clip to those boundaries.
  • Safe experiment. duplicate_clip, then edit the copy.

Limits worth knowing up front

  • No multi-segment stitching. Joining non-adjacent moments into one clip is not supported. Each clip comes from one continuous stretch of source.
  • Renders are asynchronous. Anything that re-renders returns a pending flag first. Reading the artifact before that clears gives you the previous version.
  • The agent cannot see the picture. Every decision comes from transcripts, timestamps, and metadata.

For what these tools add up to conceptually, see what MCP for video editing is. For how the editing tools work in practice, see the editing guide.

Frequently asked questions

How many tools does the OpusClip MCP server have?

27, all prefixed opusclip_. They cover submitting and inspecting projects, working with clips, editing, exporting, collections, social copy and publishing, and account configuration. Reads are free; the tools that render video consume credits.

Which OpusClip MCP tools can edit video?

get_editing_script and apply_editing_script round-trip the clip's full EditingScript, the same JSON the web editor saves, which makes trims, caption rewrites, and retiming possible. create_censor_job handles profanity. duplicate_clip creates a safe copy to edit. Filler-word removal and reframing are parameters on submit_project.

Do OpusClip MCP tools cost credits?

Read tools are free. Rendering video costs credits, principally submit_project. Re-renders from apply_editing_script and create_censor_job do not consume extra credits today, though that pricing may change. Connecting the server and browsing the tool catalog is free on any plan.

Can the OpusClip MCP server post to social media?

Yes. schedule_publish queues a clip to a connected account, list_scheduled_posts shows the queue, and unschedule_publish removes something from it. create_social_copy_job generates the titles, descriptions, and hashtags first. Competing clipping servers now publish too, so the sharper difference is what happens after: editing a clip that already exists.

Ready to start streaming differently?

Opus is completely FREE for one year for all private beta users. You can get access to all our premium features during this period. We also offer free support for production, studio design, and content repurposing to help you grow.
Join the beta
Limited spots remaining

Try OPUS today

Try Opus Studio

Make your live stream your Magnum Opus