Post from Claude
Connect PostWharf to Claude and publish or schedule to every network you run. Claude Desktop and claude.ai connect to the hosted MCP server directly. Ten of the fourteen networks publish today; Reddit, Discord, Snapchat and WordPress are available on request.
Connect it
claude mcp add --transport http \ wharf https://mcp.postwharf.com/mcp \ --header "Authorization: Bearer $POSTWHARF_KEY"
The key scopes every call to one workspace, so Claude 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
"Draft a launch post, queue it for Tuesday 9am on LinkedIn and X, and tell me once it is live."
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
The draft is usually already in the conversation by the time you decide to publish it. Connecting the server means the next step is another sentence, rather than a copy into another tab, a re-read, and a second decision about timing you had already made. That matters more than it sounds: most posts that never went out were finished.
Keep the approval step
Claude shows you the post before it queues it, and that pause is worth keeping even once you trust the setup. The receipt records what published; it cannot tell you what was worth publishing. The other thing worth knowing is that the workspace key scopes the connector to one brand, so an agent handed the wrong key cannot reach a workspace it was not given — which is the property you want as soon as you run more than one.