The situation, in one table
Search "Mailchimp MCP server" and you will find an official Mailchimp docs page, which is how most people end up confused: that server belongs to Mailchimp Transactional, the developer product formerly called Mandrill, and it cannot see your campaigns, audiences or reports. As of August 2026 there is still no official MCP server for the Mailchimp marketing platform. Three routes exist, and they suit different people.
| Route | What it reaches | The catch |
|---|---|---|
| Official Transactional MCP mandrillapp.com/mcp | Transactional email only: API integration help, template building, failed-send diagnosis. Nine tools, aimed at developers wiring up receipts and password resets. | Not your marketing account. Needs the paid Transactional add-on on a Standard plan or higher. If you came for campaigns, this is the wrong server. |
| Community servers marketing API | The real surface: campaigns, audiences, segments, templates, reports, classic automations. The largest covers most of the marketing API with 227 tools; a smaller one ships 18 curated tools with a one-click Claude Desktop bundle. | An API key in a config file, desktop only, and trust in a small open-source project. This is the route that works, and it is a developer-shaped route. |
| Hosted aggregators Zapier MCP and similar | Around 30 Mailchimp actions (create and send campaigns, manage subscribers, pull reports) behind a personal remote URL, which also works on claude.ai in the browser. | A third party in the middle with its own account, pricing and limits. Fine for light use, awkward as the backbone of your email program. |
Why this page is the exception in the gallery. Our email tools list only recommends ESPs a marketer can connect without an API key, and Mailchimp does not clear that bar: Brevo, Klaviyo and others have official OAuth connectors, Mailchimp does not. If you are still choosing an ESP for agent work, that comparison is the page to read. If you are on Mailchimp and staying, read on.
The practical setup, step by step
The workable marketer path today is a community server on Claude Desktop. The setup below uses the most complete one; the same shape applies to the others.
Create a Mailchimp API key
In Mailchimp: Account → Extras → API keys → Create a
key. Copy it somewhere safe; it ends in your data
centre code, like -us8. API keys are available on
every plan, including free.
Add the server to Claude Desktop
In Claude Desktop, open Settings → Developer → Edit
Config and add the server with your key. The
uv Python runner needs to be installed once; the
server itself downloads on first use.
{"mcpServers": {"mailchimp": {
"command": "uvx", "args": ["mailchimp-mcp"],
"env": {"MAILCHIMP_API_KEY": "your-key-us8",
"MAILCHIMP_READ_ONLY": "true"}}}}
Note the read-only flag. Leave it on for the first week; flip it when you trust the setup. If config files are a dealbreaker, the smaller community server ships a one-click bundle you install from a file instead.
Verify with something read-only
List my Mailchimp audiences with their member counts, and my five most recent campaigns with open rates. Don't change anything.
What the community route can do
- Campaigns end to end. Create a campaign, set its content, send a test, schedule or send it, and pull the report afterwards: opens, clicks, unsubscribes, domain performance, even Mailchimp's own advice endpoint.
- Audiences and segments. List and search members, add and update them, tag them, build segments, read growth history.
- Templates, with an asterisk. Read and create templates as raw HTML. The drag-and-drop builder templates are not editable over the API, and on the free Mailchimp plan template writes are read-only.
- Reports across the account. Everything the reports tab shows, queryable in a sentence, which is the part that earns its keep first.
What none of the routes can do
- Customer Journeys are invisible. Mailchimp's modern automation builder has no public read API, so no MCP server can list, build or edit journeys. Only the old classic automations are even listable, and the single journey write is triggering one contact into a journey. If automations are the heart of your Mailchimp use, the connector cannot see the heart.
- The official server will not touch marketing. No campaigns, no audiences, no reports, by scope. It exists to help developers integrate transactional sending.
- Nothing runs on its own. No triggers, no watching an audience, no acting when a campaign finishes. Everything happens inside a conversation you start.
- The usual sending rules apply. Verified domains, plan-level send limits, and on the free plan (around 500 sends a month in 2026) not much room to experiment.
Where Plainpaper fits
The community servers can send, which is exactly why a review step belongs in front of them. On a Plainpaper board the agent drafts the campaign as cards: subject lines, body, the segment it targets, and you approve the rendered email before anything is created in Mailchimp, let alone sent. The Claude and Mailchimp workflow guide runs that loop, and the Canva and Mailchimp guide adds the visual half.
Key takeaways
- Mailchimp's only official MCP server is for Mailchimp Transactional (the old Mandrill): nine developer tools, a paid add-on, and no access to campaigns or audiences.
- The marketing platform is reachable only through community servers (up to 227 tools, API key in a config file, desktop only) or hosted aggregators like Zapier MCP.
- Customer Journeys cannot be read, built or edited by any route; the API does not expose them. Classic automations are listable, and that is it.
- Template writes are raw HTML only, and read-only on the free plan.
- Start any community server in read-only mode, and keep sending as a deliberate, human, final step.
Frequently asked questions
Is there an official Mailchimp MCP server?
For the marketing platform, no. Mailchimp's official MCP server, launched in 2026, covers Mailchimp Transactional only: programmatic email like receipts and password resets. Campaigns, audiences and reports are not in its scope, and Mailchimp has not announced a marketing equivalent.
Can Claude build and send Mailchimp campaigns at all?
Yes, through a community MCP server for the marketing API. The largest exposes campaign creation, content, scheduling, sending and reporting. It needs a Mailchimp API key in Claude Desktop's config file, which is the part that makes this a developer-shaped setup.
Does any of this work on claude.ai in the browser?
The community servers do not; they run locally on your machine, which claude.ai cannot reach. The browser route is a hosted aggregator like Zapier MCP, which gives you a personal remote URL and around 30 Mailchimp actions through Zapier's own account and pricing.
Does it work on the free Mailchimp plan?
Mostly. API keys are available on every plan, so the community servers connect fine. The free plan's limits still bind: around 500 sends a month in 2026, and template writes are read-only until you pay.
Why can't it see my Customer Journeys?
Because Mailchimp's API cannot. Journeys have no public read endpoint, so every MCP server is blind to them; the only write is triggering a single contact into a journey. The old classic automations can be listed, but building or editing any automation flow stays in Mailchimp's interface.
Should I switch ESPs over this?
Not over this alone, but if agent workflows matter to you, the gap is real: Brevo, Klaviyo, MailerLite and others offer official OAuth connectors you add in two clicks, with no key and no config file. Our email tools comparison scores them side by side.
Keep reading
- Claude and Mailchimp workflow: brief to finished campaign, with the approval step where it belongs.
- Canva and Mailchimp with Claude: the visual half of the campaign, designed on-brand and assembled into the send.
- Best email template tools for Claude: the ESPs whose connectors clear the no-API-key bar, scored honestly.
- Welcome series playbook: the first flow to fix, whichever ESP sends it.
- Draft email campaigns in Plainpaper: email cards, A/B variants, and the ESP handoff.