Intuit Mailchimp
Plan omnichannel marketing campaigns and save them to Mailchimp as drafts from an AI agent. Anthropic lists 12 tools; none sends email. Mailchimp states campaigns arrive as drafts and that you finalize and send from Mailchimp. OAuth sign-in, one scope.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Intuit Mailchimp via MCP
https://ai-inc.mailchimp.com/claude/mcp/v2Works in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Intuit Mailchimp Tools & Capabilities (12)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Mailchimp publishes no tool list for this server. The 12 names come from Anthropic's directory. We searched Mailchimp's help center, both of its Claude connector pages, and all 677 URLs in its developer sitemap; the only MCP page describes the separate Transactional server. No vendor enumeration exists to diff the 12 against, so do not size this connector's reach from the listing alone.
- We could not read tool schemas or safety annotations. The endpoint returned HTTP 403 to an anonymous request, so no parameter-level detail is published here. A send flag hidden in a parameter is the one hiding place this page's evidence cannot fully close, though Mailchimp documents the outcome as a draft in two places.
- The scope list draws no boundary.
scopes_supportedcontains exactly one value,mailchimp. A single scope cannot separate reading your campaign history from writing into your account, so the consent screen offers no way to grant one without the other. - No connector-side confirmation exists before a write. Your MCP client's tool-approval prompt is the only gate on
save-to-mailchimp. Confirmation dialogs in Mailchimp's web interface guard the send step and do not constrain an agent. - Mailchimp's own marketing copy overstates the reach. Its Claude resource page says in one paragraph that you can "launch campaigns all from one conversation", and in another that you move into your Mailchimp account to finalize and send. The second statement matches the help article and the API structure; read the first as marketing.
- The connector is narrow by design. Mailchimp's troubleshooting says the connector is focused on campaign planning, editing and saving, and that Claude may not be able to help with tasks outside those through the connector. There is no audience management, list import, subscriber editing or reporting tool in the listing.
- Anthropic lists only two client families. The directory's
works_withfield names Claude and the Claude API. Mailchimp's own connector documentation covers Claude only. Other MCP clients may work, but neither party documents them for this server. - No rate limits are published for this endpoint. Mailchimp documents rate limits for its Marketing and Transactional APIs, but neither connector page states a limit for the MCP server, and we did not test one. Treat the ceiling as unknown rather than absent.
- The host's OAuth metadata leaks a second deployment. The bare
/.well-known/oauth-protected-resourceonai-inc.mailchimp.comreturns a descriptor formc-chatgpt-mcp.mailchimp.com, an unrelated ChatGPT-facing host, rather than for the Claude endpoint. The path-suffixed descriptor is the correct one. This is a metadata defect, not a security finding, but a client that probes only the bare root will be pointed at the wrong resource and the wrong authorization server. - The directory's documentation URL 301s. Anthropic publishes
mailchimp.com/help/use-mailchimp-connector-claude, which redirects to the trailing-slash canonical. We cite the destination.
Frequently asked questions
No. Mailchimp's help article states campaigns arrive in your account as drafts, and its Claude resource page says you move into Mailchimp to finalize and send. No tool among the 12 Anthropic lists carries a send verb, and Mailchimp's Marketing API keeps sending as a separate action endpoint that has no counterpart in the listing.
A distinct API action, not a field. Mailchimp's Marketing API reference documents creating a campaign as one operation and sending it as a separate action endpoint, alongside separate schedule, cancel, test-send and resend actions. A campaign sits in saved status until one of those send actions runs. The connector's save tool reaches the first operation only.
Only your MCP client's own tool-approval prompt. Mailchimp documents no connector-side confirmation for saving a campaign, and any confirmation in Mailchimp's web interface guards the send step that this connector never reaches. Treat your client's approval dialog as the sole gate, and do not blanket-approve the save tool.
Twelve, per Anthropic's directory snapshot dated 2026-08-16. Mailchimp publishes no tool list for this server anywhere in its help center, its two connector articles, or its 677-page developer sitemap. So 12 is a floor from one party's listing, not a total either party confirms, and no second enumeration exists to diff it against.
One scope, named mailchimp. The server's RFC 9728 descriptor declares scopes_supported containing that single value, and its authorization server metadata repeats it. A one-value scope list draws no boundary at all, so nothing at the OAuth grant separates reading your campaign history from writing a draft into your account.
Yes, for existing accounts. Mailchimp's resource page states Claude connects directly to your data and that recommendations draw on your actual campaign history, audience engagement patterns and performance benchmarks. For new accounts with no history, Mailchimp says the integration falls back to its own aggregate industry data instead.
No, and the difference matters. Mailchimp runs a second MCP server at mandrillapp.com for Transactional Messaging, keyed by API key rather than OAuth. That one ships a tool that calls any Transactional API endpoint, and its own documentation gives sending an email as an example prompt. It is not the connector on this page.
Active accounts on both platforms and permission to authorize integrations. Mailchimp's help article states you need an active Claude account and a Mailchimp account, plus a user role able to authorize third-party integrations in both platforms, which it says is usually Owner or Admin. It also states your Mailchimp data is not used to train Claude.
Sources
- Mailchimp help center, "Use the Mailchimp Connector in Claude" (retrieved 2026-08-22). Anthropic's directory publishes the non-trailing-slash form, which 301s here. · retrieved 2026-08-22
- Mailchimp resources, "Smarter campaigns with the Mailchimp x Claude Connector" (retrieved 2026-08-22) · retrieved 2026-08-22
- Mailchimp Marketing API reference, Campaigns (retrieved 2026-08-22). Source for the separate create, send, schedule, cancel, test and resend action endpoints. · retrieved 2026-08-22
- Mailchimp developer guide, "How to Use Mailchimp's Transactional Messaging MCP" (retrieved 2026-08-22). The separate server, its nine tools and its example send prompt. · retrieved 2026-08-22
- Mailchimp Transactional API reference (retrieved 2026-08-22). Source for the 99-endpoint count reachable through that server's dispatcher tool. · retrieved 2026-08-22
- Mailchimp machine-readable page index,
llms.txt(retrieved 2026-08-22). A 988-page content analysis dated 2025-07-29 containing no MCP or connector content. · retrieved 2026-08-22 - Mailchimp
robots.txt(retrieved 2026-08-22). Fully permissive, noContent-Signaldirective. · retrieved 2026-08-22 - Live OAuth posture check, RFC 9728 metadata at
https://ai-inc.mailchimp.com/.well-known/oauth-protected-resource/claude/mcp/v2, and authorization server metadata athttps://ai-inc.mailchimp.com/claude/.well-known/oauth-authorization-server(2026-08-22) · retrieved 2026-08-22 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Mailchimp support — · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Intuit Mailchimp
- Tools
- 12
- Domain
- ai-inc.mailchimp.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.