Newsletter Caddie has no dashboard to operate — it is built for AI. Connect it to Claude or any MCP-aware app and your assistant builds the list, writes the issue, schedules the send, and tells you what got clicked.
Most tools hand you one rigid subscriber record and expect every list to fit it. Here each list declares exactly the fields it needs — and nothing else gets in.
Open rates stopped meaning anything the day Apple began pre-fetching images, so we do not report them. Clicks are the one signal a recipient really sends, and every issue is measured on them: how many went out, how many people clicked, and which link earned it.
Sent, total clicks, and unique clickers — so a handful of enthusiasts clicking ten times never reads as a hit.
Every call to action counted separately, so you can see which one carried the issue instead of guessing from a single rate.
Engagement feeds straight back into who gets the next one — re-engage the quiet, or send the follow-up only to people who clicked.
Newsletter tools bury the work in template builders, segment builders and campaign wizards. Newsletter Caddie removes all of it — every capability is a tool your AI can call, so the interface is simply your conversation. It is built so an autonomous agent can run the whole thing.
Newsletter Caddie is an MCP server — any MCP-aware AI, like Claude, can drive it.
Add Newsletter Caddie as a connector in Claude (or your MCP client) and authorize it once. Verify your sending domain and you are ready to send.
“Add these 400 signups,” “write issue 12 in our template,” “send it Thursday at 10am to anyone we haven't mailed in a month.” Plain language is the interface.
It calls the right tools — contact_import, template_create,
journey_schedule, journey_report — and reports back. Guide
it, or let it run.
There is no newsletter dashboard to operate — every capability is a tool your AI calls over MCP, so you run the whole thing by chatting. There is a lightweight account portal for signing in, connecting your AI assistant, reviewing connected apps and billing, but no newsletter work happens there.
Claude today, and any MCP-aware AI client. You connect the MCP server once and authorize it — no per-seat accounts to set up.
Because they are not real. Apple Mail Privacy Protection pre-fetches the tracking image whether or not anyone read the message, so an open rate mostly measures Apple. We report clicks — total, unique clickers, and a breakdown per link — which is a signal the recipient actually sent.
One flag on the subscriber, checked before every send, and nothing else can override it. Unsubscribing is the only way out of a sequence. Every template must carry an unsubscribe link — the platform refuses to save one without it — and hard bounces unsubscribe themselves, so the list cleans as it sends.
Yes, and you should. Each project gets its own verified sending domain with SPF, DKIM, DMARC and a custom envelope domain, so mail authenticates as you rather than as us — which is what keeps it out of spam.
Everything, unlimited — subscribers, lists, issues and sends — plus full MCP access for any AI client, and a REST API for signup forms and for triggering a send from your own systems. One flat price, no metering.
Everything included — grow without watching a usage meter.