Schedule social media posts with Codex
One command adds ClipSpeed to Codex. It reads the repo, writes the release post, cuts the demo into clips and books everything, or does it unattended with codex exec.
- codex mcp add, OAuth or API key
- Reads release notes and docs to write posts
- codex exec runs a prompt 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: Codex shows the plan and you approve it.
Also try
How to connect ClipSpeed to Codex
One command writes the server into Codex's config. Start codex, sign in to ClipSpeed when it asks, and the tools are available.
1 · Connect · about a minute
codex mcp add clipspeed --url https://api.clipspeed.ai/mcpCodex stores MCP servers in ~/.codex/config.toml under [mcp_servers.clipspeed]. You can also paste the block by hand.
2 · Then ask
- Run codex mcp add clipspeed --url https://api.clipspeed.ai/mcp in your terminal.
- Start codex. On first use of a ClipSpeed tool it opens the OAuth sign-in; approve it.
- Ask it to list your channels to confirm.
- On a runner without a browser, set the server's bearer token to a ClipSpeed API key in config.toml instead.
Want ChatGPT instead? It is a connector URL in Developer mode: see the ChatGPT guide. Developer reference: the Codex 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 Codex 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 Codex?
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 |
|---|---|---|---|---|
| codex mcp add (this page) | codex mcp add clipspeed --url https://api.clipspeed.ai/mcp | OAuth on first use | Full: scheduling, clipping, generation | Most Codex users |
| config.toml with a key | [mcp_servers.clipspeed] url = "…" plus a bearer token env | ClipSpeed API key | Full | CI and servers |
| ChatGPT connector | Developer mode → Connectors | OAuth | Full | Planning by conversation |
The same server works with every other agent too: see the MCP server page and the AI agents overview.
Why use Codex for social media with ClipSpeed?
Codex brings the context: the terminal and IDE. 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.
Release notes become posts
Codex reads CHANGELOG.md or the tag diff and writes the X and LinkedIn versions with each platform's limit respected.
codex exec for cron
A single prompt, no session, exits when done. Nightly digests and release announcements without anyone at a keyboard.
Approval mode you choose
Codex's approval settings govern tool calls. Keep approvals on for scheduling; 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 Codex books, so a hurried prompt cannot flood a platform or post the same thing twice.
What is Codex?
Codex is OpenAI's coding agent. It runs in the terminal (codex), inside IDEs, and in the cloud, reads your codebase, runs commands and calls MCP tools. With ClipSpeed added as an MCP server, Codex can clip a video, generate images and video, and schedule posts, interactively or from a script with codex exec.
Codex vs ChatGPT
| Surface | Where it runs | Who it is for | How ClipSpeed connects | Notable difference |
|---|---|---|---|---|
| Codex | Terminal, IDE, cloud | Developers | codex mcp add | This page. Repo access; codex exec for unattended runs. |
| ChatGPT | chatgpt.com | Anyone | Custom connector | Conversation first; confirms each write. |
Where it runs
Terminal, VS Code and other IDEs, codex cloud.
Who it is for
Developers who want the release to announce itself.
Status with ClipSpeed
Verified end to end. ClipSpeed has driven Codex end to end: install, sign-in, clip, schedule.
How ClipSpeed works with Codex
Once connected, Codex 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.
- codex mcp add writes the server into config.toml; Codex discovers the tools at start
- It reads
platform_settingsbefore writing so limits are met schedule_postis exact or refused with the next open slot; nothing moved quietlypreview: truereturns the plan with nothing bookedcodex exectakes one prompt and exits, for cron and CI
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.
# Written by: codex mcp add clipspeed --url https://api.clipspeed.ai/mcp
[mcp_servers.clipspeed]
url = "https://api.clipspeed.ai/mcp"
# For a runner with no browser, authenticate with an API key instead:
# bearer_token_env_var = "CLIPSPEED_API_KEY"
# Verify
$ codex "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
Codex 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. Codex 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. Codex 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: Codex 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: Codex as a publisher nobody has to babysit
codex exec as a publisher. Codex's non-interactive mode makes it a scheduler you can call from anything that can run a command. A GitHub Action after a release, a cron entry at eight in the morning, a Makefile target: each runs one prompt, Codex writes the copy from the repository and books the posts through ClipSpeed, and the booking rules stop it from double-posting or flooding a platform.
#!/bin/bash
# Every weekday at 08:00
codex exec "Read docs/updates/$(date +%F).md if it exists. Write one X post under 280 characters and one LinkedIn post under 1,000. Schedule both via ClipSpeed for 10:00 today. If a slot is refused, take the next open one it suggests and tell me."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 Codex to do?
Anything the ClipSpeed tools expose: channels, posts, media, clips, generation and analytics. Four typical requests and what Codex does with each. Copy one and change the names.
Tag to posts
Summarise the changes since the last git tag as one X post and one LinkedIn post, and schedule both via ClipSpeed for 10am today.
Clip the demo
Clip ./media/demo.mov, keep the top three, and post them to TikTok at 1pm, 3pm and 5pm with captions from the transcript.
Docs to a week
Read the five files in docs/tips and schedule one LinkedIn post a day at 8:30am next week. Preview first.
From a script
codex exec "Post the summary of today's merged PRs to X at 6pm via ClipSpeed; under 280 with the link counted as 23."
Which platforms can Codex post to?
ClipSpeed posts today to YouTube, TikTok, Instagram, X (Twitter) and LinkedIn. Every platform below has a dedicated Codex guide with the settings reference, the limits and example prompts. The badge is the truth: only a platform marked posting today can be booked.
Codex and ClipSpeed: frequently asked questions
How do I connect ClipSpeed to Codex?
One command writes the server into Codex's config. Start codex, sign in to ClipSpeed when it asks, and the tools are available. Run codex mcp add clipspeed --url https://api.clipspeed.ai/mcp in your terminal. Start codex. On first use of a ClipSpeed tool it opens the OAuth sign-in; approve it. Nothing else is installed, and the same account you use in the ClipSpeed app is the one Codex books into.
Do I need a paid ClipSpeed plan to schedule from Codex?
Scheduling needs an active ClipSpeed plan or the $1 trial, and it is included on every paid plan at no extra cost. Codex itself is billed by OpenAI under your own account. Connect during the trial, book a few posts, and the plan screen in ClipSpeed takes it from there.
Is Codex the same as ChatGPT?
No. Codex: terminal, ide, cloud, repo access; codex exec for unattended runs. ChatGPT: chatgpt.com, conversation first; confirms each write. All of them reach the same ClipSpeed account and the same calendar; this page covers Codex.
What can Codex 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 Codex books a post, ClipSpeed holds it and publishes at the scheduled minute whether or not the session is open. For runs where Codex 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 Codex 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 Codex never sees the platform at all. Codex authenticates to ClipSpeed over OAuth, so no key is pasted anywhere, and it can only reach channels already connected in your account. Keep Codex's confirmation step on for anything that goes live.
Which platforms can Codex 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 Codex guide with a settings reference and the limits that apply.
Codex 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 Codex to list channels again.
How do I add ClipSpeed to Codex?
Run codex mcp add clipspeed --url https://api.clipspeed.ai/mcp. Start codex, approve the ClipSpeed sign-in on first use, and the tools are there. The server lands in ~/.codex/config.toml under [mcp_servers.clipspeed].
Can Codex schedule posts without me at the keyboard?
Yes. codex exec "…" runs a single prompt and exits; put it in cron or a CI step. On a machine without a browser, authenticate the server with a ClipSpeed API key in config.toml.
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.