Table of contents
Is there an official Mailchimp MCP server? Only half of one. Mailchimp runs an official Model Context Protocol (MCP) server for its Mandrill transactional email product at mandrillapp.com/mcp — 9 tools, authenticated with a static Bearer API key, no OAuth flow. The Marketing API that most marketing teams actually want an AI agent working against — audiences, campaigns, automations, reports — has no official server at all. Every option for connecting an agent to that side of Mailchimp is community-built.
This information is correct as of September 2026.
That gap catches people out, because the assumption is reasonable: Mailchimp is one of the most widely used marketing platforms, and HubSpot ships an official remote MCP server for its own Marketing Hub data, so it’s natural to expect the same from Mailchimp. It doesn’t exist yet. Here’s what the official server does cover, and how the community options that fill the rest compare.
What the official Mandrill MCP server actually does
Mandrill is Mailchimp’s transactional email product — the triggered, one-to-one emails a product sends automatically, like password resets, order confirmations, and account notifications, as distinct from the bulk marketing campaigns sent from Mailchimp’s Marketing Hub. The official MCP server at mandrillapp.com/mcp exposes 9 tools scoped to that job: sending transactional messages, working with templates, and checking message status and delivery info.
Auth is a static Bearer API key rather than an OAuth flow. That’s simpler to set up than HubSpot’s OAuth 2.1 connector, and it means the server can run unattended in a scheduled job or an agent-triggered workflow with no person present to approve access. The tradeoff is the usual one with static keys: there’s no per-user scoping or session expiry, so treat the key with the same care as any other production credential.
The tool set is deliberately narrow. If your workflow is “send this transactional email” or “check whether that message delivered,” the official server covers it. It has no visibility into audiences, campaigns, automations, or reports — that’s a different product, with no official server of its own.
The Marketing API gap: community options fill it
Ask an AI agent to segment an audience, draft a campaign, or pull campaign performance, and you’re outside what the official server can do. Mailchimp hasn’t shipped an MCP server for the Marketing API, so the field is entirely third-party. Five options currently cover it, at very different levels of completeness.
damientilman/mailchimp-mcp-server
The most complete option by a wide margin: an open-source, self-hosted package covering 227 tools against Mailchimp’s Marketing API, spanning audiences, campaigns, automations, templates, and reporting. Authentication is your own Mailchimp API key, stored wherever you run the server. The breadth makes it the closest thing to a full Marketing API surface available to an agent today, at the cost of self-hosting and keeping it updated yourself.
Apify’s hosted server
Apify runs a hosted Mailchimp MCP server exposing 56 tools, trading some of damientilman’s breadth for zero infrastructure to manage. It’s a reasonable middle ground if your team already uses Apify for other scraping or automation work and wants Mailchimp reachable from the same account without standing up a new server.
StackOne
StackOne’s Mailchimp connector exposes 91 actions through its unified integration platform, with managed OAuth and session-scoped tokens rather than a long-lived static key. If your team already routes other tools through StackOne for its governance and audit trail, adding Mailchimp is incremental rather than a new integration to manage from scratch.
Zapier MCP
Zapier exposes Mailchimp as one of the 9,000+ apps reachable through its own MCP server, authenticated the same way as any other Zapier-connected app. Coverage maps to whatever Zapier’s existing Mailchimp integration supports rather than the full Marketing API surface, but it’s the fastest path for a team already living in Zapier.
Pipedream
Pipedream’s Mailchimp connector is reachable through its own MCP server via a static per-client URL, drawing on the same integration Pipedream maintains for its workflow automation product. Similar tradeoff to Zapier: convenient if Mailchimp is one piece of a broader automation you’re already building there, less compelling as a standalone Mailchimp integration.
Mailchimp MCP server options compared
| Mandrill MCP (official) | damientilman/mailchimp-mcp-server | Apify | StackOne | Zapier MCP | |
|---|---|---|---|---|---|
| Status | Official, maintained by Mailchimp | Independent, open source | Independent, hosted | Independent, hosted | Official Zapier product |
| Purpose | Transactional email only | Full Marketing API | Marketing API | Marketing API | Marketing API, via Zapier’s existing app connector |
| Hosting | Remote, hosted by Mailchimp | Self-hosted | Remote/cloud | Remote/cloud | Remote/cloud |
| Auth | Static Bearer API key | Your own Mailchimp API key | Managed by Apify | Managed OAuth, session-scoped tokens | Zapier’s existing auth model |
| Tool count | 9 | 227 | 56 | 91 actions | Varies with Zapier’s Mailchimp app |
| Best for | Triggered transactional sends and status checks | Teams wanting the most complete Marketing API coverage and willing to self-host | Teams wanting a hosted option with no infrastructure to manage | Teams already governing other tools through StackOne | Teams already building automations in Zapier |
For most marketing teams, the choice comes down to how much Marketing API surface you need and whether you’re willing to self-host. damientilman/mailchimp-mcp-server is the most complete option today, in the same way the community fills the gap left by Segment’s lack of an official server — a pattern that keeps showing up wherever a platform’s most valuable data lives behind an API its vendor hasn’t wrapped in MCP yet.
Marketing-team use cases
Once connected, the Marketing API options open up work that today means logging into the Mailchimp dashboard directly:
- Audience segmentation — an agent reads existing audience and tag data to propose or build new segments based on engagement history, rather than a manual export and filter.
- Campaign drafting — pulling recent campaign structure and copy into a planning conversation, so a new campaign starts from what worked last time instead of a blank editor.
- Performance reporting — asking an agent for open rates, click rates, and unsubscribes across recent campaigns and getting an answer sourced from live Mailchimp data, without a dashboard export.
The transactional side, by contrast, is mostly infrastructure: an agent triggering a password-reset or order-confirmation email as part of a larger workflow, not a marketing task in itself.
About Growth Method
An MCP server gets an AI agent read access to your Mailchimp data, or in the case of the official Mandrill server, the ability to send a transactional email. What it doesn’t give you is a way to turn that access into a measured piece of work. Growth Method is the agentic marketing platform for B2B teams: plan a campaign as a testable hypothesis grounded in your live data, launch it with the before-metrics already recorded, and let agents pull the after-numbers from your connected tools once results are in. Connect Mailchimp alongside your analytics and CRM stack, and an audience segment or a campaign performance dip stops being a one-off report and becomes a planned, launched, and analysed campaign, for people and agents alike.
Get started to connect your stack and run your next campaign from live data, not a dashboard export.
Frequently asked questions
Is there an official Mailchimp MCP server?
Only for Transactional email. Mailchimp runs an official MCP server for its Mandrill transactional product at mandrillapp.com/mcp, with 9 tools authenticated by a static Bearer API key. The Marketing API — audiences, campaigns, automations, reports — has no official server; every option for it is community-built.
What’s the difference between the Transactional and Marketing API options?
The official Mandrill server only covers transactional sending: templates, message status, and sending-related tools for triggered, one-to-one email. It has no access to audiences, campaigns, automations, or reports, which is the Marketing API most marketing teams actually want an agent working against. That side is served entirely by community projects such as damientilman/mailchimp-mcp-server, Apify’s hosted server, StackOne, Zapier MCP, and Pipedream.
Is it free?
The official Mandrill MCP server is free to use with any Mandrill account, though Mandrill sending itself is a paid add-on. On the Marketing API side, the open-source damientilman/mailchimp-mcp-server package is free but self-hosted, so you carry the running cost; Apify, StackOne, Zapier and Pipedream are hosted options that are typically free at low volumes and gate heavier usage behind a paid tier.
Can it run headlessly or unattended?
The official Mandrill server can, since it authenticates with a static Bearer API key rather than an interactive OAuth flow, which suits scheduled or agent-triggered jobs. On the Marketing API side, self-hosting damientilman/mailchimp-mcp-server with a stored API key also supports unattended use; the hosted community options vary, so check each provider’s auth model before relying on it for a job with no person present.