Schedule social media posts with Claude Code
One command registers ClipSpeed in Claude Code. From then on it can read your repo, cut the clips, write the posts and book them, in a session or headless from a release script.
- claude mcp add, OAuth sign-in, no key to manage
- Reads CHANGELOG.md and your docs to write the posts
- claude -p runs the whole thing from cron or CI
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: Claude Code shows the plan and you approve it.
Also try
How to connect ClipSpeed to Claude Code
One terminal command registers the server. Start a session, run /mcp to sign in to ClipSpeed in the browser tab that opens, and every tool is available.
1 · Connect · about a minute
claude mcp add --transport http clipspeed https://api.clipspeed.ai/mcpServers load at session start. If the tools do not appear, run claude mcp list, then start a new session.
2 · Then ask
- Run claude mcp add --transport http clipspeed https://api.clipspeed.ai/mcp in your terminal.
- Start claude and run /mcp. Pick clipspeed and authenticate; a browser tab opens for the ClipSpeed sign-in. Approve it.
- Ask it to list your channels. Claude Code calls list_channels and shows what is connected.
- Running on a machine with no browser? Export CLIPSPEED_API_KEY and add --header "Authorization: Bearer $CLIPSPEED_API_KEY" to the add command instead.
Using Claude in the browser instead? The custom connector is a URL: see the Claude guide. Developer reference: the Claude Code 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 Claude Code 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 Claude Code?
Use the first row unless you have a reason not to. 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 |
|---|---|---|---|---|
| MCP server, OAuth (this page) | claude mcp add --transport http clipspeed https://api.clipspeed.ai/mcp | OAuth via /mcp in a session | Full: scheduling, clipping, image and video generation | Most Claude Code users |
| MCP server, API key | The same command with --header "Authorization: Bearer $CLIPSPEED_API_KEY" | A csai_live_ key from Account → API & Integrations | Full | CI runners and servers with no browser |
| Claude.ai connector | Add the custom connector in claude.ai; it is available in Claude Code with the same account | OAuth via claude.ai | Full | People already using ClipSpeed in Claude |
The same server works with every other agent too: see the MCP server page and the AI agents overview.
Why use Claude Code for social media with ClipSpeed?
Claude Code brings the context: the terminal, VS Code and JetBrains. 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.
Your repo is the source
Release notes, docs, a demo recording in ./media: Claude Code reads them and writes the posts. No copy-paste between tools.
Headless and scriptable
claude -p "…" runs a single prompt and exits. Put it after git tag in a release script, in cron, or in a GitHub Action, and the posts book themselves.
Permission prompts stay on
Claude Code asks before it runs a tool that changes something. Scheduling is one of those. Keep the prompt on for anything public; use preview for a dry run.
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 Claude Code books, so a hurried prompt cannot flood a platform or post the same thing twice.
What is Claude Code?
Claude Code is Anthropic's agentic coding tool. It runs in your terminal, with extensions for VS Code and JetBrains, reads your codebase, runs commands and calls MCP tools to finish multi-step work. With ClipSpeed registered as an MCP server, it can also clip a video, generate images and video, and schedule posts to your connected platforms from the same session, or from a script with claude -p.
Claude Code vs Claude Cowork vs the Claude connector
| Surface | Where it runs | Who it is for | How ClipSpeed connects | Notable difference |
|---|---|---|---|---|
| Claude Code | Terminal, VS Code, JetBrains | Developers | claude mcp add | This page. Reads your repo; headless with claude -p; CI and cron. |
| Claude Cowork | Claude Desktop | Knowledge workers | The same connector URL in Settings → Connectors | Works with local folders and desktop apps, no terminal. |
| Claude (claude.ai) | Browser, desktop, mobile | Anyone | Custom connector URL | Chat first; approves bookings in the thread. |
Where it runs
Terminal, VS Code, JetBrains; headless with claude -p.
Who it is for
Developers who want releases, docs and demos to become posts without copy-pasting.
Status with ClipSpeed
Verified end to end. ClipSpeed has driven Claude Code end to end: install, sign-in, clip, schedule.
How ClipSpeed works with Claude Code
Once connected, Claude Code 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.
- claude mcp add registers the HTTP server; /mcp in a session completes the OAuth sign-in
- Claude Code discovers the ClipSpeed tools at session start and chains them:
submit_to_clipspeed→check_clips→schedule_post platform_settingsis read before composing so X's 280 and YouTube's 100-character title are met the first time- A time you name is booked exactly or refused with the next open slot; a taken slot is never silently moved
- Works with Claude.ai, Console, Bedrock and Vertex AI accounts; the ClipSpeed sign-in is separate and OAuth
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.
# Register the server (OAuth; sign in with /mcp inside a session)
claude mcp add --transport http clipspeed https://api.clipspeed.ai/mcp
# No browser on this machine? Use an API key header instead
export CLIPSPEED_API_KEY="csai_live_..."
claude mcp add --transport http clipspeed https://api.clipspeed.ai/mcp \
--header "Authorization: Bearer $CLIPSPEED_API_KEY"
# Verify
claude mcp list
claude "List my connected ClipSpeed channels"# 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
Claude Code 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. Claude Code 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. Claude Code 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: Claude Code 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.
Headless: Claude Code as a publisher nobody has to babysit
Headless: announce every release automatically. The reason to pick Claude Code over a chat window is claude -p. One prompt, no session, exits when done. Wire it into the step after git tag and every release announces itself on X and LinkedIn with a clip from the demo recording, booked for the time you name and refused with the next slot if the time is taken. The MCP server has to be registered on that machine; on a CI runner use the API key header.
#!/bin/bash
# Runs after a new tag is pushed
claude -p "Summarise the changes since the last git tag in one post for X (under 280, link counts as 23) and one for LinkedIn. Schedule both via ClipSpeed for today at 10am. Attach ./assets/release.png."
# Claude Code reads the git history, writes the copy,
# uploads nothing (the PNG is served from your public assets),
# and books both posts. The reply lists each slot and id.Keep these on
preview: truefirst, so an unattended run reports a plan before it books.- The ClipSpeed server registered on that machine; use the API key header where there is no browser.
- A log of the reply: every booked slot comes back with its id, and every refusal with the next open slot.
What can you ask Claude Code to do?
Anything the ClipSpeed tools expose: channels, posts, media, clips, generation and analytics. Four typical requests and what Claude Code does with each. Copy one and change the names.
README to posts
Turn README.md into one X post under 280 characters and one LinkedIn post under 1,000. Schedule both for Monday 10am. Preview first.
Changelog with a clip
Read CHANGELOG.md, clip ./media/demo.mp4, and post about v2.4 on X and LinkedIn tomorrow at 9am with the best clip attached to the X post.
A week of Shorts
Clip https://youtu.be/… , keep the top five by score, and plan one YouTube Short a day at 5pm with titles under 100 characters. Show the plan before booking.
Audit the calendar
List everything scheduled for the next 7 days as a table, flag anything over its platform's text limit, and cancel the duplicate if two posts share the same text.
Which platforms can Claude Code post to?
ClipSpeed posts today to YouTube, TikTok, Instagram, X (Twitter) and LinkedIn. Every platform below has a dedicated Claude Code guide with the settings reference, the limits and example prompts. The badge is the truth: only a platform marked posting today can be booked.
Claude Code and ClipSpeed: frequently asked questions
How do I connect ClipSpeed to Claude Code?
One terminal command registers the server. Start a session, run /mcp to sign in to ClipSpeed in the browser tab that opens, and every tool is available. Run claude mcp add --transport http clipspeed https://api.clipspeed.ai/mcp in your terminal. Start claude and run /mcp. Pick clipspeed and authenticate; a browser tab opens for the ClipSpeed sign-in. Approve it. Nothing else is installed, and the same account you use in the ClipSpeed app is the one Claude Code books into.
Do I need a paid ClipSpeed plan to schedule from Claude Code?
Scheduling needs an active ClipSpeed plan or the $1 trial, and it is included on every paid plan at no extra cost. Claude Code itself is billed by Anthropic under your own account. Connect during the trial, book a few posts, and the plan screen in ClipSpeed takes it from there.
Is Claude Code the same as Claude Cowork?
No. Claude Code: terminal, vs code, jetbrains, reads your repo; headless with claude -p; ci and cron. Claude Cowork: claude desktop, works with local folders and desktop apps, no terminal. Claude (claude.ai): browser, desktop, mobile, chat first; approves bookings in the thread. All of them reach the same ClipSpeed account and the same calendar; this page covers Claude Code.
What can Claude Code 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 Claude Code books a post, ClipSpeed holds it and publishes at the scheduled minute whether or not the session is open. For runs where Claude Code decides what to post without you, use its headless mode shown on this page and keep preview mode on so the plan is reviewed first.
Does Claude Code 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 Claude Code never sees the platform at all. Claude Code authenticates to ClipSpeed over OAuth, so no key is pasted anywhere, and it can only reach channels already connected in your account. Keep Claude Code's confirmation step on for anything that goes live.
Which platforms can Claude Code 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 Claude Code guide with a settings reference and the limits that apply.
Claude Code does not show the ClipSpeed tools. What should I check?
Run claude mcp list and confirm clipspeed is registered with the HTTP transport. Servers load at session start, so start a new session. Then run /mcp and complete the sign-in if it shows as needing authentication. On a machine with no browser, use the API key header instead of OAuth.
Can I schedule posts from CI or a cron job with Claude Code?
Yes. claude -p "…" runs one prompt and exits. Register the ClipSpeed server on that machine first; on a runner without a browser use the API key header form of claude mcp add. The reply lists each booked slot and id, which your script can log.
Does the directory connector from claude.ai work in Claude Code?
The custom connector you add in claude.ai is available in Claude Code when you sign in with the same account. If you only added the directory listing (clipping only), add the custom connector URL or run claude mcp add to get scheduling and generation.
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.