Schedule social media posts with Cursor
Add ClipSpeed to Cursor's MCP settings and the Agent can post the changelog when you tag a release, with a clip from the demo recording attached.
- One JSON block in .cursor/mcp.json, OAuth sign-in
- The Agent reads the repo and writes the posts
- 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: Cursor shows the plan and you approve it.
Also try
How to connect ClipSpeed to Cursor
Cursor reads MCP servers from a JSON file. Add the block, open Cursor Settings → MCP, click the sign-in for clipspeed, and the Agent has the tools.
1 · Connect · about a minute
{
"mcpServers": {
"clipspeed": { "url": "https://api.clipspeed.ai/mcp" }
}
}Cursor shows the tools under Settings → MCP once the server connects. If the list is empty, check the JSON and restart Cursor. ClipSpeed has not yet seen a real Cursor session connect; the setup is Cursor's documented MCP route and the URL is the same as every verified client.
2 · Then ask
- Create .cursor/mcp.json in the project (or ~/.cursor/mcp.json for every project) with the block shown.
- Open Cursor Settings → MCP. clipspeed appears; click to authenticate and approve the ClipSpeed sign-in.
- Open the Agent panel and ask it to list your channels.
- For a runner with no browser, add a headers block with Authorization: Bearer and a ClipSpeed API key instead.
Windsurf user? The file is different and the URL is the same: see the Windsurf guide. Developer reference: the Cursor 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 Cursor 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 Cursor?
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.json with OAuth (this page) | { "mcpServers": { "clipspeed": { "url": "https://api.clipspeed.ai/mcp" } } } | OAuth via Settings → MCP | Full: scheduling, clipping, generation | Most Cursor users |
| mcp.json with a key | Add "headers": { "Authorization": "Bearer csai_live_…" } | ClipSpeed API key | Full | Shared machines and CI |
| Cursor CLI | cursor-agent uses the same mcp.json | Same | Full | Scripts |
The same server works with every other agent too: see the MCP server page and the AI agents overview.
Why use Cursor for social media with ClipSpeed?
Cursor brings the context: the Cursor editor's Agent. 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.
Post the changelog on tag
Ask the Agent to post about the release when you tag it. It reads the diff, writes per platform and books the slot you name.
Clips from the demo recording
./media/demo.mp4 in the repo becomes captioned clips; the best one rides the X post as native video.
Rules in the editor
A .cursor/rules file can tell the Agent to always preview before booking and to keep X under 280 with links as 23.
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 Cursor books, so a hurried prompt cannot flood a platform or post the same thing twice.
What is Cursor?
Cursor is the AI code editor built on VS Code. Its Agent runs multi-step tasks in your project, runs commands and calls MCP tools. With ClipSpeed in Cursor's MCP settings, the Agent can clip a video, generate media and schedule posts from inside the editor, and the Cursor CLI can do the same from a script.
Cursor vs Windsurf vs Claude Code
| Surface | Where it runs | Who it is for | How ClipSpeed connects | Notable difference |
|---|---|---|---|---|
| Cursor | Cursor editor, cursor-agent | Developers | .cursor/mcp.json | This page. Agent panel in the editor; CLI for scripts. |
| Windsurf | Windsurf editor | Developers | mcp_config.json with serverUrl | Cascade agent; same URL. |
| Claude Code | Terminal | Developers | claude mcp add | No editor needed; claude -p for headless. |
Where it runs
The Cursor editor; cursor-agent on the command line.
Who it is for
Developers who live in Cursor and want releases to become posts.
Status with ClipSpeed
Standard MCP route · not yet verified by us. Cursor speaks standard MCP over HTTP; we have not yet run it end to end ourselves and say so.
How ClipSpeed works with Cursor
Once connected, Cursor 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.
- Cursor reads .cursor/mcp.json and connects to the ClipSpeed server; sign in under Settings → MCP
- The Agent reads
platform_settingsbefore composing schedule_postbooks exactly or refuses with the next open slotpreview: truefor a plan with nothing booked- cursor-agent -p runs the same flow from a script
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"
// no browser on this machine? add:
// "headers": { "Authorization": "Bearer csai_live_..." }
}
}
}
# .cursor/rules/clipspeed.mdc
# Always call schedule_post with preview: true first and show the plan.
# X posts stay under 280 characters; every link counts as 23.# 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
Cursor 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. Cursor 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. Cursor 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: Cursor 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: Cursor as a publisher nobody has to babysit
Post the changelog when I tag a release. The Cursor use case is the release. Tag, and the Agent turns the diff into a post for each platform, cuts the demo recording into clips, attaches the best one, and books the slot you named. Put the instruction in a rules file and it applies to every release without being asked.
# Cursor's CLI uses the same mcp.json
cursor-agent -p "Read CHANGELOG.md and schedule a post about the latest version on X and LinkedIn via ClipSpeed for tomorrow 9am. Preview first, then book if nothing is refused."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 Cursor to do?
Anything the ClipSpeed tools expose: channels, posts, media, clips, generation and analytics. Four typical requests and what Cursor does with each. Copy one and change the names.
Changelog to posts
Read CHANGELOG.md and post about the latest version on X and LinkedIn at 2pm with the best clip from ./media/demo.mp4.
Tips from the docs folder
Turn the five pages in docs/tips into LinkedIn posts under 800 characters and schedule one a day at 8:30am. Preview first.
Generate a graphic
Generate a 16:9 image of the new dashboard theme as abstract shapes and post it to X at noon with one line.
From the CLI
cursor-agent -p "What's scheduled via ClipSpeed this week? Print it as a table."
Which platforms can Cursor post to?
ClipSpeed posts today to YouTube, TikTok, Instagram, X (Twitter) and LinkedIn. Every platform below has a dedicated Cursor guide with the settings reference, the limits and example prompts. The badge is the truth: only a platform marked posting today can be booked.
Cursor and ClipSpeed: frequently asked questions
How do I connect ClipSpeed to Cursor?
Cursor reads MCP servers from a JSON file. Add the block, open Cursor Settings → MCP, click the sign-in for clipspeed, and the Agent has the tools. Create .cursor/mcp.json in the project (or ~/.cursor/mcp.json for every project) with the block shown. Open Cursor Settings → MCP. clipspeed appears; click to authenticate and approve the ClipSpeed sign-in. Nothing else is installed, and the same account you use in the ClipSpeed app is the one Cursor books into.
Do I need a paid ClipSpeed plan to schedule from Cursor?
Scheduling needs an active ClipSpeed plan or the $1 trial, and it is included on every paid plan at no extra cost. Cursor itself is billed by Anysphere under your own account. Connect during the trial, book a few posts, and the plan screen in ClipSpeed takes it from there.
Is Cursor the same as Windsurf?
No. Cursor: cursor editor, cursor-agent, agent panel in the editor; cli for scripts. Windsurf: windsurf editor, cascade agent; same url. Claude Code: terminal, no editor needed; claude -p for headless. All of them reach the same ClipSpeed account and the same calendar; this page covers Cursor.
What can Cursor 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 Cursor books a post, ClipSpeed holds it and publishes at the scheduled minute whether or not the chat is open. For runs where Cursor 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 Cursor 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 Cursor never sees the platform at all. Cursor authenticates to ClipSpeed over OAuth, so no key is pasted anywhere, and it can only reach channels already connected in your account. Keep Cursor's confirmation step on for anything that goes live.
Which platforms can Cursor 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 Cursor guide with a settings reference and the limits that apply.
Cursor does not show the ClipSpeed tools. What should I check?
Open Settings → MCP and confirm clipspeed is listed and connected; click to authenticate if it is not. Check the JSON for a typo and restart Cursor. On a machine with no browser, use the Authorization header with an API key.
Where does the ClipSpeed MCP config go in Cursor?
.cursor/mcp.json in the project for that project only, or ~/.cursor/mcp.json for every project. The block is one URL. Sign in under Cursor Settings → MCP.
Can I run it from the command line?
Yes. cursor-agent -p "…" uses the same mcp.json and runs one prompt, which fits a release script.
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.