Connect PostNext to Codex in three steps
Open the Codex config
Codex reads MCP servers from config.toml in your .codex folder. Open it, or create it if it does not exist.
Add the server
Paste the block below. Codex picks the HTTP transport automatically when an entry has a url instead of a command. On an older Codex that only reads stdio servers, also set experimental_use_rmcp_client = true under [features], or upgrade.
[mcp_servers.postnext] url = "https://mcp.postnext.io/api"Sign in on first use
Start Codex. The first time it calls a PostNext tool it opens the PostNext sign-in screen in your browser; approve it once and the token is kept for 30 days.
MCP API URL:https://mcp.postnext.io/api
What you can ask
Show me everything scheduled for this week and flag the gaps.Draft a Friday recap thread for X and a shorter version for Threads.Which of my LinkedIn posts got the most engagement in the last 30 days?
Tools your assistant can call
- Generate a one-time link to authorise a new social channel.
- Draft a new post (won't auto-publish).
- Move a draft into the publish queue at a future time.
- Read your queued posts before they go out.
- Fetch likes, comments, shares and impressions for a published post across every connected platform.
- Recommend the best (dayOfWeek, hour) slots for the next post on a given platform, ranked by engagement over the past 90 days.
Frequently asked questions
Do I need a paid plan?
No. The free plan gives you read access and draft creation. Only get_account_health (the 30-day analytics summary) requires a paid plan: Basic, Pro, Teams or Business.
How do I revoke access?
Disconnect from your AI client's settings, or open your account page on PostNext and remove the client. Tokens also auto-expire after 30 days of inactivity.