Skip to main content
Glama
Mailchimp MCP Server

Mailchimp MCP Server

by aakarsh1t

Mailchimp MCP Server

npm version

Watch the Notion Tutorial video Website

A Model Context Protocol (MCP) server exposing read-only access to the Mailchimp Marketing API v3 through 18 tools covering 103 endpoints — audiences, members, campaigns, reports, automations, templates, landing pages, e-commerce, and account administration.

Tools are grouped by domain and dispatch on an action parameter, so the full API surface stays reachable while the tool count stays low enough for hosts that cap actions per agent (Microsoft Copilot Studio among them).

Every tool issues a GET. The server has no code path that can create, modify, or delete anything in your Mailchimp account, or send email.

Usage

{
  "mcpServers": {
    "mailchimp": {
      "command": "npx",
      "args": ["@agentx-ai/mailchimp-mcp-server"],
      "env": {
        "MAILCHIMP_API_KEY": "your-api-key-here"
      }
    }
  }
}

Related MCP server: Mailchimp MCP Server

Local installation

npm install     # installs deps and builds
npm run dev     # build + open the MCP Inspector

Other scripts: npm run build (compile), npm start (raw stdio server), npm run watch (recompile on change), npm run inspector (Inspector against the existing build).

Configuration

MAILCHIMP_API_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-us14

A .env file in the project root is read automatically. The key must keep its data-center suffix (-us1, -us14, …) — it determines the API hostname. The server refuses to start without a valid suffix rather than failing later with an opaque DNS error.

Transports

Both transports serve the identical tool surface from one server definition (src/server.ts), so they cannot drift apart.

stdio (default) — for Claude Desktop, Cursor, the MCP Inspector, and any local client:

npm start

Streamable HTTP — for network-based hosts such as Microsoft Copilot Studio:

npm run start:http          # or: node build/index.js --http

HTTP mode also activates automatically when PORT is set, which is how Azure App Service, Container Apps, and most PaaS hosts signal that they expect a listener.

Variable

Default

Purpose

MAILCHIMP_API_KEY

—

Required. Must keep its data-center suffix.

PORT

3000

HTTP port. Setting it enables HTTP mode.

HOST

0.0.0.0

Bind address.

MCP_PATH

/mcp

Endpoint path.

MCP_AUTH_TOKEN

—

When set, /mcp requires Authorization: Bearer <token>.

MCP_TRANSPORT

stdio

Set to http to force HTTP mode.

GET /health returns server name, version, endpoint path, and whether auth is required — use it as your platform's health probe.

Set MCP_AUTH_TOKEN before exposing this server publicly. The endpoint grants read access to your entire Mailchimp account, and there is no other access control in front of it. The server logs a warning at startup when the token is unset. Compare is constant-time, so the token is not vulnerable to timing analysis.

Sessions are stateless: each request gets its own server and transport instance, so the process scales horizontally with no shared session store.

Microsoft Copilot Studio

  1. Deploy this server somewhere with a public HTTPS URL (Azure Container Apps, App Service, or any container host). Set MAILCHIMP_API_KEY and MCP_AUTH_TOKEN in its environment.

  2. Confirm https://<your-host>/health returns {"status":"ok"}.

  3. In Copilot Studio, add a new tool → Model Context Protocol, pointing at https://<your-host>/mcp.

  4. Configure authentication as a bearer token and supply the same value as MCP_AUTH_TOKEN.

  5. All 18 tools appear as agent actions. The tool count is deliberately kept low because Copilot Studio limits actions per agent — the action parameter is what preserves access to all 103 endpoints.

Tool catalog

Tool

Actions

Covers

mailchimp_account

11

ping, account overview, authorized apps, verified domains, batches, connected sites, chimp chatter

mailchimp_search

2

members, campaigns

mailchimp_audiences

12

lists, growth history, activity, client stats, location stats, abuse reports, signup forms, webhooks, merge fields

mailchimp_audience_groups

7

segments, segment members, interest categories, interests

mailchimp_members

9

members, tags, activity, activity feed, events, notes, goals

mailchimp_campaigns

5

campaigns, content, feedback, send checklist

mailchimp_reports

16

summary, advice, opens, clicks, link clickers, unsubscribes, abuse, sent-to, domain performance, locations, eepurl, sub-reports, email activity, product activity

mailchimp_automations

7

workflows, emails, queues, removed subscribers

mailchimp_templates

3

templates, default content

mailchimp_files

6

File Manager files and folders, campaign folders

mailchimp_landing_pages

3

pages, content

mailchimp_conversations

3

conversations, messages

mailchimp_stores

3

stores, account-wide orders

mailchimp_products

4

products, variants

mailchimp_orders

3

orders, line items

mailchimp_customers

2

customers

mailchimp_carts

3

carts, line items

mailchimp_promos

4

promo rules, promo codes

Each tool's description lists its actions and what each one needs. Run npm run dev and open the Inspector's Tools tab to see the full schemas.

Conventions

