I built an MCP server so founders can schedule social posts without leaving their editor
One friction point I kept hitting with my own tool: I'd finish shipping something, want to post about it while the context was fresh, then lose the thread switching apps.
So I built an MCP server for XreplyAI. One config line in .mcp.json and Claude Code (or Cursor, or any MCP client) gets tools to create, schedule, and publish posts across 8 platforms — without leaving the editor.
The part that makes it more than a gimmick: XreplyAI trains on your tweet archive, so when you ask Claude to draft a post about what you just shipped, the output is in your voice. Not a template, not "as an AI language model" — your actual writing patterns.
BYOK model. You bring your own Gemini, OpenAI, or Claude key. ~$1–5/mo in AI costs, no markup from me.
A few things I learned building it:
- MCP over HTTP with OAuth 2.1 is surprisingly well-specced for a new protocol. Cloudflare Workers + Durable Objects made the remote deployment straightforward.
- Distribution-as-MCP-tool is an interesting pattern. The people most likely to want this are exactly the people already living in Claude Code.
- The hardest part wasn't the protocol — it was making sure "schedule a post" had enough guardrails that it wouldn't accidentally publish half-written drafts.
If you're building in public and already in the Claude Code workflow, it might be worth 5 minutes to wire up.
https://xreplyai.com?utm_source=indiehackers&utm_medium=social&utm_campaign=feature-2026-06-01
This is a strong wedge because the timing is right: the best post usually happens right after shipping, while the context is still fresh.
I’d be careful not to lead too heavily with “MCP server” though. Builders will understand it, but the emotional pain is probably not the protocol. It is losing the moment between shipping something and actually turning it into a useful public update.
The sharper promise might be closer to:
“Turn what you just shipped into scheduled founder posts without leaving Claude Code or Cursor.”
That makes XreplyAI feel less like another social scheduling tool and more like a distribution layer built directly into the builder workflow.
For early users, I’d target people already doing build-in-public posts weekly, not generic creators. They will feel the pain fastest because they are already trying to turn product progress into distribution.