Post from Codex
Connect PostWharf to Codex and publish or schedule to every network you run. OpenAI Codex reaches the same twenty-one tools over the hosted MCP endpoint. Ten of the fourteen networks publish today; Reddit, Discord, Snapchat and WordPress are request-only: PostWharf cannot publish to them yet.
Connect it
# Point the connector at: https://mcp.postwharf.com/mcp # with the header: Authorization: Bearer YOUR_WORKSPACE_KEY
The key scopes every call to one workspace, so Codex can only ever act on the brand you hand it — not on every account you run. Find it in the dashboard under API keys.
Then just ask
"Post the deploy summary to our Telegram channel."
The agent drafts and queues; the delivery receipt tells you what actually published, including if a post is removed by the platform afterwards. You keep the approval step.
What it can reach
Twenty-one tools: read the workspace and its channels, describe what each network accepts, connect a channel, upload media and describe an image, create a post, schedule one or a batch, save drafts, list and edit them, publish a draft, edit anything still in the queue, list the queue, cancel, check status, retry the networks that failed, read the receipt feed, and a health check. Full reference.
Where this actually happens
Alongside whatever else the agent has been asked to finish. The post reads best as the last step of a task rather than a task of its own, because the agent already knows what it just did, and that is most of what an announcement needs to say.
Say what changed, not that something changed
An agent asked to “post about the update” will write something true and empty. Asked to post about the specific thing it just finished, it has the details: what was broken, what it does now, who it affects. That is the difference between a post somebody reads and one they scroll past. Keep the approval step for the same reason — the agent can tell you what happened, not whether it was worth saying.