@m6b9/mcp-mailchimp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAILCHIMP_API_KEY | Yes | Your Mailchimp API key (format xxx-usXX) |
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 |
|---|---|
| pingA | Test connection and get Mailchimp account info |
| list_audiencesA | List all Mailchimp audiences (lists) |
| get_audienceC | Get details of a specific Mailchimp audience |
| list_audience_activityB | Get recent activity feed for an audience |
| create_audienceB | Create a new audience/list with contact info and campaign defaults |
| update_audienceC | Update audience settings |
| delete_audienceA | Permanently delete an audience/list |
| list_membersB | List members of a Mailchimp audience |
| get_memberA | Get a specific member by email from an audience |
| search_membersA | Search for members across all audiences by email or name |
| add_memberC | Add a new subscriber to an audience |
| update_memberC | Update an existing member in an audience |
| archive_memberB | Archive (soft-delete) a member from an audience |
| tag_memberA | Add or remove tags on a member |
| delete_memberA | Permanently delete a member from an audience (irreversible, unlike archive) |
| list_campaignsB | List Mailchimp campaigns |
| get_campaignC | Get details of a specific campaign |
| create_campaignC | Create a new email campaign |
| update_campaignC | Update campaign settings |
| set_campaign_contentB | Set the HTML content of a campaign |
| send_campaignB | Send a campaign immediately. This action is irreversible. |
| schedule_campaignB | Schedule a campaign for a future date/time |
| delete_campaignA | Permanently delete a campaign |
| get_campaign_contentB | Get the HTML/text content of a campaign |
| list_templatesB | List Mailchimp email templates |
| get_templateA | Get a specific template with its HTML content |
| create_templateB | Create a new email template |
| update_templateA | Update an existing template's name or HTML |
| delete_templateC | Delete a template |
| list_template_foldersB | List template folders |
| create_template_folderC | Create a template folder |
| delete_template_folderB | Delete a template folder |
| list_reportsA | List campaign reports with performance stats |
| get_campaign_reportA | Get detailed performance report for a specific campaign (opens, clicks, bounces, etc.) |
| list_segmentsC | List segments for an audience |
| get_segmentA | Get details of a specific segment |
| list_segment_membersB | List members in a segment |
| create_segmentB | Create a new segment (static or saved/conditional) |
| update_segmentB | Update a segment's name or conditions |
| delete_segmentC | Delete a segment |
| list_tagsB | List all tags for an audience |
| create_tagB | Create a new tag for an audience |
| delete_tagC | Delete a tag from an audience |
| list_merge_fieldsA | List merge fields (custom fields) for an audience |
| get_merge_fieldB | Get details of a specific merge field |
| create_merge_fieldB | Create a new merge field for an audience |
| update_merge_fieldC | Update a merge field's properties |
| delete_merge_fieldA | Delete a merge field from an audience |
| list_automationsA | List automation workflows |
| get_automationB | Get details of a specific automation workflow |
| list_automation_emailsC | List emails in an automation workflow |
| get_automation_emailA | Get details of a specific automation email |
| list_interest_categoriesB | List interest categories (groups) for an audience |
| get_interest_categoryB | Get details of a specific interest category |
| list_interestsB | List interests within a category |
| get_interestB | Get details of a specific interest |
| list_conversationsC | List conversations (inbox messages) |
| get_conversationC | Get details of a specific conversation |
| list_conversation_messagesB | List messages in a conversation thread |
| list_filesA | List files in the Mailchimp file manager |
| get_fileB | Get details of a specific file |
| upload_fileA | Upload a file to the Mailchimp file manager (max 10MB) |
| delete_fileB | Delete a file from the file manager |
| list_file_foldersB | List folders in the file manager |
| get_file_folderA | Get details of a specific file folder |
| create_file_folderB | Create a new folder in the file manager |
| delete_file_folderB | Delete a folder from the file manager |
| list_verified_domainsA | List all verified sending domains |
| get_verified_domainA | Get verification status of a specific domain |
| create_verified_domainC | Add a domain for verification |
| send_domain_verification_emailB | Resend verification email for a domain |
| delete_verified_domainC | Remove a verified domain |
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 72 tools
Most tools follow a distinct resource+action pattern, and descriptions clarify boundaries (e.g., archive_member vs delete_member). A few pairs like search_members vs list_members or list_reports vs get_campaign_report could cause minor confusion, but overall the purposes are clear.
All tools use snake_case and predominantly follow verb_noun conventions (list_, get_, create_, update_, delete_). Exceptions like ping and search_members are still predictable and do not break the pattern.
At 72 tools, the surface is very large. While it covers many Mailchimp resources, the sheer number makes it heavy and potentially overwhelming for an agent; some resources could have been consolidated or omitted.
Core CRUD/lifecycle coverage is strong for audiences, members, campaigns, templates, and files. Gaps exist for creating/updating automations and conversations (read-only), but the main email marketing workflows are well supported.