Local MCP server

Let Codex CLI publish what it just wrote

Codex CLI works in your terminal against your code. Add SchedPilot and the output of a session can become a scheduled post rather than something you summarise later from memory.

Start for free Full docs

Setup

Connect Codex CLI in three steps

Create an API key

In SchedPilot, open API Access and generate a key. It starts with smm_.

Add the MCP server

Drop the configuration below into Codex CLI, using your key.

Restart and ask

Restart Codex CLI and ask it to list your connected accounts.

{
  "mcpServers": {
    "schedpilot": {
      "command": "npx",
      "args": ["-y", "schedpilot-mcp"],
      "env": { "SCHEDPILOT_TOKEN": "smm_your_key" }
    }
  }
}

Replace smm_your_key with the key from API Access in your SchedPilot account.

Once connected

What Codex CLI can do

get_accounts

List every connected social account, with its id and type.

create_post

Schedule a post to one or many accounts, with media, a thread and a video title.

list_posts

Read scheduled and published posts, filtered by date or status.

delete_post

Cancel a scheduled post before it goes out.

upload_media

Upload an image or video from a URL and get a media id back.

get_analytics

Read impressions, reach, likes, comments and shares for a published post.

Rate limits are 150 read and 100 write requests per hour, per user. Scheduling a post with media costs two writes.

Why Codex CLI

The work and the write-up in one session

Write-ups get skipped because they happen after the interesting part is over. Doing it in the same session, with the agent that has the context, is the only version that reliably happens.

Drafts from real work rather than a blank prompt
Scriptable for release pipelines
Approval still required before anything publishes

Try asking it

Things that work well once Codex CLI is connected.

“Summarise what we changed today and schedule a post for 9am.”

“Draft a thread explaining this refactor for X.”

“Show me the posting queue.”

Treat anything scheduled from an automated session as a draft. The approval step in your calendar is what keeps unattended runs safe.

FAQs

Codex CLI questions

Can it run unattended?

Yes, and posts still wait for your approval, so an unattended run cannot publish on its own.

Does it need its own key?

No — one SchedPilot key works across every client.

Can it publish without my approval?

No. Scheduling queues a post; it waits in your calendar until you approve it. That holds for every agent and every connection method.

Using something else?

There is a setup guide for every agent we support, plus a REST API for anything that is not on the list.

See all agents

Connect Codex CLI to SchedPilot

Free to start, and every post waits for your approval.

Start for free