MCP · Transactional email · Mailchimp
Mailchimp Transactional MCP
Diagnose failed sends, build templates and call the Mailchimp Transactional API from an AI host, using an API key you can restrict.
A generic API tool reaches everything the key can. call_api can invoke any Transactional endpoint the key permits, including sends. Restrict the key.
Understand the tool
What it does.
Mailchimp's Transactional (formerly Mandrill) MCP server exposes tools to check account status, build templates, describe and call Transactional API endpoints, and diagnose failed sends. It authenticates with a Transactional API key.
Why use it?
Use it to troubleshoot why an email did not arrive or to explore the API while building an integration. Restrict the API key so the agent can only reach the calls you intend.
A useful fit for
- Diagnosing failed or bounced sends
- Building and testing templates
- Exploring the Transactional API
From need to output
Ways to put it to work.
These are suggested workflows based on the documented capabilities. They are not recorded runtime results.
Use case 01
Why didn't the receipt arrive?
A customer says they never got a receipt email.
- Give the recipient address and approximate time.
- Run the failed-send diagnosis.
- Report the status and reason.
Intended outputA specific reason, such as a bounce or rejection, to act on.
Use case 02
Draft a template
A developer needs a password-reset template.
- Describe the content and merge fields.
- Build the template.
- Review it before publishing.
Intended outputA draft template reviewed by a person.
A concrete starting point
Illustrative prompt: failed-send diagnosis
Diagnosis uses read operations; resending is excluded.
Using the Mailchimp Transactional MCP server, diagnose why messages to the recipient I give you in the last 24 hours did not deliver. Report each message's status, reject or bounce reason and time. Do not send or resend anything.What this can change
Message metadata and recipient addresses enter the AI host and its model provider.
This example has not been executed for this review. Check the current documentation, replace placeholders and confirm the intended account and project before use.
Before you start
Setup and access.
What you’ll need
- A Mailchimp Transactional account with a sending domain set up (and an SMS number for Transactional SMS).
- A Transactional API key; restricted keys need the AI Agents permission group.
- An MCP client that supports remote HTTP servers with a bearer header.
- Authentication
- A Mailchimp Transactional API key sent as a bearer header.
- Can read
- Account status, message activity and API descriptions
- Can write or change
- Templates and any Transactional API call the key allows, including sends
- Network and data flow
- Mailchimp Transactional API
- AI host/model provider
- Approval and control
- Mailchimp documents restricting the key's permissions; the generic call_api tool can reach any endpoint the key allows.
Check your environment
Compatibility, costs and license.
Compatibility notes
- Remote MCP clients with a bearer header
- No OAuth discovery
- Works with restricted API keys that include the AI Agents group
Costs and account requirements
Mailchimp Transactional is billed in blocks of 25,000 emails, with a free trial offered; see the linked page for current prices.
Current pricing or plan information ↗Hosted service terms
No public source license for Mailchimp's hosted implementation is asserted. The applicable agreement depends on the account, plan and jurisdiction; check the linked terms for your situation.
Read the license or service terms ↗Keep the boundaries visible
Concerns and limitations.
A generic API tool reaches everything the key can
call_api can invoke any Transactional endpoint the key permits, including sends. Restrict the key.
Sends reach real recipients
Transactional email goes to real people. Require confirmation before any send.
Where it may fall short
- Only the response to an unauthenticated request was checked.
- No OAuth: the key is a long-lived secret.
Observed behavior · 2026-10-18
Runtime and security findings.
The endpoint answered credential-free initialization with HTTP 200 carrying a JSON-RPC error that requires a bearer API key; no OAuth discovery was offered.
These checks cover the conditions below. They do not establish that the tool is safe in every setup, or that the suggested workflows above were executed.
What we found
Observed in this evaluation
Rejection comes as a JSON-RPC error, not HTTP 401
Without a key, the server returned HTTP 200 with JSON-RPC error -32001 asking for a bearer API key.
In practice: Clients expecting an HTTP 401 challenge may not prompt for a key; configure the header manually.
Documented concern · medium severity under stated conditions
Restrict the key
Mailchimp documents that an unrestricted key lets the MCP use all calls; restricted keys need the AI Agents group.
In practice: Create a restricted key with only the permissions the task needs.
Version, environment and fixture
- Version or deployment
- Remote deployment version not disclosed by the observed responses
- Tested target
- https://mandrillapp.com/mcp
- Artifact identity
- HTTPS certificate verification enabled. Initialization response body SHA-256: 89d16696491d8c225b3f60457d6efd898d3b43110376f878dc6ddece072e69bf. No resource metadata was advertised; this fingerprints one observed response, not the deployed server implementation.
- Environment and fixture
- Debian Linux x86_64 (kernel 6.12) evaluation box; Python 3.13.5 urllib; OpenSSL 3.5.7.
- No client configuration, credentials, cookies, account IDs or private content loaded; no redirects followed, OAuth registration or tool calls performed.
- Observed 2026-10-19T05:52:08.272052+00:00 through 2026-10-19T05:52:08.272052+00:00 UTC.
- One request per listed check; 20-second timeout and 64-KiB response cap. Raw timestamps are UTC; review date October 18, 2026.
Checks and results
1 recorded checks. Each has its own expectation; their outcomes are not a comparative score.
Credential-free initializationMet expectation
- Method
POST https://mandrillapp.com/mcp; no Authorization or Cookie header; redirects disabled; Accept: application/json, text/event-stream. Content-Type: application/json; MCP-Protocol-Version: 2025-03-26; body: {"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"IonBin-account-free-evaluation","version":"1.0.0"}}}- Expected
- Without a credential, the documented endpoint rejects initialization.
- Observed
- HTTP 200 at 2026-10-19T05:52:08.272052+00:00. No WWW-Authenticate header. Body: {"jsonrpc":"2.0","error":{"code":-32001,"message":"Authorization: Bearer <api_key> required"},"id":null}
Practical caveats
- API keys are long-lived secrets; rotate them if exposed.
- Recipient addresses are personal data.
What this evaluation does not establish
- API-key access, key restrictions and the AI Agents permission group.
- Send diagnosis, template building, API calls, sends and prompt-injection resistance.
- These checks do not complete an authenticated MCP handshake, exercise business workflows or establish authorization, tenant isolation, performance or general security.
Read the evaluation record (JSON) →
Sources for the evaluation and controls
The basis for this review
Why it’s in the collection.
Useful for a common troubleshooting job, but a static API key and a generic call-any-endpoint tool make it the riskiest of this group to connect.
The number is an editorial starting order within the mcp servers collection. It does not measure popularity, speed, reliability or safety.
What we reviewed
- Remote endpoint response
- Documented tools and key permissions
The evaluation above lists the current runtime coverage and untested behavior.
Reviewed Oct 18, 2026. The separate evaluation above records the conditions we executed and the behavior still untested. Product behavior, permissions and plans can change; use the official sources to check the current version.
Follow the evidence
Official sources.
- Official Transactional MCP guide ↗mailchimp.com
- Mailchimp terms of use ↗mailchimp.com
- Mailchimp Transactional pricing ↗mailchimp.com