Every tool follows the same shape, so the catalog above is enough to predict any call:

  • action is always required and selects the data to retrieve. An invalid action returns an error listing the valid ones.

  • List-style actions return a summary envelope — { total_items, returned, items: [...] } — where each item is trimmed to identifying fields. This keeps a 1000-row page from flooding the model's context, while total_items tells the caller whether more rows exist.

  • Detail-style actions (details, summary, single-record lookups) return the complete raw Mailchimp record, unmodified.

  • Paging: collection tools accept count (1–1000, default 1000) and offset. To read an audience larger than 1000, call repeatedly with offset 0, 1000, 2000, … until returned is less than count.

  • IDs: start at mailchimp_audiences action=list, mailchimp_campaigns action=list, or mailchimp_stores action=list. mailchimp_search action=members is the fastest route to a subscriber_hash.

  • Missing arguments are rejected before any HTTP request, with a message naming exactly which ones the chosen action needs.

Development

npm run build      # tsc
npm run watch      # tsc --watch
npm run inspector  # MCP Inspector against build/index.js

There is no test suite in this repository.

Known gaps

  • Customer journeys are not readable. Mailchimp does not expose them via the Marketing API; the automation tools cover classic automations only.

  • Endpoint coverage is based on the documented Marketing API v3 surface and has not been exercised against a live account for all 103 actions. The transport, dispatch, and validation layers are verified; individual endpoint URLs are not.

  • No deployment manifests. There is no Dockerfile or IaC in this repo; hosting is left to you.

API reference

https://mailchimp.com/developer/marketing/api/

License

MIT.

Available Tools

18 tools
mailchimp_accountA

Account-level administration: plan and contact details, API health, app authorizations, verified sending domains, batch jobs, connected sites, and the account activity feed. Set action to one of: ping (verify the API key works); overview (plan, contact, total subscribers, industry benchmarks); authorized_apps (apps with access to this account); authorized_app (one app, needs app_id); verified_domains (sending domains and their verification state); verified_domain (one domain, needs domain_name); batches (batch API jobs and status); batch (one batch job, needs batch_id); connected_sites (websites connected to the account); connected_site (one site, needs site_id); chimp_chatter (recent account-wide activity feed).

Inputs: action (required), count, app_id, offset, +3 more.

mailchimp_audience_groupsA

Segments, tags, and interest groups within one audience, including which members belong to a segment. Set action to one of: segments (all segments and tags with member counts); segment (one segment with its matching conditions, needs segment_id); segment_members (members inside a segment or tag, needs segment_id); interest_categories (group titles defined on the audience); interest_category (one category, needs category_id); interests (groups inside a category, needs category_id); interest (one group, needs category_id and interest_id).

Inputs: action (required), list_id (required), count, offset, +3 more.

mailchimp_audiencesA

Audiences (lists) and their configuration and health: growth history, daily activity, email client and geographic breakdowns, spam complaints, signup forms, webhooks, and merge fields. Set action to one of: list (all audiences with member counts — start here for a list_id); details (full audience record with complete stats); growth_history (month-by-month subscriber growth); activity (recent daily subs, unsubs, opens, clicks); client_stats (which email clients members use); location_stats (geographic distribution of members); abuse_reports (spam complaints against this audience); signup_forms (configured signup forms); webhooks (registered webhooks); webhook (one webhook, needs webhook_id); merge_fields (custom subscriber attributes defined on the audience); merge_field (one merge field, needs merge_field_id).

Inputs: action (required), count, offset, list_id, +2 more.

mailchimp_automationsA

Classic automations, their emails, and subscriber queues. Customer journeys are not exposed by the Mailchimp API. Set action to one of: list (all automations — start here for a workflow_id); details (full automation record including its report_summary); emails (emails in the automation, in send order); email (one automation email, needs email_id); queue (subscribers queued for an email, needs email_id); queue_subscriber (one queued subscriber, needs email_id and subscriber_hash); removed_subscribers (subscribers removed from the workflow).

Inputs: action (required), count, offset, email_id, +2 more.

mailchimp_campaignsA

Campaigns and their configuration and content. For performance data use mailchimp_reports instead. Set action to one of: list (all campaigns newest-first — start here for a campaign_id); details (full campaign record with settings and recipients); content (rendered HTML and plain-text body); feedback (internal team comments); send_checklist (what is blocking the campaign from sending).

Inputs: action (required), count, offset, campaign_id.

mailchimp_cartsA

Abandoned and active shopping carts for one store, for abandoned-cart analysis. Set action to one of: list (carts in the store); details (full cart record, needs cart_id); lines (line items in the cart, needs cart_id).

Inputs: action (required), store_id (required), count, offset, +1 more.

mailchimp_conversationsA

Inbound replies from subscribers, tracked as conversations. Set action to one of: list (all conversations); details (full conversation record); messages (all messages in the conversation).

Inputs: action (required), count, offset, conversation_id.

mailchimp_customersA

