Schedule posts and cut clips from any MCP client
One URL. OAuth or an API key. Every client that speaks MCP over HTTP gets the same tools: clip, generate, schedule.
- https://api.clipspeed.ai/mcp for every client
- OAuth in a browser, or an API key header without one
- The same booking rules whatever the client
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: Any MCP client shows the plan and you approve it.
Also try
How to connect ClipSpeed to Any MCP client
Add the URL as an HTTP (streamable) MCP server. If the client can open a browser, sign in with OAuth. If it cannot, send an Authorization: Bearer header with a ClipSpeed API key.
1 · Connect · about a minute
https://api.clipspeed.ai/mcpThe transport is streamable HTTP. There is nothing to install locally and nothing to update.
2 · Then ask
- Add https://api.clipspeed.ai/mcp as an HTTP MCP server in your client.
- Browser available: complete the ClipSpeed sign-in when the client opens it.
- No browser: generate a key under Account → API & Integrations and send Authorization: Bearer csai_live_… on every request.
- Call list_channels to confirm the round trip.
For clients that run commands rather than MCP, the ClipSpeed CLI is in progress. Developer reference: the Any MCP client 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 Any MCP client 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 Any MCP client?
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 |
|---|---|---|---|---|
| OAuth | Add the URL; sign in when prompted | Browser sign-in | Full | Desktop and chat clients |
| API key | Add the URL with Authorization: Bearer csai_live_… | Key from Account → API & Integrations | Full | Servers, CI, self-hosted agents |
| npm clipspeed-mcp (stdio) | npx clipspeed-mcp with CLIPSPEED_API_KEY | API key | Clipping and scheduling (clip posts) | Clients that only speak stdio |
The same server works with every other agent too: see the MCP server page and the AI agents overview.
Why use Any MCP client for social media with ClipSpeed?
Any MCP client brings the context: any client that speaks the Model Context Protocol. 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.
One URL
The same endpoint for Claude, ChatGPT, Claude Code, Codex, Cursor, Windsurf and everything else.
Two credentials
OAuth where there is a browser; a revocable API key where there is not.
Rules on the server
Caps, spacing, exact-or-refused booking and duplicate protection run server-side, so no client can misbehave.
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 Any MCP client books, so a hurried prompt cannot flood a platform or post the same thing twice.
What is Any MCP client?
The ClipSpeed MCP server is a hosted Model Context Protocol server over streamable HTTP. Any client that can add an HTTP MCP server, from Claude and ChatGPT to a self-hosted agent, gets the same tools: list and connect channels, read platform rules, schedule and manage posts, read analytics, clip videos and generate images and video.
Hosted MCP vs stdio package vs CLI
| Surface | Where it runs | Who it is for | How ClipSpeed connects | Notable difference |
|---|---|---|---|---|
| Hosted MCP server | api.clipspeed.ai | Any HTTP MCP client | The URL | This page. Full toolset, OAuth or key. |
| clipspeed-mcp (npm) | Your machine, stdio | Clients without HTTP MCP | npx clipspeed-mcp | Local process; clipping plus clip scheduling. |
| ClipSpeed CLI | Your machine | Agents that run commands | In progress | Coming. |
Where it runs
Hosted at api.clipspeed.ai.
Who it is for
Anyone whose client is not on the named list.
Status with ClipSpeed
Verified end to end. ClipSpeed has driven Any MCP client end to end: install, sign-in, clip, schedule.
How ClipSpeed works with Any MCP client
Once connected, Any MCP client 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.
- Streamable HTTP transport; tools are advertised at handshake
list_channels, connect_channel,platform_settings,schedule_post,list_scheduled_posts,update_scheduled_post,cancel_scheduled_post,post_analyticsfor schedulingsubmit_to_clipspeed,check_clipsand the live-clipping tools for clippinggenerate_image,generate_video,wait_for_generationfor creation- Every booking runs through the same rules as the web app
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.
{
"mcpServers": {
"clipspeed": {
"url": "https://api.clipspeed.ai/mcp",
"headers": { "Authorization": "Bearer csai_live_..." } // omit for OAuth
}
}
}
# Prove the round trip without starting any work:
# call list_channels → your connected platforms and your time zone# 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
Any MCP client 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. Any MCP client 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. Any MCP client 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: Any MCP client 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.
The two credentials
GUI clients complete an OAuth sign-in in a browser tab, which means no key to manage. Headless clients send a Bearer API key on every request; the key is csai_live_ followed by 48 hex characters, shown once at creation, listed with its usage counters and revocable in one call. Both reach the same account and the same tools.
What can you ask Any MCP client to do?
Anything the ClipSpeed tools expose: channels, posts, media, clips, generation and analytics. Four typical requests and what Any MCP client does with each. Copy one and change the names.
Round trip
Call list_channels and tell me what is connected and my time zone.
Read before writing
Call platform_settings for x and linkedin and summarise the limits.
Schedule
Schedule this text to X and LinkedIn for 9am tomorrow. Preview first.
Chain
submit_to_clipspeed this link, check_clips until done, schedule_post the best to TikTok at 5pm.
Which platforms can Any MCP client post to?
ClipSpeed posts today to YouTube, TikTok, Instagram, X (Twitter) and LinkedIn. Every platform below has a dedicated Any MCP client guide with the settings reference, the limits and example prompts. The badge is the truth: only a platform marked posting today can be booked.
Any MCP client and ClipSpeed: frequently asked questions
How do I connect ClipSpeed to Any MCP client?
Add the URL as an HTTP (streamable) MCP server. If the client can open a browser, sign in with OAuth. If it cannot, send an Authorization: Bearer header with a ClipSpeed API key. Add https://api.clipspeed.ai/mcp as an HTTP MCP server in your client. Browser available: complete the ClipSpeed sign-in when the client opens it. Nothing else is installed, and the same account you use in the ClipSpeed app is the one Any MCP client books into.
Do I need a paid ClipSpeed plan to schedule from Any MCP client?
Scheduling needs an active ClipSpeed plan or the $1 trial, and it is included on every paid plan at no extra cost. Any MCP client 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 Any MCP client the same as clipspeed-mcp (npm)?
No. Hosted MCP server: api.clipspeed.ai, full toolset, oauth or key. clipspeed-mcp (npm): your machine, stdio, local process; clipping plus clip scheduling. ClipSpeed CLI: your machine, coming. All of them reach the same ClipSpeed account and the same calendar; this page covers Any MCP client.
What can Any MCP client 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 Any MCP client 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 Any MCP client 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 Any MCP client never sees the platform at all. Any MCP client authenticates to ClipSpeed over OAuth, so no key is pasted anywhere, and it can only reach channels already connected in your account. Keep Any MCP client's confirmation step on for anything that goes live.
Which platforms can Any MCP client 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 Any MCP client guide with a settings reference and the limits that apply.
Any MCP client 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 Any MCP client to list channels again.
Which clients work with the ClipSpeed MCP server?
Any client that can add an HTTP (streamable) MCP server. Verified: Claude, ChatGPT, Claude Code, Claude Desktop, Codex, Cursor, Windsurf. Compatible: everything else that speaks the protocol.
OAuth or API key?
OAuth when the client can open a browser; an API key header when it cannot. Same tools either way.
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.