D
Dani Kalmar
Please add an official MCP server for OpusClip so AI assistants and agents (Claude, Claude Code, Cursor, and other MCP-compatible clients) can connect to OpusClip directly and drive it in natural language.
Right now the options for programmatic use are the REST API (Business plan only) and webhooks. Webhooks are one-way and the API is gated behind the top tier. An MCP server would give every plan a clean, two-way, agent-native way to work with OpusClip, which is quickly becoming the standard interface for AI tools.
Use cases this would unlock:
* Kick off a clipping job from an agent (paste a long video URL or pick an upload, set aspect ratio, language, and clip length).
* Read finished clips and their metadata (download URL, virality score, AI captions, hashtags, title, timestamps).
* Route clips into downstream tools from an agent workflow, for example scheduling them into Buffer, Hootsuite, or Later, or posting to socials.
* Manage the built-in scheduler and content calendar (list, create, reschedule, or cancel scheduled posts).
* Check account usage and remaining quota.
Suggested MCP tools to expose:
* list_projects, get_project, list_clips, get_clip
* create_clipping_job, get_job_status
* get_clip_download_url, get_clip_captions
* list_scheduled_posts, create_scheduled_post, update_scheduled_post
* get_account_usage
Auth: OAuth or a scoped API key, honoring the user's plan and permissions.
Why it matters: Teams increasingly run their whole content pipeline through an AI assistant. A native MCP server would make OpusClip the clipping layer that plugs straight into those agent workflows, instead of requiring custom webhook plumbing or a Business-tier API. It would also match the direction competitors and adjacent tools are moving.