Post to X from Codex CLI

What Codex CLI can do with calmposts

Codex reads your repository, runs commands and edits files. With calmposts as an MCP server it can also announce the work: a thread when a pull request lands, a short post for each release, a draft for every item in the changelog.

Codex reads the instructions calmposts sends when it connects and follows them alongside the tools: check the accounts and the limits first, prefer the queue or a draft, never reply, follow or send DMs. The same config.toml serves the Codex CLI, the IDE extension and the ChatGPT desktop app, so you set calmposts up once.

calmposts' X (Twitter) MCP server gives Codex CLI 11 tools, the same set every client gets:

Set up calmposts in Codex CLI

Check the key before you start

Create a key in calmposts under API & MCP (it's shown only once), then ask the server for its tools. A list of 11 tools means the address and the key are right; a 401 means the key is wrong or was sent without “Bearer ”.

curl -s https://calmposts.com/mcp \
  -H "Authorization: Bearer cp_live_…" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
# 200 {"jsonrpc":"2.0","id":1,"result":{"tools":[…]}}

Setup 1: One command, with the key in an environment variable

Codex stores only the variable's name; the key stays in your shell.

1. Create a key in calmposts under API & MCP and export it in the shell you start Codex from, for example in ~/.zshrc:

   export CALMPOSTS_API_KEY=cp_live_…

2. Add the server. Codex sends the variable's value as a Bearer token:

   codex mcp add calmposts --url https://calmposts.com/mcp --bearer-token-env-var CALMPOSTS_API_KEY

3. Check it: calmposts is listed with its URL. In the Codex TUI, /mcp shows it with its tools.

   codex mcp list

Setup 2: Straight into config.toml

The same entry by hand, in ~/.codex/config.toml or in a trusted project's .codex/config.toml.

1. Add the table. The last line is optional: writes makes Codex ask before any tool that isn't marked read-only, and calmposts marks list_* and get_* read-only.

   [mcp_servers.calmposts]
   url = "https://calmposts.com/mcp"
   bearer_token_env_var = "CALMPOSTS_API_KEY"
   default_tools_approval_mode = "writes"

2. Start codex and run /mcp: calmposts is listed with its 11 tools.

Signing in: a key or OAuth

bearer_token_env_var names an environment variable, and Codex sends its value as Authorization: Bearer with every request. If the variable isn't set where Codex starts, no key goes out and calmposts answers 401 missing_api_key.

Codex can also sign in to MCP servers with OAuth (codex mcp login calmposts), but that path hasn't been tested with calmposts yet. The key is the setup this page was checked with.

Give Codex a key of its own, with only the permissions it needs, so you can revoke it in API & MCP without touching your other agents.

Check that it works

• codex mcp list shows calmposts with its URL.
• In the TUI, /mcp lists calmposts and its tools; /mcp verbose adds the server's diagnostics.
• Ask “What are my calmposts limits today?”: Codex calls get_limits and reads back your plan and the posts left today.
• Ask for a draft and find it under Posts in calmposts, with the source mcp.

Prompts to try

Ask in your own words and the agent picks the tools. A few that work well:

• “Read the diff of the last merged PR and write an X post about what changed. Save it in calmposts as a draft.”
• “Turn CHANGELOG.md's 3.1 section into a thread for X and Bluesky and put it in the calmposts queue.”
• “Draft one post for each release tag this month and spread them over next week's free slots.”
• “What's scheduled in calmposts for Friday? Fix any post that's over the X limit.”

Networks, threads and approval

Posts go to X and Bluesky. A thread goes out as a reply chain on X and Bluesky. Coming soon: Threads and LinkedIn.

Write once, post everywhere: your agent sends one text for every account it picks. If the text is longer than a network allows, calmposts posts it there as a thread, splitting at a paragraph break, then at the end of a sentence, then at a space, with nothing numbered or added. calmposts checks each network's rules and your plan's limits before it saves the post and names the field that's wrong, so the agent can fix the text and try again.

By default your agent's posts wait for you. They come back as pending_approval, and you approve or reject each one in the app, in Telegram or from the email calmposts sends. The workspace owner can let agents publish on their own, but only when both the workspace and the API key are set to publish. X expects an account that posts automatically to carry its Automated label (Settings → Your account → Account information → Automation).

Which networks work today→

Limits and costs

• Agents need a paid plan: the Free plan has no API keys and can't approve connected apps. API keys per plan: Pro 3 · Advanced 10 · Agency 25.
• Your agent's posts count the same as yours. Posts a day: Pro 20 · Advanced 100 · Agency 300. Posts with a link per month: Pro 30 · Advanced 300 · Agency 600. Each post in a thread counts.
• Posts with a link are counted separately because X charges every app $0.015 per post and $0.20 per post with a link. Your plan includes X's fees, so you don't need an X developer account or an X API bill of your own.
• Try it first: 7-day free trial. Card required. 5 posts with a link during the trial.
• Each key can make 60 requests a minute across MCP and REST; beyond that, the server returns 429 with Retry-After.

Pricing→

What to know about Codex CLI

• Codex gives a server 10 seconds to start and 60 seconds per tool call by default (startup_timeout_sec, tool_timeout_sec). calmposts answers in well under a second; create_post with images takes longest, while calmposts downloads them.
• enabled_tools and disabled_tools trim what Codex sees, for example disabled_tools = ["delete_post"].
• A project's .codex/config.toml is read only in trusted projects; ~/.codex/config.toml applies everywhere.
• Codex's docs ask servers to keep the first 512 characters of their instructions self-contained; calmposts' open with what to call first, list_accounts and get_limits.

Without MCP: the REST API

Everything the tools do is also a REST call under /api/v1 with the same key, which suits a script or a workflow step that only speaks HTTP. calmposts posts through its own approved X app, so you don't need X API keys of your own.

export CALMPOSTS_API_KEY=cp_live_…
curl -H "Authorization: Bearer $CALMPOSTS_API_KEY" https://calmposts.com/api/v1/accounts
curl -X POST https://calmposts.com/api/v1/posts \
  -H "Authorization: Bearer $CALMPOSTS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"parts":[{"text":"Calm posts, scheduled."}],"targets":[{"account_id":"ACCOUNT_ID"}],"schedule":{"mode":"queue"}}'

REST API docs→

The Codex CLI docs this page follows

• Codex docs: Model Context Protocol (CLI)
• Codex docs: Configuration reference
• Codex docs: Commands

calmposts is an independent service and is not affiliated with or endorsed by the makers of Codex CLI. Product names belong to their owners.