Mailchimp MCP Server
Related Servers
Alternatives to Mailchimp MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA server that integrates Mailchimp's email marketing platform with AI applications via the Model Context Protocol, enabling campaign, list, and automation management.-
- FlicenseDqualityDmaintenanceA comprehensive Model Context Protocol server that enables interaction with the Klaviyo API, providing tools and resources for managing customer profiles, lists, segments, campaigns, flows, and various marketing automation features.473-
- AlicenseNot gradedqualityCmaintenanceProvides a standardized interface for interacting with Mailchimp's tools and services through the Model Context Protocol, enabling easy management of Mailchimp campaigns, audiences, and reports via natural language commands.1MIT
- FlicenseNot gradedqualityDmaintenanceIntegrates Mailchimp with GenAI applications via the Model Context Protocol, enabling email marketing automation through natural language interactions.2-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for Marketing Connect AI integrations that provides tools, resources, and prompts for AI models to interact with marketing systems and data.-
- AlicenseAqualityAmaintenanceMailchimp MCP Server - Access Mailchimp data from Claude via MCP.100208 PyPI24MIT
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.