Schedule social media posts with GitHub Copilot
Add ClipSpeed to .vscode/mcp.json and Copilot's agent mode can clip the demo, write the release posts and book them from inside VS Code.
- One http server entry in .vscode/mcp.json
- Agent mode reads the workspace 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: GitHub Copilot shows the plan and you approve it.
Also try
How to connect ClipSpeed to GitHub Copilot
VS Code reads MCP servers from .vscode/mcp.json. Add the entry, start the server from the editor, sign in, and agent mode has the tools.
1 · Connect · about a minute
{
"servers": {
"clipspeed": { "type": "http", "url": "https://api.clipspeed.ai/mcp" }
}
}ClipSpeed has not yet run an end-to-end check inside Copilot. The server is standard MCP over HTTP, which VS Code's agent mode supports.
2 · Then ask
- Create .vscode/mcp.json in the workspace with the block shown.
- Open the file; VS Code shows a Start action above the server. Start it and approve the ClipSpeed sign-in.
- Open Copilot Chat in agent mode, confirm clipspeed is in the tools picker, and ask it to list your channels.
- No browser? Replace OAuth with an Authorization header carrying a ClipSpeed API key.
Cursor or Windsurf instead? Each has a guide with its own file.
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 GitHub Copilot 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 GitHub Copilot?
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 |
|---|---|---|---|---|
| .vscode/mcp.json (this page) | { "servers": { "clipspeed": { "type": "http", "url": "https://api.clipspeed.ai/mcp" } } } | OAuth on start | Full | VS Code users |
| User settings | The same entry in the user-level mcp.json | OAuth | Full | Every workspace |
| Copilot CLI | Same server config | OAuth or key | Full | Scripts |
The same server works with every other agent too: see the MCP server page and the AI agents overview.
Why use GitHub Copilot for social media with ClipSpeed?
GitHub Copilot brings the context: VS Code's agent mode and the Copilot CLI. 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.
Workspace as source
Agent mode reads the changelog and docs in the workspace and writes the posts.
Tools picker
Choose which ClipSpeed tools agent mode may call; keep scheduling behind a confirmation.
Clips in the editor
Clip the demo recording and attach the best to the post without leaving VS Code.
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 GitHub Copilot books, so a hurried prompt cannot flood a platform or post the same thing twice.
What is GitHub Copilot?
GitHub Copilot's agent mode in VS Code runs multi-step tasks in your workspace and calls MCP tools; the Copilot CLI does the same in a terminal. With ClipSpeed added as an HTTP MCP server, Copilot can clip a video, generate media and schedule posts to your connected platforms.
Copilot vs Cursor vs Claude Code
| Surface | Where it runs | Who it is for | How ClipSpeed connects | Notable difference |
|---|---|---|---|---|
| GitHub Copilot | VS Code, JetBrains, CLI | Teams on Copilot | .vscode/mcp.json | This page. Agent mode in the editor. |
| Cursor | Cursor editor | Developers | .cursor/mcp.json | Standard MCP route, not yet verified by us. |
| Claude Code | Terminal | Developers | claude mcp add | Verified; headless with claude -p. |
Where it runs
VS Code agent mode, JetBrains, the Copilot CLI.
Who it is for
Teams already on Copilot.
Status with ClipSpeed
Standard MCP route · not yet verified by us. GitHub Copilot speaks standard MCP over HTTP; we have not yet run it end to end ourselves and say so.
How ClipSpeed works with GitHub Copilot
Once connected, GitHub Copilot 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.
- VS Code starts the server from .vscode/mcp.json and handles the OAuth sign-in
- Agent mode reads
platform_settingsbefore composing schedule_postis exact or refused with the next open slotpreview: truefor a plan with nothing booked- Tool confirmations keep a human in the loop
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.
{
"servers": {
"clipspeed": {
"type": "http",
"url": "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
GitHub Copilot 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. GitHub Copilot 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. GitHub Copilot 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: GitHub Copilot 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: GitHub Copilot as a publisher nobody has to babysit
Verification status. VS Code's agent mode supports HTTP MCP servers with OAuth, which is what ClipSpeed serves. We have not yet driven Copilot end to end ourselves, so this page is marked as the generic route; the file format is VS Code's documented one and the URL is the same as every other client.
# Copilot CLI, non-interactive
copilot -p "Read CHANGELOG.md and schedule a post about the latest version on X and LinkedIn via ClipSpeed for tomorrow 9am. Preview first."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 GitHub Copilot to do?
Anything the ClipSpeed tools expose: channels, posts, media, clips, generation and analytics. Four typical requests and what GitHub Copilot 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 via ClipSpeed for tomorrow 9am. Preview first.
Clip and attach
Clip ./media/demo.mp4 and attach the best moment to the X post.
Generate a graphic
Generate a 16:9 graphic for the release and post it to X at noon.
Copilot CLI
copilot -p "List what's scheduled via ClipSpeed this week."
Which platforms can GitHub Copilot post to?
ClipSpeed posts today to YouTube, TikTok, Instagram, X (Twitter) and LinkedIn. Every platform below has a dedicated GitHub Copilot guide with the settings reference, the limits and example prompts. The badge is the truth: only a platform marked posting today can be booked.
GitHub Copilot and ClipSpeed: frequently asked questions
How do I connect ClipSpeed to GitHub Copilot?
VS Code reads MCP servers from .vscode/mcp.json. Add the entry, start the server from the editor, sign in, and agent mode has the tools. Create .vscode/mcp.json in the workspace with the block shown. Open the file; VS Code shows a Start action above the server. Start it and approve the ClipSpeed sign-in. Nothing else is installed, and the same account you use in the ClipSpeed app is the one GitHub Copilot books into.
Do I need a paid ClipSpeed plan to schedule from GitHub Copilot?
Scheduling needs an active ClipSpeed plan or the $1 trial, and it is included on every paid plan at no extra cost. GitHub Copilot itself is billed by GitHub under your own account. Connect during the trial, book a few posts, and the plan screen in ClipSpeed takes it from there.
Is GitHub Copilot the same as Cursor?
No. GitHub Copilot: vs code, jetbrains, cli, agent mode in the editor. Cursor: cursor editor, standard mcp route, not yet verified by us. Claude Code: terminal, verified; headless with claude -p. All of them reach the same ClipSpeed account and the same calendar; this page covers GitHub Copilot.
What can GitHub Copilot 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 GitHub Copilot books a post, ClipSpeed holds it and publishes at the scheduled minute whether or not the chat is open. For runs where GitHub Copilot 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 GitHub Copilot 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 GitHub Copilot never sees the platform at all. GitHub Copilot authenticates to ClipSpeed over OAuth, so no key is pasted anywhere, and it can only reach channels already connected in your account. Keep GitHub Copilot's confirmation step on for anything that goes live.
Which platforms can GitHub Copilot 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 GitHub Copilot guide with a settings reference and the limits that apply.
GitHub Copilot 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 GitHub Copilot to list channels again.
Has ClipSpeed verified Copilot?
Not end to end yet. The server is standard MCP over HTTP, which VS Code's agent mode supports. The badge on this page changes when we have run it.
Does this work in JetBrains Copilot?
JetBrains Copilot supports MCP servers through its own settings; the URL is the same. We have not tested it.
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.