Clipmaster MCP

AI video clipping with ClipMaster (clipmaster.app): clips, exports, scheduling.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "clipmaster-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "clipmaster-mcp"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

clipmaster-mcp

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.

Talks ONLY to the public REST API (https://api.clipmaster.app/api/v1) with the user's API key — no database access, no internal services.
Ingestion is URL-only by design (streaming a local file through an LLM tool call is impractical). Account management (keys, billing, OAuth connects) is excluded; the API rejects those routes for key auth anyway.

Requirements

Python 3.10+
A ClipMaster API key (paid plans): web app → Settings → API access

Install

From this repo checkout:

bash

pipx install ./clipmaster-mcp
# or, without installing:
uvx --from ./clipmaster-mcp clipmaster-mcp

Configure

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:

bash

mkdir -p ~/.config/clipmaster && printf '%s' 'cm_live_...' > ~/.config/clipmaster/key && chmod 600 ~/.config/clipmaster/key

The env var wins when both are set.

Claude Code

Terminal

claude mcp add clipmaster -e CLIPMASTER_API_KEY=cm_live_... -- clipmaster-mcp

Claude Desktop

claude_desktop_config.json:

config.json

{
  "mcpServers": {
    "clipmaster": {
      "command": "clipmaster-mcp",
      "env": { "CLIPMASTER_API_KEY": "cm_live_..." }
    }
  }
}

Tools

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

Development

bash

python3 -m venv .venv && .venv/bin/pip install -e ./clipmaster-mcp pytest
.venv/bin/pytest clipmaster-mcp/tests -q

Read the full README →View source on GitHub →

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Clipmaster MCP

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "clipmaster-mcp": { "command": "npx", "args": ["-y", "clipmaster-mcp"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/clipmaster-mcp?style=directory)](https://allmcps.com/mcp/clipmaster-mcp)

HTML Embed

<a href="https://allmcps.com/mcp/clipmaster-mcp"><img src="https://allmcps.com/api/badge/clipmaster-mcp?style=directory" alt="Clipmaster MCP on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Clipmaster MCP →Install in Claude Desktop Install in Cursor Install in VS Code

Documentation Overview

clipmaster-mcp

mcp-name: io.github.n0Sp00n/clipmaster-mcp

Talks ONLY to the public REST API (https://api.clipmaster.app/api/v1) with the user's API key — no database access, no internal services.
Ingestion is URL-only by design (streaming a local file through an LLM tool call is impractical). Account management (keys, billing, OAuth connects) is excluded; the API rejects those routes for key auth anyway.

Requirements

Python 3.10+
A ClipMaster API key (paid plans): web app → Settings → API access

Install

From this repo checkout:

bash

pipx install ./clipmaster-mcp
# or, without installing:
uvx --from ./clipmaster-mcp clipmaster-mcp

Configure

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:

bash

mkdir -p ~/.config/clipmaster && printf '%s' 'cm_live_...' > ~/.config/clipmaster/key && chmod 600 ~/.config/clipmaster/key

The env var wins when both are set.

Claude Code

Terminal

claude mcp add clipmaster -e CLIPMASTER_API_KEY=cm_live_... -- clipmaster-mcp

Claude Desktop

claude_desktop_config.json:

config.json

{
  "mcpServers": {
    "clipmaster": {
      "command": "clipmaster-mcp",
      "env": { "CLIPMASTER_API_KEY": "cm_live_..." }
    }
  }
}

Tools

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

Development

bash

python3 -m venv .venv && .venv/bin/pip install -e ./clipmaster-mcp pytest
.venv/bin/pytest clipmaster-mcp/tests -q