The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Clipmaster MCP listing page.
mcp-name: io.github.n0Sp00n/clipmaster-mcp
MCP (Model Context Protocol) server for ClipMaster — AI video clipping at clipmaster.app. It exposes the ClipMaster public API as tools, so Claude Desktop, Claude Code, and any MCP client can ingest videos, monitor processing, browse clips, trigger exports, and schedule posts.
https://api.clipmaster.app/api/v1) with
the user's API key — no database access, no internal services.From this repo checkout:
| Env var | Required | Meaning |
|---|---|---|
CLIPMASTER_API_KEY | yes* | Your cm_live_… API key |
CLIPMASTER_API_BASE | no | Override the API base URL (default https://api.clipmaster.app/api/v1) |
*Instead of the env var you can put the key in ~/.config/clipmaster/key —
this keeps it out of client config files and shell history:
The env var wins when both are set.
claude_desktop_config.json:
| Tool | What it does |
|---|---|
ingest_youtube(url, orientation?, user_query?, compilation_format?) | Import a YouTube video, start clip generation |
get_status(project_id) | Processing progress / state |
list_projects() | The user's projects |
list_clips(project_id) | Generated clips with AI metadata |
get_clip(project_id, clip_id) | Full detail for one clip |
trigger_export(project_id, clip_id) | Render a clip with its saved settings (charges tokens) |
get_export_status(export_id) | Poll an export; completed → temporary download_url |
list_compilations(source_project_id?) / get_compilation(id) | Cross-project clip collections |
list_social_accounts() | Connected channels for scheduling |
schedule_post(...) | Schedule an export to publish (idempotent on retry) |
list_scheduled_posts(from_date, to_date) | Posting calendar range |