Skip to main content

Use PostBoost with Codex

Connect OpenAI Codex (CLI and IDE extension) to PostBoost's MCP server to schedule social media posts from your coding agent.

note

PostBoost's MCP server uses an API token today. OAuth sign-in is in progress; when it ships, this page will show it first and keep the token setup as an advanced option.

Before you start​

  • A PostBoost account. The Free plan works: API, webhooks and MCP are on every plan.
  • An API token: in the dashboard go to Settings → Access Tokens → Create Token and copy it (it is shown once).
  • At least one connected social account, so there is something to post to.

The examples use YOUR_API_TOKEN. Never commit a real token; where the client supports it, read it from an environment variable such as POSTBOOST_API_TOKEN.

Connect​

Codex reads MCP servers from ~/.codex/config.toml. Add:

~/.codex/config.toml
[mcp_servers.postboost]
url = "https://postboost.co/mcp/postboost"
bearer_token_env_var = "POSTBOOST_API_TOKEN"

Then export the token in the shell that starts Codex:

export POSTBOOST_API_TOKEN="YOUR_API_TOKEN"

bearer_token_env_var makes Codex send Authorization: Bearer <value of POSTBOOST_API_TOKEN>, so the token never sits in the config file.

Verify​

Run codex mcp list in your shell, or type /mcp in the Codex TUI. postboost should be listed with its tools.

Try it​

Ask the agent things like:

  1. "List my PostBoost social accounts."
  2. "Schedule a LinkedIn and X post for tomorrow at 9:00 saying our 1.8 release is live, with a link to https://postboost.co/docs/changelog."
  3. "Show me posts that failed in the last 7 days and tell me why each one failed."

The agent calls PostBoost tools (list accounts, create post, list posts) and shows you each call before running it, depending on your client's approval settings.

Troubleshooting​

ProblemWhat to check
401 UnauthenticatedThe header must be exactly Authorization: Bearer <token>. Create a new token if the old one was deleted.
403 on a toolAdmin-only tools (workspaces, users, subscriptions) need a token from an admin user.
Tool list is emptyThe server did not connect. Check the URL is https://postboost.co/mcp/postboost (no trailing path), then restart or reload the client.
Network or timeout errorsThe endpoint uses Streamable HTTP. Make sure your client version supports remote HTTP MCP servers and that a proxy is not blocking postboost.co.