Post from Cursor
Connect PostWharf to Cursor and publish or schedule to every network you run. Post from the editor — useful when the thing you are announcing is the thing you just shipped. Ten of the fourteen networks publish today; Reddit, Discord, Snapchat and WordPress are available on request.
Connect it
{
"mcpServers": {
"wharf": {
"url": "https://mcp.postwharf.com/mcp",
"headers": { "Authorization": "Bearer YOUR_WORKSPACE_KEY" }
}
}
}
The key scopes every call to one workspace, so Cursor 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
"Summarise this changelog entry and queue it for 9am."
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
Fifteen tools: list channels, create a post, schedule one, save it as a draft, list and edit drafts, publish one, edit anything still in the queue, cancel, check status, read the receipt feed, register media, describe an image, connect a channel, and a health check. Full reference.
Where this actually happens
In the editor, with the changelog or the release notes already open in front of you. The useful pattern is turning a diff into an announcement: the file that changed is the context, so the post does not have to be written from memory once the details have gone.
Announcements go stale fastest
The gap between shipping something and saying so is where most release posts die. By the time there is a moment to write one, the specifics have to be reconstructed, and the reconstruction is always worse than the original would have been. Writing it while the change is on screen removes that gap. Queue it rather than publishing immediately if the deploy has not landed yet — a post about a release that is not out is a worse problem than a late one.