JustClip

justclip-mcp

Clip any video from Claude, Cursor or any MCP client. Video downloads run on your machine before upload to JustClip. Same credits, same clips, same plan as the app.

Why it's different

JustClip runs yt-dlp on your machine, then uploads the video for processing. This avoids relying on a datacenter connection to download YouTube videos. Source-platform restrictions still apply.

This package is the local stdio server for Claude Desktop, Claude Code, Cursor, Codex and other clients that run local servers.

For Claude or ChatGPT in a browser, connect to JustClip's hosted MCP server: https://justclip.ai/api/mcp. It uses Streamable HTTP with browser OAuth. Hosted setup instructions. Hosted downloads return links; local files must be uploaded in the dashboard. YouTube fetching is subject to the account's plan; the local package downloads on your machine.

Setup — no keys to copy

The first time the agent clips something, it opens your browser to "Authorize JustClip". You click Authorize (you're already signed in to justclip.ai) and that's it — the token is stored locally, you never see or paste a key. Revoke any time from Settings.

Use Node.js 22 or later. For video downloads, install yt-dlp and ffmpeg: brew install yt-dlp ffmpeg on macOS, or install them for your platform. Other ways to install yt-dlp include: brew install yt-dlp, pipx install yt-dlp, or pip install -U yt-dlp.

Option A — one click (Claude Desktop)

Download the JustClip Desktop Extension (justclip.mcpb): double-click it, Claude Desktop installs the server, and the first clip triggers the browser Authorize. Nothing to edit.

Option B — config (Cursor, or manual)

{

"mcpServers": { "justclip": { "command": "npx", "args": ["-y", "https://github.com/0Xflacko/justclip-mcp/releases/download/v0.3.0/justclip-mcp-0.3.0.tgz"] } } }

The release tarball is public; an npm account is not needed.

No env needed — auth is the browser flow. (Power users/CI can set JUSTCLIP_API_KEY to skip it, and JUSTCLIP_BASE_URL for staging.)

Tools

Everything spends one credit balance: clipping costs 1 credit per minute of footage, a Beat Edit 1, and AI generation is priced per job in credits; the agent prices it with ai_price and asks you first. The one-time AI consent (18+, no real people or brands without consent, the likeness consent) is yours to give in the browser; the agent can't give it for you.

What it will NOT do

It never buys anything. When you're out of credits, hit the plan's export cap, or have no active plan, the tool response says so in plain language with a link you open — the purchase is always a human click, never the agent's. It also can't change your plan, see your password, touch other accounts, delete your projects or clips, publish anything, or accept terms and consent for you.

Example

You: clip this and give me the top 3 — https://youtube.com/watch?v=…

Agent: *(calls clip_video → browser opens → you click Authorize)*

Downloaded on your machine and uploaded (own lane) — project abc123 is

processing. *(polls project_status, then list_clips, then download_clip

for the top 3)*

Privacy Policy

JustClip Privacy Policy covers uploaded media, account data, processing providers, storage, retention and deletion. The local server sends the videos, media and requests you select to JustClip. AI generation can also send selected media to the providers described in that policy after you complete the required consent in JustClip. Local downloads contact the source platform. This server does not send your chat history to JustClip.

Your authorization token is saved at ~/.justclip/token.json with file mode 0600 and reused for the same JustClip base URL. Revoke it in JustClip Settings. Downloaded files are written to the output paths you request and may overwrite existing files. Clipping and generation can spend your existing JustClip credits; the server cannot buy credits or change your subscription.

Support: justclip.ai/contact · admin@justclip.io · Report an issue

Development

npm ci

npm test npm run bundle

npm run bundle writes artifacts/justclip.mcpb with production dependencies. The server source and bundle are MIT licensed; use of the JustClip service is subject to JustClip Terms.

Directory listings

• Official MCP Registry
• Smithery
• Glama local server
• Glama hosted connector

Glama's local server has passed its build and tool-discovery inspection. Its build settings are recorded in glama-build-spec.json; enter the startup command without the mcp-proxy wrapper, which Glama adds. The placeholder key is only for schema inspection. Users authorize their own JustClip account. The hosted connector separately needs a maintainer OAuth test profile and production support for Glama's callbacks.

For a Smithery release, run npm run bundle and npm run smithery:metadata. Submit artifacts/justclip.mcpb as the bundle and the JSON in artifacts/smithery-release.json as the payload using Smithery's publish API. The metadata includes actual tool input schemas required by Smithery's server card. Smithery CLI 4.11.1 copies the simpler desktop manifest entries into that card, which fails validation; the API keeps the standard MCPB manifest intact.