Skip to main content
The OpenAI Codex CLI supports streamable HTTP MCP servers via ~/.codex/config.toml. Wire Carousify in and you can ask Codex to draft posts, schedule them, or pull analytics from any terminal session — globally or scoped to a single repo.
Codex CLI added support for streamable HTTP MCP servers in late 2025. Make sure you’re on a recent version (codex --version) — older builds only support stdio servers.

​
Before you start

You’ll need:
  • MCP enabled on the workspace — see MCP overview for the one-click flow
  • An MCP key from Manage Workspace › MCP (only shown once, right after creating it)
  • Codex CLI installed and authenticated (codex login)

​
Step 1 — Copy your Carousify MCP URL

In Carousify, open Manage Workspace › MCP. Use the auto-provisioned MCP System Key or click Create API Key to mint a fresh one (e.g. codex-cli). Your MCP URL has this shape: 
https://app.carousify.com/api/mcp?token=YOUR_MCP_KEY
Treat the MCP URL like a password. Anyone with it can act on your workspace. Carousify reveals the full key only once — copy it the moment it’s generated.

​
Step 2 — Add Carousify to Codex

1

Run codex mcp add

The fastest path. The token is part of the URL, so no separate auth flag is needed:
codex mcp add carousify --url "https://app.carousify.com/api/mcp?token=YOUR_MCP_KEY"
Codex writes the entry to ~/.codex/config.toml and verifies the connection.
2

Or edit ~/.codex/config.toml directly

Open (or create) ~/.codex/config.toml and add:
[mcp_servers.carousify]
url = "https://app.carousify.com/api/mcp?token=YOUR_MCP_KEY"
To keep the token out of the file, set it in your shell environment and reference it through Codex’s bearer-token field:
export CAROUSIFY_MCP_TOKEN="your_mcp_key"

[mcp_servers.carousify]
url = "https://app.carousify.com/api/mcp"
bearer_token_env_var = "CAROUSIFY_MCP_TOKEN"
The env-var route is the cleaner choice if you commit dotfiles or share config.toml between machines — your config.toml stays free of secrets.
3

Verify the connection

Quit any running Codex sessions, then run:
codex mcp list
You should see carousify in the list with status connected and a count of discovered tools.

​
Step 3 — Use it from a Codex session

Start a session (codex) and try:
  • “Using Carousify, draft a LinkedIn post about today’s release notes and schedule it for 9 AM IST tomorrow.”
  • “List my scheduled Carousify posts for this week.”
  • “Pull analytics for the post I published yesterday.”
Codex picks the matching Carousify tool, asks for your approval the first time, and runs it.
Be explicit about Carousify in the prompt the first few times. Codex routes on tool descriptions, so naming the server helps it land on the right call.

​
Disconnect or rotate

  • Disconnect — run codex mcp remove carousify, or delete the [mcp_servers.carousify] block from config.toml.
  • Rotate the key — in Carousify, delete the row in MCP Keys, click Create API Key to mint a new one, and update the URL (or env var) in Codex.

​
Troubleshooting

  • codex mcp list shows “failed” — the token is wrong or revoked. Confirm the key shows Active in Manage Workspace › MCP and the URL ends with the full token, not the masked XXXX... version.
  • Codex doesn’t pick the Carousify tool — be explicit in the prompt (“using Carousify, …”). The agent uses tool descriptions for routing, so naming the server helps.

​
What’s next

MCP overview

How MCP keys, tools, and workspace scoping fit together.

Use it from VS Code

Same MCP URL, inside VS Code’s chat agent.

Use it from Claude

Custom connector setup for Claude web, desktop, and Claude Code.

Schedule a post

Quick refresher on how scheduling works inside Carousify.