The ClipSpeed CLI for any AI agent
For agents that run commands rather than MCP tools: a CLI and a SKILL.md that teach any agent to clip, generate and schedule. In progress.
- Commands that mirror the MCP tools
- A SKILL.md with the hard rules
- Status: coming
ClipSpeed is the scheduler whose agent also makes the content. Posting today: YouTube, TikTok, Instagram, X (Twitter) and LinkedIn. Keep a human in the loop: ClipSpeed CLI shows the plan and you approve it.
Also try
How to connect ClipSpeed to ClipSpeed CLI
The commands below are the plan. They are not published yet, and this page says so. The MCP server is the route that works today.
1 · Connect · about a minute
# Planned, not yet published:
npm i -g clipspeed
clipspeed auth:login # device-code sign-in, or CLIPSPEED_API_KEY
clipspeed channels:listStatus: coming. Command names may change before release; this page will be regenerated with the final ones.
2 · Then ask
- Today: use the MCP server from any client that supports it; the URL is https://api.clipspeed.ai/mcp.
- Soon: npm i -g clipspeed, then clipspeed auth:login (device code) or export CLIPSPEED_API_KEY.
- The SKILL.md installs with the package and states the rules: read channels:settings before posting, never skip the approval step, preview a plan before booking.
- The badge on this page changes when the package is published.
Works today: the MCP server in Claude, ChatGPT, Claude Code, Codex, Cursor, Windsurf. Developer reference: the ClipSpeed CLI MCP page.
What a first session looks like
Also try
One connection powers every channel you run
Connect each platform to ClipSpeed once, through the platform's own sign-in. From then on ClipSpeed CLI can post to any of them by name, and ClipSpeed publishes at the minute you set. Posting today: YouTube, TikTok, Instagram, X (Twitter) and LinkedIn. The badge on each platform tells you the truth about the rest.
posting today next on the rail on the roadmap
Which way should I connect ClipSpeed to ClipSpeed CLI?
The first row is the route this page documents. Every row reaches the same account, the same calendar and the same booking rules; they differ in how you sign in and what else is in the toolset.
| Method | How you connect | Auth | Toolset | Best for |
|---|---|---|---|---|
| ClipSpeed CLI | npm i -g clipspeed (planned) | Device-code sign-in or API key | Channels, posts, upload, clip | Command-running agents |
| SKILL.md | Installed with the CLI | Same | Teaches the commands and rules | Skill-based agents |
| MCP server | https://api.clipspeed.ai/mcp | OAuth or key | Full | Today |
The same server works with every other agent too: see the MCP server page and the AI agents overview.
Why use ClipSpeed CLI for social media with ClipSpeed?
ClipSpeed CLI brings the context: any agent that can run a command. ClipSpeed brings structured tools for every platform, the booking rules that keep an account healthy, and the two things no other scheduler's agent can do: cut the clips and generate the media in the same conversation.
Commands mirror tools
channels:list, posts:create, posts:list, upload, clip:create, clip:status.
Rules in the skill
The SKILL.md carries the rules an agent must follow.
Honest status
Coming until it is published.
Clips from inside the tool call
Submit a video or a live stream, get back captioned 9:16 clips with a viral score, and book the best ones. The clipping step is a tool, not a separate product.
Image and video generation
Generate a product shot, a quote card or a short opener with ClipSpeed's models, see the credit price first, and post the hosted result with media_url.
Rules that run on the server
Caps, spacing, exact-or-refused booking, duplicate protection and per-platform limits are enforced when ClipSpeed CLI books, so a hurried prompt cannot flood a platform or post the same thing twice.
What is ClipSpeed CLI?
The ClipSpeed CLI is a command-line tool, in progress, for agents that install skills and run commands rather than connecting to MCP servers: OpenClaw-family agents, Grok Bot, Paperclip, Perplexity Computer and others. It will mirror the MCP tools (channels, posts, upload, clip) and ship with a SKILL.md so an agent learns the commands and the rules on install.
CLI vs MCP server vs npm clipspeed-mcp
| Surface | Where it runs | Who it is for | How ClipSpeed connects | Notable difference |
|---|---|---|---|---|
| ClipSpeed CLI | Any machine | Command-running agents | npm (planned) | This page. Coming. |
| MCP server | Hosted | MCP clients | The URL | Works today. |
| clipspeed-mcp (npm) | Local stdio | stdio-only clients | npx clipspeed-mcp | Clipping and clip scheduling today. |
Where it runs
Any machine with Node; installed by the agent.
Who it is for
Agents and people who prefer a CLI.
Status with ClipSpeed
Coming · CLI or plugin in progress. The ClipSpeed CLI route depends on the ClipSpeed CLI or plugin, which is in progress.
How ClipSpeed works with ClipSpeed CLI
Once connected, ClipSpeed CLI sees every ClipSpeed tool the moment the sign-in completes: channels, platform rules, posts, analytics, clipping and generation. It chains them for you; the rules below are what keeps that safe.
- Planned commands mirror the MCP tools
- Reads platform rules
- Exact-or-refused booking
- preview before booking
- Key or device-code sign-in
How booking works, whatever the client
- Exact or refused. A time you name is booked to the minute or refused with the reason and the next open slot. ClipSpeed never moves a booked post without asking.
- As soon as possible is placed and said. Leave the time out and the reply tells you exactly where the post landed.
- Preview books nothing.
preview: trueruns the whole booking, including caps, spacing and slot choice, and writes nothing. It is how a week gets planned before it is booked. - Limits are refused at booking, never trimmed at send time. The reply carries the real count so the fix is one edit.
- Pacing protects the account. Text posts on X are at least 30 minutes apart (ten a day); LinkedIn text is an hour apart (three a day); video uploads are two to four hours apart under your plan's daily cap.
- One piece of content goes to one platform once. The same text or the same file to the same platform is recognised as a duplicate and refused.
- Cancel is undoable for 72 hours in the ClipSpeed app. Copy can be edited while a post is still scheduled; the time cannot, by design.
---
name: clipspeed
description: Clip videos, generate images and video, and schedule posts with ClipSpeed
requirements:
env: [CLIPSPEED_API_KEY]
binaries: [clipspeed]
---
# Rules
- Run `clipspeed channels:settings <platform>` before composing a post.
- Always preview a plan before booking; never skip the user's approval.
- A refused slot comes back with the next open one; use it, never guess.
# Commands
- clipspeed channels:list
- clipspeed posts:create --platform x --text "..." --at 2026-11-17T09:00
- clipspeed posts:list --from today --to +7d
- clipspeed clip:create <url> · clipspeed clip:status <projectId># What the agent reads at connect time (tool descriptions, abridged)
list_channels Connected platforms, what each accepts, limits, your time zone
connect_channel A private 10-minute link to connect one platform
platform_settings Limits, title rules, link handling, pacing per platform
schedule_post clip_id | text | media_url → platforms[], scheduled_at, preview
list_scheduled_posts Scheduled, sending, posted, failed — with post links
update_scheduled_post Edit copy while still scheduled (the time never moves)
cancel_scheduled_post Cancel; undoable 72 h in the app
post_analytics Views, likes, comments, shares where the platform gives them
submit_to_clipspeed Start clipping a video or stream link → projectId
check_clips Finished 9:16 clips with titles, transcripts, viral scores
generate_image / generate_video / wait_for_generation
---
name: clipspeed
description: Clip videos, generate images and video, and schedule posts with ClipSpeed
# SKILL.md ships with the ClipSpeed CLI (in progress). Over MCP the same rules
# live in the tool descriptions the agent reads at connect time.
---
# Rules
- Read platform_settings before composing; limits are refused, never trimmed.
- Preview a plan (preview: true) before booking; never skip the user's approval.
- A refused slot comes back with the next open one. Use it; never guess a time.
- One piece of content goes to one platform once.What Postiz-style schedulers cannot do
Cut the clips first
ClipSpeed CLI does not need finished video to start. Hand it a YouTube link, a podcast, a stream VOD or a local export. ClipSpeed finds the moments, cuts them to 9:16 with word-by-word captions, scores each one 0 to 100 for shareability, and returns them in the same conversation. ClipSpeed CLI picks by score, writes the caption from the transcript, and books the clips on YouTube, TikTok, Instagram, X (Twitter) and LinkedIn. Three tool calls, one approval, no download and no re-upload.
- Clips arrive with a title written from the hook, a transcript and a viral score, so the agent can choose and caption without watching the footage.
- Live streams can be clipped while they are still on air; the agent books the highlights for the next morning before the stream ends.
- Every clip is already hosted, so
schedule_posttakes its id directly. Nothing moves through your laptop.
submit_to_clipspeedPaste the link. ClipSpeed starts the job and returns a project id.check_clipsPoll with the project id. Back come the finished 9:16 clips with titles, transcripts, viral scores and preview links.schedule_postPass the clip id, the platforms, a caption and a time. ClipSpeed CLI shows the plan with preview: true, you say yes, it books.generate_image or generate_videoDescribe the shot. ClipSpeed runs it on the model that fits (Seedance, Kling, Veo, Nano Banana Pro, GPT Image and others) and quotes the credits first.wait_for_generationReturns the hosted result link and a preview the agent can show you.schedule_post with media_urlThe result link goes straight into the booking. The caption, the time and the file are approved together.The other half nobody else has
Generate the image or video, then post it
A product shot for Instagram, a 16:9 announcement graphic for X, a six-second opener before a clip: ClipSpeed CLI can make an image or a short video with ClipSpeed's image and video models and book the result in the same reply. There is no separate design tool, no export, no upload page. The generated file is hosted, so media_url is the only thing the booking needs.
- The price in credits is quoted before anything renders, within the per-generation and daily caps you set in Settings.
- Results are previewed in the conversation, so you approve the picture and the post at once.
- Images post as JPG, PNG or WebP up to 25 MB; video posts as MP4, MOV or WebM up to 1 GB.
Status: in progress
The CLI exists so that agents which cannot speak MCP can still use ClipSpeed. It is not published yet. Everything on this page about it is the plan, labelled as such, and the MCP server is the thing that works today.
What can you ask ClipSpeed CLI to do?
Anything the ClipSpeed tools expose: channels, posts, media, clips, generation and analytics. Four typical requests and what ClipSpeed CLI does with each. Copy one and change the names.
List
clipspeed channels:list
Create
clipspeed posts:create --platform linkedin --text "…" --at 2026-11-17T08:30 --preview
Create
clipspeed clip:create https://youtu.be/… && clipspeed clip:status <projectId>
List
clipspeed posts:list --from today --to +7d
Which platforms can ClipSpeed CLI post to?
ClipSpeed posts today to YouTube, TikTok, Instagram, X (Twitter) and LinkedIn. Every platform below has a dedicated ClipSpeed CLI guide with the settings reference, the limits and example prompts. The badge is the truth: only a platform marked posting today can be booked.
ClipSpeed CLI and ClipSpeed: frequently asked questions
How do I connect ClipSpeed to ClipSpeed CLI?
The commands below are the plan. They are not published yet, and this page says so. The MCP server is the route that works today. Today: use the MCP server from any client that supports it; the URL is https://api.clipspeed.ai/mcp. Soon: npm i -g clipspeed, then clipspeed auth:login (device code) or export CLIPSPEED_API_KEY. Nothing else is installed, and the same account you use in the ClipSpeed app is the one ClipSpeed CLI books into.
Do I need a paid ClipSpeed plan to schedule from ClipSpeed CLI?
Scheduling needs an active ClipSpeed plan or the $1 trial, and it is included on every paid plan at no extra cost. ClipSpeed CLI itself is billed by ClipSpeed under your own account. Connect during the trial, book a few posts, and the plan screen in ClipSpeed takes it from there.
Is ClipSpeed CLI the same as MCP server?
No. ClipSpeed CLI: any machine, coming. MCP server: hosted, works today. clipspeed-mcp (npm): local stdio, clipping and clip scheduling today. All of them reach the same ClipSpeed account and the same calendar; this page covers ClipSpeed CLI.
What can ClipSpeed CLI do with ClipSpeed?
List your connected channels, read each platform's rules, write posts within those rules, schedule or preview them, edit or cancel what is scheduled, and read the numbers after a post goes out. It can also cut a video or a live stream into captioned 9:16 clips with a viral score, generate images and video, and book the results. Today that posts to YouTube, TikTok, Instagram, X (Twitter) and LinkedIn; text-only posts go to X (Twitter) and LinkedIn.
Will posts go out while I am away?
Yes. Once ClipSpeed CLI books a post, ClipSpeed holds it and publishes at the scheduled minute whether or not the chat is open. For fully unattended runs, pair ClipSpeed with a headless agent such as Claude Code or Codex.
Does ClipSpeed CLI need my social media passwords?
No. You connect each platform to ClipSpeed once through that platform's own sign-in; ClipSpeed never sees the password and ClipSpeed CLI never sees the platform at all. ClipSpeed CLI authenticates to ClipSpeed over OAuth, so no key is pasted anywhere, and it can only reach channels already connected in your account. Keep ClipSpeed CLI's confirmation step on for anything that goes live.
Which platforms can ClipSpeed CLI post to through ClipSpeed?
Today: YouTube, TikTok, Instagram, X (Twitter) and LinkedIn. Next on the rail: Facebook, Threads, Bluesky and Pinterest. 21 more platforms, from Telegram and Discord to Reddit and WordPress, are described on their pages with an honest status badge and are not bookable until that badge changes. Each platform below has its own ClipSpeed CLI guide with a settings reference and the limits that apply.
ClipSpeed CLI does not show the ClipSpeed tools. What should I check?
Confirm the connection finished: the ClipSpeed sign-in (or the API key header) has to complete before the tool list is advertised. Then start a fresh chat and make sure the ClipSpeed connector is enabled for it. If a channel is missing rather than a tool, connect the platform in ClipSpeed first and ask ClipSpeed CLI to list channels again.
Is the ClipSpeed CLI available?
Not yet. The badge changes when it is published to npm.
What works today for command-running agents?
Agents that can add an HTTP MCP server can use the URL with an API key. Others wait for the CLI.
Other AI agents that schedule through ClipSpeed
The same ClipSpeed account works with every agent below, through the MCP server or, for agents that run commands, the CLI that is in progress.