Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Mailchimp to Claude Code

Have Claude draft campaigns and manage your audience in Mailchimp. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Mailchimp to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Mailchimp, you add a Mailchimp MCP server: a small hosted service that exposes Mailchimp's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Mailchimp account. No API keys pasted into config files.

claude mcp add --transport http mailchimp https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Mailchimp once connected?

Full read-write Mailchimp access lets Claude draft a campaign, populate the content, set the audience and segment, and queue it for your approval before sending. It can add or update subscribers, apply tags, and manage merge fields, so list hygiene and campaign prep happen where your audience already lives.

  • Draft a campaign with subject line and content, set the audience, and leave it for review
  • Add or update subscribers in an audience, including merge field values
  • Apply or remove tags to segment contacts for a targeted send
  • Create or update an audience segment from a described set of criteria
  • Schedule or send a prepared campaign after you approve it
  • Update a subscriber's status, such as resubscribing or marking unsubscribed

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Mailchimp access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Mailchimp API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Mailchimp changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Mailchimp connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Mailchimp connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Mailchimp account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Mailchimp's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Mailchimp?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Mailchimp account it signs in with. Revoking access is one click in Mailchimp.

More on the Mailchimp connector

Mailchimp connector for claude.aiKlaviyo + Claude CodeActiveCampaign + Claude CodeMarketo + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us