OpusClip

@mindstone/mcp-server-opus-video-clip

OpusClip MCP server for Model Context Protocol hosts. Turn long-form videos into short clips, manage projects, collections, censor jobs, and scheduled social posts through the OpusClip API.

Requirements

• Node.js 20+
• npm
• An OpusClip API key (https://app.opus.pro/settings/integration-tokens)

One-click install

After clicking the button, your host will prompt you to fill: OPUS_API_KEY, OPUS_API_TIMEOUT_MS, OPUS_UPLOAD_TIMEOUT_MS, OPUS_BRIDGE_TIMEOUT_MS.

Manual config for Claude Desktop / Claude Code / Goose / Continue.dev (OpusClip)

{

"mcpServers": { "OpusClip": { "command": "npx", "args": [ "-y", "@mindstone/mcp-server-opus-video-clip" ], "env": { "OPUS_API_KEY": "", "OPUS_API_TIMEOUT_MS": "120000", "OPUS_UPLOAD_TIMEOUT_MS": "600000", "OPUS_BRIDGE_TIMEOUT_MS": "30000" } } } }

Quick Start

Install & build

cd <path-to-repo>/connectors/opus-video-clip

npm install npm run build

npx (once published)

npx -y @mindstone/mcp-server-opus-video-clip

Local

node dist/index.js

Configuration

Environment variables

• OPUS_API_KEY — OpusClip API key
• MCP_HOST_BRIDGE_STATE — optional path to a host bridge state file used for credential management
• MINDSTONE_REBEL_BRIDGE_STATE — backwards-compatible alias for MCP_HOST_BRIDGE_STATE
• OPUS_API_TIMEOUT_MS — outbound HTTP timeout for general Opus API calls (default 120000 ms, max 30 min)
• OPUS_UPLOAD_TIMEOUT_MS — per-chunk HTTP timeout for GCS resumable upload (default 600000 ms, max 30 min)
• OPUS_BRIDGE_TIMEOUT_MS — HTTP timeout for the optional host-app bridge (default 30000 ms, max 30 min)
• MCP_WORKSPACE_PATH — workspace directory for local-file access (see below)

Local-file sandbox and input permissions

opus_download_clip writes are confined to a workspace sandbox: MCP_WORKSPACE_PATH when set, otherwise the system temp directory. Paths outside the sandbox — including .. traversal and symlinks that escape it — are refused. For standalone clients, including clients that do not negotiate files/readModes version 1, opus_upload_video reads follow these same restrictions: place source videos inside the workspace (or temp) directory before uploading. With negotiated version 1, the host selects a mode for each call: in central mode, input reads use only the host-authorized canonical path described under Host-authorized local inputs; in standalone mode, the standalone restrictions apply. In every mode, pick download targets inside the workspace (or temp) directory.

Host configuration examples

Claude Desktop / Cursor

{

"mcpServers": { "OpusClip": { "command": "npx", "args": ["-y", "@mindstone/mcp-server-opus-video-clip"], "env": { "OPUS_API_KEY": "your-api-key" } } } }

Local development (no npm publish needed)

{

"mcpServers": { "OpusClip": { "command": "node", "args": [" /connectors/opus-video-clip/dist/index.js"], "env": { "OPUS_API_KEY": "your-api-key" } } } }

Tools (22)

Configuration

• configure_opus_api_key — Configure the OpusClip API key

Brand templates

• opus_get_brand_templates — List brand templates

Project lifecycle

• opus_create_project — Submit a long-form video URL for clipping (marked destructive)
• opus_get_project — Retrieve a project's status, metadata, and clips
• opus_get_clips — Retrieve clips generated for a project (surfaces pagination metadata: total/next/limit)
• opus_share_project — Update a project's sharing visibility (marked destructive)

Upload

• opus_upload_video — Upload a local video file and create a clip project (orchestrates the 4-step GCS resumable upload; standalone-mode reads confined to the workspace sandbox, central-mode reads use only the host-authorized canonical path; marked destructive)

Downloads

• opus_download_clip — Download an exported clip MP4 to a local file inside the workspace sandbox. Only OpusClip CDN / Google Cloud Storage hosts are accepted; hostnames are DNS-resolved and every resolved address must be public

Censor jobs

• opus_create_censor_job — Create a censor job for a clip (marked destructive)
• opus_get_censor_job_status — Poll the status of a censor job

Collections

• opus_create_collection — Create a clip collection (marked destructive)
• opus_get_collections — List your collections
• opus_export_collection — Export all clips from a collection
• opus_delete_collection — Delete a collection (clips themselves are preserved)

Collection contents

• opus_add_clip_to_collection — Add a clip to an existing collection
• opus_remove_clip_from_collection — Remove a clip from a collection (uses Opus's POST-to-delete idiom)

Social posting

• opus_get_social_accounts — List connected social accounts
• opus_create_social_copy_job — Generate platform-specific social copy for a clip
• opus_get_social_copy_job — Retrieve the result of a social-copy job
• opus_publish_post — Publish a clip to a connected social account immediately (marked destructive)
• opus_schedule_post — Schedule a clip for future publishing (marked destructive)
• opus_cancel_scheduled_post — Cancel a scheduled social post

External text returned by the Opus API (project/clip titles, template and collection names, social account display names, generated social copy, upstream error strings and error bodies, job statuses, and continuation tokens) is wrapped in envelopes so the model treats it as data, not instructions.

Licence

FSL-1.1-MIT — Functional Source License, Version 1.1, with MIT future licence. The software converts to MIT licence on 2030-05-19.

Host-authorized local inputs

files/readModes version 1 is an experimental extension used by these connectors, not part of the MCP standard. A compatible host (the app running the connector) decides which input files a tool call may read. The connector opens only the host-approved physical path, after resolving symlinks. The host supplies this permission information with each call; it is not a tool argument you need to set. Missing or invalid permission information, or a file absent from the approved list, stops the read.

Clients that do not negotiate this extension keep the connector's existing standalone file restrictions. This extension changes input-read permissions; existing output destinations, upload formats, size limits and file checks apply.