Mailchimp MCP server
Mailchimp's official MCP server for Transactional Email (Mandrill): explore the API, build templates, and diagnose failed sends from your agent.
The Mailchimp Transactional MCP server is Mailchimp's official hosted integration for Mailchimp Transactional Email, the service formerly known as Mandrill. Instead of jumping between the Mandrill dashboard, the API reference, and your editor, an agent can ask the server what endpoints exist, get a precise description of any endpoint's parameters and schema, call the API directly, and build message templates — all in one connected loop. It is designed to make wiring up transactional sends (receipts, password resets, shipping notifications, and other one-to-one mail) fast and correct, with onboarding guidance and a dedicated tool that diagnoses why a particular send failed.
The canonical deployment is the hosted remote endpoint at https://mandrillapp.com/mcp over Streamable HTTP. It authenticates with your Mandrill API key passed as a bearer token in the Authorization header; restricted keys need the "AI Agents" permission group enabled. Clients without native remote support can bridge to it with npx mcp-remote https://mandrillapp.com/mcp. Note this is the transactional surface — for audience, campaign, and automation management you would use Mailchimp's Marketing API rather than this server.
Quick install
Copy-paste configs are provided for all 8 supported clients. Pick your client below.
Add to ~/.claude.json
{
"mcpServers": {
"mailchimp": {
"type": "http",
"url": "https://mandrillapp.com/mcp",
"headers": {
"Authorization": "Bearer <MANDRILL_API_KEY>"
}
}
}
}claude mcp add --transport http mailchimp https://mandrillapp.com/mcpAvailable tools
| Tool | Description |
|---|---|
| account_status | Checks the status of your Mailchimp Transactional (Mandrill) account. |
| list_api | Lists the available Transactional Messaging API endpoints. |
| describe_api | Describes a specific API endpoint, including its parameters and schema. |
| call_api | Calls a Transactional Messaging API endpoint with the supplied parameters. |
| integrate_api | Helps integrate your application with the Transactional Messaging API. |
| build_template | Builds or constructs a transactional email template. |
| diagnose_failed_send | Diagnoses why a transactional message send failed. |
| onboarding | Provides onboarding assistance for getting started with Transactional Email. |
| submit_feedback | Submits feedback about the MCP server or Transactional Email experience. |
Required configuration
- MANDRILL_API_KEYRequired
Mailchimp Transactional (Mandrill) API key, passed as a bearer token in the Authorization header. Restricted keys must have the 'AI Agents' permission group enabled.
What you can do with it
Wire up a transactional send correctly the first time
The agent lists the available endpoints, describes the exact parameters for the messages send call, and generates working integration code so a receipt or password-reset email goes out without trial and error.
Diagnose a delivery failure
When a transactional message bounces or rejects, the agent calls the diagnose tool to surface the underlying reason and suggest the fix, instead of you digging through Mandrill logs by hand.
FAQ
- Is it free?
- The MCP server itself is free to connect; it works within your existing Mailchimp Transactional (Mandrill) plan and that account's sending limits and pricing. You need a valid Mandrill API key.
- Does it support remote/OAuth?
- It is a hosted remote server at https://mandrillapp.com/mcp over Streamable HTTP. Authentication is by Mandrill API key passed as a bearer token in the Authorization header rather than an interactive OAuth flow.
- Does this manage Mailchimp audiences and campaigns?
- No. This server is scoped to Mailchimp Transactional Email (Mandrill) — one-to-one mail like receipts and resets. Audience, list, and marketing-campaign management lives in Mailchimp's separate Marketing API.