
JustClip
io.github.0XflackoPublished by GitHub account 0Xflackov0.3.0Updated Nov 5, 2026
Clip videos and live streams, create Beat Edits, and generate AI media with JustClip.
Overview
JustClip clips videos and live streams, makes Beat Edits and generates AI media through your JustClip account, from a local or hosted MCP server.
- What you can do
- Check account plan, credits and consent status
- Clip YouTube, Twitch or Kick URLs or local files, including live channels, and stop live capture
- List projects, check processing status, list clips and moments, turn moments into clips, rename clips, add caption variants
- Download single clips as mp4 or srt, or all exportable clips as a zip
- Draft ready-to-post hooks, captions and hashtags for TikTok, Shorts, Reels, X and LinkedIn
- Create Beat Edits from music and footage, check progress and download results
- When to use it
- Use it when you want an assistant to turn long videos or live streams into short clips, prepare social post drafts, or run AI image and video generations on an existing JustClip plan, without leaving the chat.
- Requirements
- A JustClip account and plan; browser OAuth authorization on first use (token stored locally), or the JUSTCLIP_API_KEY variable for CI. Local package needs Node.js 22 or later plus yt-dlp and ffmpeg for downloads. The hosted server at justclip.ai/api/mcp uses Streamable HTTP with browser OAuth. Network access to JustClip and the source platform.
Installation
In SourceWeft
- Open JustClip in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.0Xflacko%2Fjustclip/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"justclip": {
"type": "http",
"url": "https://justclip.ai/api/mcp"
}
}
}README
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)
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) — projectabc123is processing. (pollsproject_status, thenlist_clips, thendownload_clipfor 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 · [email protected] · Report an issue
Development
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
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.
Source: README.md at commit 4930908
Tools
0Version history
1- v0.3.0LatestOct 15, 2026
Score
85% 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 daysRequired25 pts
- Auth declaredRequired10 pts
- 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