Mailchimp via MCP: draft, test, and send campaigns; manage audiences and subscribers; pull reports.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-cyanheads-mailchimp-mcp-server": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Mailchimp via MCP: draft, test, and send campaigns; manage audiences and subscribers; pull reports.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in marketing
DataForSEO API modelcontextprotocol server
Search the Entra.news newsletter archive — a weekly digest of Microsoft Entra news
SFMC AMPscript/SSJS/GTL tools and searchable Marketing Cloud Engagement help (MCE vs Next scoped) via MCP.
Crawl and analyse websites for SEO errors using Crawlee with SQLite storage
MCP Security Weekly
Get CVE alerts and security updates for io.github.cyanheads/mailchimp-mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Draft, test, and send Mailchimp campaigns straight from your MCP client — with audience management, subscriber CRUD, and post-send analytics behind safe-by-default send gates. STDIO or Streamable HTTP.
Seventeen tools grouped by shape — workflow helpers orchestrate common flows end-to-end, primitive tools expose fine-grained CRUD, and the instruction tool returns procedural guidance merged with live account state.
| Tool Name | Description |
|---|---|
mailchimp_account | Account profile, plan, data center, total subscribers, and the Chimp Chatter activity feed. |
mailchimp_audiences | Manage audiences (lists) — read, create/update, per-audience analytics, signup-form config. No delete. |
mailchimp_audience_overview | One-call audience health digest: info, stats, growth history, top email clients, merge-field schema. |
mailchimp_subscribers | Subscriber CRUD + tags/notes/activity. archive is the strongest delete available. |
mailchimp_upsert_subscriber | Add or update a subscriber idempotently with status, merge fields, tags, and optional note. |
mailchimp_find_subscriber | Locate a subscriber by email in one audience or across the account. |
mailchimp_import_subscribers | Batch add/update subscribers (capped at 500/call). Status defaults to pending (double-opt-in). |
mailchimp_segments | CRUD for audience segments (saved, static, fuzzy) plus member listing and batch add/remove. |
mailchimp_merge_fields | Read + create/update custom subscriber attributes. No delete — drops data across all subscribers. |
mailchimp_campaigns | Campaign record management: list/get/create/update, replicate, content, checklist, RSS/resend controls. |
mailchimp_send_campaign | Compose and send (or schedule/test) a campaign in one call. Elicits human confirmation on send/schedule. |
mailchimp_replicate_campaign | Duplicate a campaign with optional overrides, then draft/test/send/schedule. Same elicit + cleanup semantics. |
mailchimp_reports | Campaign reports — generic slicer across ten dimensions (clicks, opens, locations, etc.). |
mailchimp_campaign_report | Post-send analytics digest — headline metrics + top 5 slices in one response. |
mailchimp_templates | Email template CRUD (base, user; gallery requires a paid plan). |
mailchimp_search | Global search across members or campaigns. Lightweight discovery — use find_subscriber for detail. |
mailchimp_playbook | Returns a structured procedural playbook merged with live account state. Advice-only, no writes. |
mailchimp_send_campaignCompose and send (or schedule/test) a campaign in one call.
ctx.elicit when mode: 'send' | 'schedule' and the client supports elicitationcleanupOnError: true