Schedule social media posts with Gemini CLI
Register ClipSpeed as an HTTP MCP server in Gemini CLI and ask it to clip, write and schedule from the terminal, or run it headless with gemini -p.
- gemini mcp add with the HTTP transport
- Reads the repo and writes per platform
- Standard MCP route; not yet verified end to end by ClipSpeed
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: Gemini CLI shows the plan and you approve it.
Also try
How to connect ClipSpeed to Gemini CLI
One command registers the server in Gemini CLI's settings. Start gemini, run /mcp auth clipspeed to sign in, and the tools are available.
1 · Connect · about a minute
gemini mcp add --transport http clipspeed https://api.clipspeed.ai/mcpClipSpeed has not yet run an end-to-end check inside Gemini CLI. The server is standard MCP over streamable HTTP, which Gemini CLI supports; the flags above are Gemini CLI's documented ones.
2 · Then ask
- Run gemini mcp add --transport http clipspeed https://api.clipspeed.ai/mcp.
- Start gemini and run /mcp. Authenticate clipspeed; approve the ClipSpeed sign-in in the browser.
- Ask it to list your channels.
- No browser? Set a header with a ClipSpeed API key in settings.json instead of OAuth.
Not a Gemini user? Claude Code and Codex are one command each and verified.
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 Gemini 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 Gemini CLI?
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 |
|---|---|---|---|---|
| gemini mcp add (this page) | gemini mcp add --transport http clipspeed https://api.clipspeed.ai/mcp | OAuth via /mcp auth | Full | Most Gemini CLI users |
| settings.json with a key | "clipspeed": { "httpUrl": "…", "headers": { "Authorization": "Bearer …" } } | ClipSpeed API key | Full | CI |
| Any other MCP agent | Same URL | OAuth or key | Full | Everything else |
The same server works with every other agent too: see the MCP server page and the AI agents overview.
Why use Gemini CLI for social media with ClipSpeed?
Gemini CLI brings the context: the terminal. 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.
Repo in, posts out
Gemini CLI reads the changelog or docs and writes a post per platform within each limit.
Headless with -p
gemini -p runs one prompt and exits for cron and CI.
Clips in the same session
Submit the demo, pick by score, attach to the post.
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 Gemini CLI books, so a hurried prompt cannot flood a platform or post the same thing twice.
What is Gemini CLI?
Gemini CLI is Google's open-source terminal agent built on the Gemini models. It reads your project, runs commands and connects to MCP servers over HTTP. With ClipSpeed registered, it can clip a video, generate media and schedule posts from a terminal session or from a script.
Gemini CLI vs Claude Code vs Codex
| Surface | Where it runs | Who it is for | How ClipSpeed connects | Notable difference |
|---|---|---|---|---|
| Gemini CLI | Terminal | Developers on Gemini | gemini mcp add | This page. gemini -p for headless. |
| Claude Code | Terminal | Developers | claude mcp add | Verified end to end; claude -p. |
| Codex | Terminal | Developers | codex mcp add | Verified end to end; codex exec. |
Where it runs
Terminal; headless with gemini -p.
Who it is for
Developers on Gemini who want the release to announce itself.
Status with ClipSpeed
Standard MCP route · not yet verified by us. Gemini CLI speaks standard MCP over HTTP; we have not yet run it end to end ourselves and say so.
How ClipSpeed works with Gemini CLI
Once connected, Gemini 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.
- gemini mcp add writes the server into ~/.gemini/settings.json
- Gemini CLI discovers the tools at start and reads
platform_settingsbefore composing schedule_postis exact or refused with the next open slotpreview: truefor a dry rungemini -pfor unattended runs
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": {
"httpUrl": "https://api.clipspeed.ai/mcp"
// no browser? add:
// "headers": { "Authorization": "Bearer csai_live_..." }
}
}
}# 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
Gemini 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. Gemini 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. Gemini 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: Gemini 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.
Headless: Gemini CLI as a publisher nobody has to babysit
Verification status. Gemini CLI supports HTTP MCP servers with OAuth, which is exactly what ClipSpeed serves. We have not yet driven it end to end ourselves, so this page is marked as the generic route. The flags are Gemini CLI's own; if a flag name differs in your version, gemini mcp add --help is the reference and the URL does not change.
gemini -p "Summarise CHANGELOG.md's latest entry as one X post under 280 (links count as 23) and schedule it via ClipSpeed for 10am today."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 Gemini CLI to do?
Anything the ClipSpeed tools expose: channels, posts, media, clips, generation and analytics. Four typical requests and what Gemini CLI does with each. Copy one and change the names.
Changelog to posts
Read CHANGELOG.md and schedule a post about the latest version on X and LinkedIn for tomorrow 9am via ClipSpeed. Preview first.
Clip and post
Clip ./media/demo.mp4, keep the best two, and post them to TikTok and YouTube Shorts tomorrow at noon and 5pm.
Generate a graphic
Generate a 16:9 launch graphic and post it to X at noon with one line.
From a script
gemini -p "List what's scheduled via ClipSpeed this week as a table."
Which platforms can Gemini CLI post to?
ClipSpeed posts today to YouTube, TikTok, Instagram, X (Twitter) and LinkedIn. Every platform below has a dedicated Gemini 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.
Gemini CLI and ClipSpeed: frequently asked questions
How do I connect ClipSpeed to Gemini CLI?
One command registers the server in Gemini CLI's settings. Start gemini, run /mcp auth clipspeed to sign in, and the tools are available. Run gemini mcp add --transport http clipspeed https://api.clipspeed.ai/mcp. Start gemini and run /mcp. Authenticate clipspeed; approve the ClipSpeed sign-in in the browser. Nothing else is installed, and the same account you use in the ClipSpeed app is the one Gemini CLI books into.
Do I need a paid ClipSpeed plan to schedule from Gemini CLI?
Scheduling needs an active ClipSpeed plan or the $1 trial, and it is included on every paid plan at no extra cost. Gemini CLI itself is billed by Google under your own account. Connect during the trial, book a few posts, and the plan screen in ClipSpeed takes it from there.
Is Gemini CLI the same as Claude Code?
No. Gemini CLI: terminal, gemini -p for headless. Claude Code: terminal, verified end to end; claude -p. Codex: terminal, verified end to end; codex exec. All of them reach the same ClipSpeed account and the same calendar; this page covers Gemini CLI.
What can Gemini 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 Gemini CLI books a post, ClipSpeed holds it and publishes at the scheduled minute whether or not the session is open. For runs where Gemini CLI 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 Gemini 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 Gemini CLI never sees the platform at all. Gemini CLI authenticates to ClipSpeed over OAuth, so no key is pasted anywhere, and it can only reach channels already connected in your account. Keep Gemini CLI's confirmation step on for anything that goes live.
Which platforms can Gemini 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 Gemini CLI guide with a settings reference and the limits that apply.
Gemini 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 session, since servers load at startup. If a channel is missing rather than a tool, connect the platform in ClipSpeed first and ask Gemini CLI to list channels again.
Has ClipSpeed verified Gemini CLI?
Not end to end yet. The server is standard MCP over HTTP with OAuth, which Gemini CLI supports. The badge on this page changes when we have run it ourselves.
Can Gemini CLI run the posting unattended?
Yes, gemini -p runs one prompt and exits. Register the server on that machine and use an API key header if there is no browser.
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.