Mailchimp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAILCHIMP_API_KEY | Yes | Your Mailchimp API key including the data center suffix (e.g., xxxxxxxxxxxxxxxx-us1) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_automationsB | List all automations in your Mailchimp account |
| get_automationB | Get details of a specific automation by workflow ID |
| list_automation_emailsC | List all emails in an automation |
| get_automation_emailC | Get details of a specific email in an automation |
| list_automation_subscribersC | List subscribers in an automation email queue |
| get_automation_queueC | Get the automation email queue |
| list_listsB | List all lists in your Mailchimp account (for automation recipients) |
| get_listC | Get details of a specific list |
| get_automation_reportC | Get automation report data |
| get_automation_email_reportC | Get automation email report data |
| get_subscriber_activityC | Get subscriber activity for an automation email |
| list_campaignsB | List all campaigns in your Mailchimp account |
| get_campaignC | Get details of a specific campaign |
| list_membersC | List all members in a specific list |
| get_memberC | Get details of a specific member |
| list_segmentsC | List all segments in a specific list |
| get_segmentC | Get details of a specific segment |
| list_templatesB | List all templates in your Mailchimp account |
| get_templateC | Get details of a specific template |
| list_campaign_reportsC | List all campaign reports |
| get_campaign_reportC | Get detailed report for a specific campaign |
| get_accountC | Get account information |
| list_foldersB | List all campaign folders |
| get_folderC | Get details of a specific folder |
| list_merge_fieldsC | List all merge fields in a specific list |
| get_merge_fieldB | Get details of a specific merge field |
| list_filesB | List all files in the File Manager |
| get_fileC | Get details of a specific file |
| list_landing_pagesB | List all landing pages |
| get_landing_pageC | Get details of a specific landing page |
| list_storesB | List all e-commerce stores |
| get_storeC | Get details of a specific store |
| list_productsC | List all products in a store |
| get_productC | Get details of a specific product |
| list_ordersC | List all orders in a store |
| get_orderC | Get details of a specific order |
| list_conversationsB | List all conversations |
| get_conversationC | Get details of a specific conversation |
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 38 tools
Every tool has a clearly distinct purpose targeting specific resources and actions. The naming convention makes it immediately clear whether a tool retrieves a single item (get_*) or lists multiple items (list_*), with no ambiguity between similar operations.
The naming follows a perfect and predictable pattern throughout: all tools use snake_case with consistent verb_noun combinations (get_resource for single items, list_resources for collections). There are no deviations or mixed conventions.
With 38 tools, this is too many for typical MCP server purposes. While Mailchimp has many resources, the tool surface feels heavy and could overwhelm agents. A more focused subset would likely be more manageable and appropriate.
The surface provides extensive read-only coverage (get and list operations) but lacks create, update, or delete operations for most resources. While agents can retrieve data, they cannot modify Mailchimp resources, creating significant workflow gaps.