mailchimp-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAILCHIMP_API_KEY | Yes | Your Mailchimp API key (format: key-dc, e.g. abc123-us21) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_audiencesB | List all Mailchimp audiences/lists. Returns list IDs needed for campaign creation. |
| list_templatesB | List available Mailchimp email templates. |
| list_campaignsC | List recent Mailchimp campaigns. |
| get_campaignC | Get details of a specific campaign by ID. |
| create_campaignB | Create a new Mailchimp email campaign. Returns the campaign ID for use with set_campaign_content and send_campaign. |
| set_campaign_contentB | Set the HTML/plain-text content for a campaign. Provide either html for custom content or template_id to use a Mailchimp template. |
| get_campaign_contentB | Get the current HTML and plain-text content of a campaign. |
| send_test_emailB | Send a test email for a campaign before sending to the full audience. |
| send_campaignA | Send a campaign to its audience. This action is irreversible — the campaign will be sent immediately. |
| schedule_campaignC | Schedule a campaign to send at a specific time in the future. |
| list_membersA | List members/subscribers in a Mailchimp audience. Use for syncing or auditing contacts. |
| add_or_update_memberA | Add a new subscriber or update an existing one in a Mailchimp audience. Uses email as the unique key (upsert). Will not change subscription status of existing members. |
| batch_add_membersA | Add multiple subscribers to a Mailchimp audience in one call. Handles up to 500 members per batch. Will not overwrite existing members' subscription status. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose with no overlap: member management, campaign operations, audience listing, and template handling are all well-separated. For example, add_or_update_member and batch_add_members serve different use cases (single vs. bulk), and campaign tools like create_campaign, send_campaign, and schedule_campaign cover distinct lifecycle stages.
Tool names follow a highly consistent verb_noun pattern throughout, such as list_audiences, create_campaign, get_campaign, and send_campaign. All tools use snake_case with clear, descriptive verbs that align with their actions, making the set predictable and easy to navigate.
With 13 tools, the count is well-scoped for a Mailchimp integration, covering core operations like audience management, campaign creation, sending, and content handling. Each tool earns its place by addressing specific needs without redundancy, fitting typical MCP server ranges for this domain.
The tool surface provides comprehensive coverage for Mailchimp's key workflows, including CRUD-like operations for campaigns and members, listing resources, and campaign lifecycle management. A minor gap exists in missing update/delete operations for campaigns or members, but agents can work around this with existing tools like add_or_update_member for updates.