Post to Threads from Any MCP client
Any MCP client can post to Threads on Threads through ClipSpeed. Add the ClipSpeed connector, sign in, and then ask Any MCP client to post to Threads, pick the time, and apply Threads's settings, without leaving any client that speaks the Model Context Protocol. Threads is coming next on ClipSpeed's rail; this page describes how it works and says so.
Keep a human in the loop: Any MCP client shows the plan and asks before anything is public. Posting today: YouTube, TikTok, Instagram, X (Twitter) and LinkedIn.
Also try
How to post Threads from 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. Connect Threads in ClipSpeed, then describe the post. Setup takes about a minute.
# One-time setup: your client's MCP settings
https://api.clipspeed.ai/mcp
# Then ask Any MCP client:
> Post a one-line take on the launch to Threads at 9am
Any MCP client: Preview — nothing booked yet. Threads — text under 500. Book it?The transport is streamable HTTP. There is nothing to install locally and nothing to update.
- 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.
- Connect Threads in the ClipSpeed app, or ask Any MCP client for a connect link: it is private, valid for ten minutes, and Threads signs you in itself.
Developer reference: the Any MCP client MCP page.
What can Any MCP client do on Threads?
On Threads, Any MCP client can post 500-character text, images and video to Threads. Every booking runs through the same rules as the ClipSpeed app.
Text, Image and Video posts
Threads takes text, image and video through ClipSpeed. Video: MP4 or MOV up to 1 GB; up to five minutes on Threads. Image: JPG or PNG up to 25 MB.
500 characters, checked at booking
Threads's own arithmetic. Too long is refused with the real count, never trimmed at send time.
Exact time or refused
Name the minute and Any MCP client books it, or you are told why not and offered the next open slot. A booked Threads post is never moved behind your back.
Preview before anything posts
preview: true runs the whole booking and writes nothing. Any MCP client shows the plan, with each slot and the day's remaining cap, and books only on your yes.
Clips cut in the same chat
Submit a video or stream link, get captioned 9:16 clips with a viral score, and post the best as native video on Threads. No download, no re-upload.
Pacing and numbers
Planned: Text and image posts on Threads are at least 30 minutes apart, up to 10 a day. Video on Threads is at least 4 hours apart, up to 4 a day under your plan. After a post goes out, Any MCP client can read back views and engagement where Threads provides them.
How does Any MCP client post to Threads through ClipSpeed?
You describe what you want in plain language and Any MCP client makes the ClipSpeed calls. A typical conversation has three beats.
Find your Threads channel
Ask Any MCP client whether Threads is connected. It calls list_channels and reads platform_settings, so it also knows what Threads accepts and the limits before you write a word.
Compose within the rules
Describe the post. Any MCP client drafts within Threads's limits; mention a clip or a file and it attaches it.
Schedule or publish
Name a time, or say now. The slot is booked exactly or refused with the next open one, and the reply carries the id you can cancel or edit by.
Threads settings reference
These are the schedule_post fields that apply to Threads. Mention any of them in plain language and Any MCP client sets them; the server checks them at booking. Fields marked planned land with the Threads release.
| Field | Type | Required | What it does on Threads |
|---|---|---|---|
platforms | string[] | Yes | Include "threads". Up to ten platforms per call; each books its own slot. |
text | string | Yes for a text post | Up to 500 characters. One link per post is clickable. |
hashtags | string[] | No | Threads treats the first tag as its topic tag; keep it to one. |
media_kind | text | image | video | No | Detected from the file when omitted. |
clip_id or media_url | string | No | A ClipSpeed clip or a public link to an image or a video up to five minutes. |
scheduled_at | ISO 8601 | No | Exact or refused with the next open slot. |
preview | boolean | No | Plan only. |
Common Threads configurations
Ask Any MCP client for any of these and it applies the matching settings.
Short text post
Clip as video
Image with a topic tag
Ten posts, previewed
Example prompts for Threads in Any MCP client
Type these into any client that speaks the Model Context Protocol. Any MCP client calls ClipSpeed and confirms before publishing.
Post Threads with a scheduled time
Post a one-line take on the launch to Threads at 9am. Keep the text under 500 characters. Preview first.
Cut the clips, then post the best
Clip this link, keep the top three by viral score, and schedule them to Threads at 11am, 3pm and 7pm tomorrow. Show me the plan before booking.
Check and adjust the Threads calendar
What is scheduled on Threads this week? Cancel tomorrow's post and tell me the next open Threads slot on Friday.
Threads limits and gotchas to know
Threads enforces a few rules that Any MCP client and ClipSpeed respect automatically, but knowing them helps you phrase requests.
- 500 characters per post. Longer is refused at booking with the real count.
- Threads uses a single topic tag per post rather than a list of hashtags. Ask for one.
- Replies and multi-post threads are not part of the first release. One post per booking.
- Threads is the next rail. Until it posts, bookings to Threads are refused with a plain message and the badge says Coming soon.
- Planned pacing: ten text or image posts a day 30 minutes apart, video four hours apart.
| Rule | Threads |
|---|---|
| Accepts | Text, Image, Video |
| Text limit | 500 characters |
| Title | No title field |
| Links in the caption | Kept; one link per post is clickable |
| Pacing | Planned: Text and image posts on Threads are at least 30 minutes apart, up to 10 a day. Video on Threads is at least 4 hours apart, up to 4 a day under your plan. |
| Formats | Image: JPG or PNG up to 25 MB. Video: MP4 or MOV up to 1 GB; up to five minutes on Threads. Aspect: any; 9:16 or 1:1 |
| Status | Coming next on ClipSpeed's rail; bookings are refused with a plain message until then |
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 Threads. 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 on Threads. 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.
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.
How ClipSpeed works with Any MCP client
- 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_analytics for schedulingsubmit_to_clipspeed,check_clipsand the live-clipping tools for clipping- generate_image, generate_video, wait_for_generation for creation
- Every booking runs through the same rules as the web app
Hosted MCP vs stdio package vs CLI: Hosted MCP server (api.clipspeed.ai), clipspeed-mcp (npm) (your machine, stdio), ClipSpeed CLI (your machine). This page is about Any MCP client; the Any MCP client guide compares them.
{
"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
# Threads: text/image/video · text 500Post to Threads and other platforms from Any MCP client
One request can book the same content to Threads and other channels, each keeping its own settings and its own slot. Every platform below has its own Any MCP client guide.
Also works with
Threads and Any MCP client: frequently asked questions
How do I post to Threads from Any MCP client?
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. Connect Threads in ClipSpeed (or ask Any MCP client for a connect link; it is private and valid for ten minutes), then describe the post in plain language. Any MCP client reads the Threads rules, drafts within them, shows the plan and books on your yes. Threads is coming next; until the badge changes, the booking is refused with a plain message.
What can Any MCP client post to Threads through ClipSpeed?
Post 500-character text, images and video to Threads. Threads takes text, image and video posts. Text is limited to 500 characters.
Which Threads settings can Any MCP client control?
The fields in the settings reference above: text, hashtags, media_kind, clip_id or media_url, scheduled_at, preview. Mention any of them in plain language ("unlisted", "tomorrow at 9", "preview first") and Any MCP client sets the matching field before it books.
Do I need a Threads API key or developer account?
No. You connect Threads to ClipSpeed once through Threads's own sign-in, and Any MCP client talks to ClipSpeed over OAuth. No Threads developer key, bearer token or password is pasted anywhere.
How many Threads posts a day can Any MCP client schedule?
Planned: Text and image posts on Threads are at least 30 minutes apart, up to 10 a day. Video on Threads is at least 4 hours apart, up to 4 a day under your plan. When a time is taken, the booking is refused with the next open slot rather than moved. Ask for preview to see a day's plan and the remaining cap before anything is booked.
Can posts go out to Threads while I am away?
Yes. Once booked, ClipSpeed publishes at the scheduled minute whether or not Any MCP client is open. For unattended runs that decide what to post, use a headless agent such as Claude Code or Codex with the same account.
Is posting to Threads from Any MCP client different from clipspeed-mcp (npm)?
The booking is identical: the same rules, the same calendar, the same refusals. What differs is where you work. Any MCP client: hosted at api.clipspeed.ai. clipspeed-mcp (npm): your machine, stdio, local process; clipping plus clip scheduling.