Hey Reader,
For ten years my job was APIs. I created AsyncAPI, I ran engineering at Postman, I wrote a book about getting event-driven architecture adopted. Then I started building a newsletter platform and told myself it would be a break from all that.
It wasn’t.
One of the first people to pay for Commune runs his whole newsletter workflow from Claude. On our first call he told me he’d keep nagging until Commune had an MCP server. He kept his word.
So I built one. And an API under it. And a developer portal on top: usecommune.dev.
What it looks like
Later today, Commune’s own newsletter goes out. I wrote it in Markdown, in my code editor, next to my code. Then I told Claude Code to send it. It created the issue through Commune’s MCP server, sent me a test, waited for my OK, and scheduled it. I recorded the whole thing:
It works the other way too. You can ask your newsletter questions and get answers from your real subscriber data. Here’s a prompt to spot readers going quiet before they unsubscribe:
“Find readers I’m about to lose. For each one, give their email, what they stopped doing and when they were last active. Strongest first, top twenty. Then tell me who from last week is no longer on the list.”
Two more worth trying:
- “Read what readers said about my last three issues: replies, highlights and conversations. Suggest three topics for my next issue, quote the passage behind each, and say how many readers raised it.”
- “Find my superfans. Mark who’s new this week and who’s cooling off.”
For the API nerds
- Versioned by date in a header (Commune-Version), so your integration doesn’t break when I ship.
- Idempotency keys on every write. Retry safely and you get the first response back.
- Three separate rate-limit budgets (general, audience, write), each reported in the headers.
- 60 operations and 23 webhooks, all in a published OpenAPI document, plus llms.txt so your agent can read the docs itself.
- MCP tools named as questions (who_is_drifting_away, find_superfans) instead of one tool per endpoint.
Why bother
Most newsletter platforms treat your audience as theirs. Substack has no API at all. If you can’t get your data out or automate around it, you’re renting. Commune is the opposite bet: everything you can click, your code can call.
One honest caveat. Publishing and sending through the API only works for newsletters that send with Commune.
Try it
- Point your agent at https://api.usecommune.com/mcp and approve the consent screen. In Claude Code that’s one line: claude mcp add –transport http commune https://api.usecommune.com/mcp
- Or grab an API key in Commune’s settings and follow the quickstart at usecommune.dev.
And if you build something on it, hit reply. I want to see it.
Cheers ✌️
Fran
Pst! I see you're not on Commune yet. Click here to join us!