E-commerce customers for one store, with order counts and lifetime spend. Set action to one of: list (customers with orders_count and total_spent); details (full customer record, needs customer_id).

Inputs: action (required), store_id (required), count, offset, +1 more.

mailchimp_filesB

File Manager assets and folders, plus campaign folders used to organize campaigns. Set action to one of: files (files stored in the File Manager); file (one file, needs file_id); folders (File Manager folders); folder (one File Manager folder, needs folder_id); campaign_folders (folders that organize campaigns); campaign_folder (one campaign folder, needs folder_id).

Inputs: action (required), count, offset, file_id, +1 more.

mailchimp_landing_pagesA

Landing pages and their published content. Set action to one of: list (all landing pages with status and URL); details (full landing page record); content (rendered HTML of the page).

Inputs: action (required), count, offset, page_id.

mailchimp_membersA

Subscribers in one audience and everything recorded about them: profile, tags, engagement history, custom events, staff notes, and goal events. Set action to one of: list (members newest-first; page with count and offset); details (full profile: merge fields, interests, stats, location, tags); tags (tags applied to the member); activity (last 50 campaign actions); activity_feed (complete paged activity history across channels); events (custom events recorded against the member); notes (staff notes on the member); note (one note, needs note_id); goals (site-activity goal events).

Inputs: action (required), list_id (required), count, offset, +2 more.

mailchimp_ordersA

Orders and line items for one store, including the campaign each order is attributed to. Set action to one of: list (orders in the store with totals and attribution); details (full order record with line items, needs order_id); lines (line items only, needs order_id).

Inputs: action (required), store_id (required), count, offset, +1 more.

mailchimp_productsA

Product catalog and variants for one e-commerce store. Set action to one of: list (products in the store); details (full product record with all variants, needs product_id); variants (variants of one product, needs product_id); variant (one variant, needs product_id and variant_id).

Inputs: action (required), store_id (required), count, offset, +2 more.

mailchimp_promosA

Promotion rules and their promo codes for one store. Set action to one of: rules (promotion rules in the store); rule (one rule, needs promo_rule_id); codes (codes under a rule, needs promo_rule_id); code (one code, needs promo_rule_id and promo_code_id).

Inputs: action (required), store_id (required), count, offset, +2 more.

mailchimp_reportsA

Campaign performance analytics: opens, clicks, unsubscribes, bounces, deliverability by domain, geography, per-member activity, and attributed revenue. Set action to one of: list (performance summary for every sent campaign); summary (full report for one campaign: opens, clicks, bounces, forwards, revenue, benchmarks); advice (Mailchimp's automated performance advice); opens (which members opened, and how often); clicks (per-link click totals); link_clickers (who clicked one link, needs link_id); unsubscribes (who unsubscribed and why); abuse_reports (spam complaints against the campaign); sent_to (every recipient with per-member open and click counts); domain_performance (deliverability broken down by recipient domain); locations (where opens came from geographically); eepurl (social sharing and archive-page stats); sub_reports (child reports for an A/B or multivariate campaign); email_activity (per-member action log with timestamps); subscriber_activity (one member's action log, needs subscriber_hash); product_activity (revenue and products attributed to the campaign).

Inputs: action (required), count, offset, link_id, +2 more.

mailchimp_storesA

Connected e-commerce stores, and orders across every store. Start here for a store_id. Set action to one of: list (all connected stores); details (full store record, needs store_id); all_orders (orders across every store on the account).

Inputs: action (required), count, offset, store_id.

mailchimp_templatesC

Email templates available on the account. Set action to one of: list (all templates); details (full template record); default_content (the template's default section content).

Inputs: action (required), count, offset, template_id.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct Mailchimp resource (audiences, members, campaigns, reports, stores, etc.), and the action parameter further disambiguates within each resource. Despite minor overlaps like abuse_reports in both audiences and reports, the descriptions clearly differentiate audience-level vs campaign-level data.

    Naming Consistency5/5

    All tools follow the consistent pattern mailchimp_<resource> using snake_case and plural nouns. The action parameter uses lowercase verbs and nouns consistently, creating a predictable and uniform naming scheme throughout the server.

    Tool Count4/5

    With 18 tools, the count is slightly above the typical 3-15 range but still well-scoped given the breadth of Mailchimp's API. Each tool represents a major domain, and the grouping keeps the surface manageable without unnecessary fragmentation.

    Completeness2/5

    The tool set is heavily read-oriented, offering list and details operations but lacking any create, update, or delete actions for any resource. There are no tools to send campaigns, manage subscribers, or modify store data, which is a significant gap for a Mailchimp server.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol server that provides read-only access to Mailchimp's Marketing API for comprehensive email marketing data retrieval.
      38
      166 npm
      13
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A 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.
      71
      1
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      MCP server for Mailchimp Marketing API v3 with 72 tools covering audiences, campaigns, templates, reports, and more.
      72
      -
    • A
      license
      C
      quality
      D
      maintenance
      Comprehensive 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.
      100
      1
      MIT