Clipmaster Mcp

io.github.n0Sp00nPublished by GitHub account n0Sp00nv0.1.1Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyProductivity & WorkflowMedia & Design

Overview

AI-generated overview

ClipMaster MCP lets an assistant import YouTube videos, generate AI clips, export them and schedule social posts through the ClipMaster API.

What you can do
Import a YouTube video by URL and start AI clip generation, then check processing status and list projects and generated clips with their AI metadata, or open one clip's full detail. Render a clip with its saved settings and poll the export until a temporary download link appears. Browse cross-project clip compilations. List connected social channels, schedule an export to publish, and view the posting calendar for a date range.
When to use it
Useful when you already work with ClipMaster and want an assistant to drive the clipping pipeline from chat: kicking off imports, watching processing, reviewing clips, exporting renders and planning scheduled posts.
Requirements
Runs locally as a Python package (Python 3.10+) over stdio, installed with pipx or run with uvx. Needs a ClipMaster API key on a paid plan, supplied through the CLIPMASTER_API_KEY environment variable or a key file under the user's config directory. Network access to the ClipMaster public API is required; the API base URL can be overridden with CLIPMASTER_API_BASE.
Before you install
The API key (CLIPMASTER_API_KEY) is a live credential for a paid account; keep it out of shared config files where possible. Triggering an export charges tokens on the account, and scheduling posts publishes content to connected social channels. Video ingestion is URL-only, and account management such as keys and billing is not available.

Installation

In SourceWeft

  1. Open Clipmaster Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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 varRequiredMeaning
CLIPMASTER_API_KEYyes*Your cm_live_… API key
CLIPMASTER_API_BASEnoOverride 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

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

Claude Desktop

claude_desktop_config.json:

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

Tools

ToolWhat 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

Source: README.md at commit 27e7faa

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.