@m6b9/mcp-mailchimp
Related Servers
Alternatives to @m6b9/mcp-mailchimp
No user-submitted related servers found.
Related Servers
- FlicenseCqualityDmaintenanceComprehensive MCP server for Mailchimp Marketing API v3.0 with over 104 tools and 15+ React UI apps, enabling management of campaigns, audiences, ecommerce, automations, reports, and more via natural language.1001-
- AlicenseBqualityCmaintenanceA production-grade MCP server that integrates with the Mailchimp Marketing API to manage campaigns, audiences, members, and reports. It provides 28 specialized tools for automating marketing tasks such as sending emails, managing subscriber tags, and analyzing performance data.711MIT
- AlicenseAqualityDmaintenanceA hybrid Mailchimp MCP server with 12 tools: 10 native tools for common email workflows plus search and execute to access all 282 Mailchimp Marketing API endpoints on demand.1216 npmMIT
- FlicenseNot gradedqualityDmaintenanceComprehensive MCP server for the Mautic marketing automation API, providing 203 tools for managing contacts, campaigns, emails, segments, and more.2-
- AlicenseNot gradedqualityCmaintenanceMCP server for full Mailchimp management: audiences, tags, segments, campaigns, templates and reporting. Enables creating, sending, scheduling campaigns, managing contacts, and retrieving reports via natural language.MIT
- AlicenseAqualityDmaintenanceAn MCP server that interfaces with the Mailchimp Marketing API to manage audiences, email campaigns, and subscribers. It enables users to create and schedule campaigns, handle member lists, and send test or live emails through natural language commands.1316 npmMIT
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.