Add to Claude

MCP-first · BYO AWS SES · EU / DE compliant

Migrate off Brevo & Mailchimp to your own sending reputation.

EU-compliant email marketing you run entirely from Claude — no dashboard, your own SES, your consent trail intact.

Connect in Claude See how migration works
Sending cost via SES
$0.10 / 1k emails
Consent trail preserved
0%
Forced re-confirmations
0 — ever
claude — newslettermcp connected

Live transcript — this is the whole product. There is no dashboard.

01 — The migration

Your list is being held hostage.

Per-contact pricing punishes you for growing. Shared IPs lend your deliverability to strangers. And when you try to leave, the export strips your consent proof — so the next tool makes you re-confirm everyone, and a third of your list evaporates. That's not a technical necessity. It's a lock-in mechanism.

Before Renting a list you already own

  • Mailchimp, 25,000 contacts ≈ $270 / mo
  • Shared IP pool — someone else's spam run is your inbox placement problem
  • CSV export drops DOI timestamps & consent source
  • Re-import elsewhere → forced re-confirmation → 20–40% list decay
  • Every unsubscribe you still pay for, every month

After Your own infrastructure, intact list

  • Same list on your AWS SES — 100k emails / mo ≈ $10 / mo
  • Your own sending reputation — warmed, owned, portable
  • Consent status and timestamped trail imported field-for-field
  • Suppressions arrive as suppressed — bounces & complaints never re-mailed
  • Zero re-confirmation emails. Zero list decay. Audit-ready from day one.

Back in your pocket, year one

0

25k contacts · 4 sends / mo · Mailchimp Standard vs. AWS SES us/eu pricing. Your DOI proof rides along — German Double-Opt-In case law (BGH I ZR 164/09) is exactly why we never ask your subscribers twice.

02 — How it works

Three sentences. Not three tabs.

  1. 01

    Connect

    "Add newslettermcp and hook up my SES."

    One MCP connector. Claude verifies your DKIM, SPF and DMARC records, confirms your SES sandbox status, and you're live on your own domain.

  2. 02

    Migrate

    "Import my Brevo export — keep the consent trail."

    Contacts, DOI timestamps, consent source, tags, and suppression lists land exactly as they were. Suppressed stays suppressed. Nobody gets asked to opt in again.

  3. 03

    Send

    "Send the weekly. Follow up with non-openers in 3 days."

    Campaigns, automation flows, and per-link analytics — all conversational. Ask "how did Tuesday's send do?" and get real open and click numbers back.

03 — What's inside

Everything an ESP does. Nothing an ESP charges for.

  • Bring your own SES / SMTP

    Sends go out through your AWS SES account or any SMTP relay. The reputation you warm up is yours — and it leaves with you.

  • EU / GDPR + German DOI

    Double-opt-in flows built to German case-law standard, timestamped consent records, EU data residency. Audit-ready, not audit-anxious.

  • Automation flows

    Welcome series, re-engagement, date triggers — described in plain language, executed as durable flows. "If they don't open in 5 days, send the nudge."

  • Real open & click analytics

    Per-campaign, per-link, per-contact. Queryable in conversation: "compare the last four subject lines" is a sentence, not a CSV project.

  • Bounce & complaint suppression

    Hard bounces and spam complaints are auto-suppressed via SES feedback loops before they can dent your reputation. Imported suppressions honored forever.

  • One-click unsubscribe

    RFC 8058 List-Unsubscribe-Post on every send — the Gmail/Yahoo bulk-sender requirement, handled. Opt-outs propagate instantly across all flows.

04 — Why MCP-first

The dashboard was the product. Now it's overhead.

You already draft copy in Claude, plan campaigns in Claude, analyze results in Claude. The only reason you tab over to an ESP is to click the buttons it hides behind a paywall. NewsletterMCP removes the tab: every capability is an MCP tool your assistant calls directly — segment, schedule, send, report — with confirmation gates on anything irreversible.

  • Works where you work — Claude, Claude Code, ChatGPT, Cursor: anything that speaks MCP.
  • Composable — pipe your CRM, your product database, your changelog straight into a send.
  • Scriptable by prose — the API surface is the tool list. No SDK to learn, nothing to click.
// the entire interface
tools: [
  "import_contacts",   // consent trail intact
  "create_campaign",
  "send_campaign",     // via your SES
  "create_flow",
  "get_analytics",
  "suppress_contact",
  "export_everything"  // no lock-in, ever
]
runs in Claude Claude Code ChatGPT Cursor

Your list. Your SES. Your reputation.

Add the connector, say "migrate my list," and watch the tool-calls run. Migration is free and reversible — export_everything is a tool too.

Connect in Claude