Mailchimp

v1.0.02 callsOAuthGitHub

Documentation

Guide

Run your Mailchimp marketing operations through AI.

A Model Context Protocol (MCP) server that exposes Mailchimp's Marketing API for reading and managing automations, audiences, campaigns, templates, landing pages, and e-commerce data.

Overview

The MewCP Mailchimp MCP Server provides authenticated access to the Mailchimp Marketing API:

Inspect classic automation workflows, their individual emails, and the subscribers queued in each email's send queue
List and read audiences (lists) and campaigns, including full campaign performance reports
Manage Classic templates and folders, and inspect landing pages and their published HTML content
Query connected e-commerce stores, products, and orders — including orders attributed to a specific campaign

Perfect for:

AI assistants that need to read or manage Mailchimp marketing data
Automating campaign and automation performance reporting
Building tools that connect Mailchimp audience, campaign, and e-commerce data to other systems

Tools

Automations

Get a summary of an account's classic automations with optional filtering and pagination

Inputs:

- `count` (int, optional, default: 10) — Number of records to return (max: 1000)
- `offset` (int, optional, default: 0) — Number of records to skip for pagination
- `fields` (string, optional, default: null) — Comma-separated list of fields to return
- `exclude_fields` (string, optional, default: null) — Comma-separated list of fields to exclude
- `before_create_time` (string, optional, default: null) — Restrict to automations created before this time (ISO 8601: 2015-10-21T15:41:36+00:00)
- `since_create_time` (string, optional, default: null) — Restrict to automations created after this time (ISO 8601: 2015-10-21T15:41:36+00:00)
- `before_start_time` (string, optional, default: null) — Restrict to automations started before this time (ISO 8601: 2015-10-21T15:41:36+00:00)
- `since_start_time` (string, optional, default: null) — Restrict to automations started after this time (ISO 8601: 2015-10-21T15:41:36+00:00)
- `status` (string, optional, default: null) — Filter by status: 'save', 'paused', or 'sending'

output data schema:

{
  automations: {
    id: string | null;
    create_time: string | null;
    start_time: string | null;
    status: string | null;
    emails_sent: number | null;
    recipients: {
      list_id: string | null;
      store_id

Get detailed information about a specific automation workflow by ID

Inputs:

- `workflow_id` (string, required) — The unique ID of the Automation workflow
- `fields` (string, optional, default: null) — Comma-separated list of fields to return
- `exclude_fields` (string, optional, default: null) — Comma-separated list of fields to exclude

output data schema:

{
  id: string | null

Get a summary of the emails in a classic automation workflow

Inputs:

- `workflow_id` (string, required) — The unique ID of the Automation workflow

output data schema:

{
  emails: {
    id: string | null;
    workflow_id: string | null;
    position: number |

Get detailed information about a specific email in an automation workflow

Inputs:

- `workflow_id` (string, required) — The unique ID of the Automation workflow
- `workflow_email_id` (string, required) — The unique ID of the Automation workflow email

output data schema:

{
  id: string | null;
  workflow_id: string | null;
  position

Get information about subscribers queued to receive a specific automation email

Inputs:

- `workflow_id` (string, required) — The unique ID of the Automation workflow
- `workflow_email_id` (string, required) — The unique ID of the Automation workflow email

output data schema:

{
  queue: {
    id: string | null;
    workflow_id: string | null

Get detailed information about a specific subscriber to an automation email queue

Inputs:

- `workflow_id` (string, required) — The unique ID of the Automation workflow
- `workflow_email_id` (string, required) — The unique ID of the Automation workflow email
- `subscriber_hash` (string, required) — The MD5 hash of the lowercase version of the subscriber's email address

output data schema:

{
  id: string | null;

Audiences

Get detailed information about a specific list (audience) in your Mailchimp account

Inputs:

- `list_id` (string, required) — The unique ID for the list

output data schema:

{
  id: string | null;
  web_id: number | null;
  name: string | null;
  date_created

Campaigns

Get detailed information about a specific campaign

Inputs:

- `campaign_id` (string, required) — The unique ID for the campaign

output data schema:

{
  id: string | null;
  web_id: number | null;
  type: string | null;
  create_time

Get all campaign reports with performance metrics

Inputs:

- `count` (int, optional, default: 10) — Number of reports to return (max: 1000)
- `offset` (int, optional, default: 0) — Number of records to skip for pagination
- `type` (string, optional, default: null) — Filter by campaign type: 'regular', 'plaintext', 'absplit', 'rss', or 'variate'

output data schema:

{
  reports

Get detailed report for a specific sent campaign

Inputs:

- `campaign_id` (string, required) — The unique ID for the campaign

output data schema:

{
  id: string | null;
  campaign_title: string | null;
  type: string | null;
  list_id

Landing Pages

Get all landing pages in your account

Inputs:

- `count` (int, optional, default: 10) — Number of landing pages to return (max: 1000)
- `sort_field` (string, optional, default: null) — Sort by: 'created_at' or 'updated_at'
- `sort_dir` (string, optional, default: null) — Sort direction: 'ASC' or 'DESC'

output data schema:

{
  landing_pages: {

Get detailed information about a specific landing page by ID

Inputs:

- `page_id` (string, required) — The unique ID for the landing page

output data schema:

{
  id: string | null;
  name: string | null;
  title: string | null;
  status

Templates

Get all folders used to organize templates

Inputs:

- `count` (int, optional, default: 10) — Number of folders to return (max: 1000)
- `offset` (int, optional, default: 0) — Number of records to skip for pagination

output data schema:

{
  folders: {
    id: string | null;

Get all templates in your account

Inputs:

- `count` (int, optional, default: 10) — Number of templates to return (max: 1000)
- `offset` (int, optional, default: 0) — Number of records to skip for pagination
- `type` (string, optional, default: null) — Filter by type: 'user', 'base', or 'gallery'
- `content_type` (string, optional, default: null) — Filter by content type: 'html', 'template', or 'multichannel'

output data schema:

Get detailed information about a specific template by ID

Inputs:

- `template_id` (string, required) — The unique ID for the template

output data schema:

{
  id: number | null;
  type: string | null;
  name: string | null;
  date_created

Create a new Classic template for the account. It supports Mailchimp Template Language

Inputs:

- `name` (string, required) — The name of the template
- `html` (string, required) — The raw HTML for the template. Supports Mailchimp Template Language
- `folder_id` (string, optional, default: null) — The ID of the folder to place the template in

output data schema:

{
  id: number | null;
  type: string

Updates the name, HTML, or folder of an existing Classic template. This overwrites the current name and HTML with the values you provide (folder_id is only changed if given) — the original state is not stored by the API after the call. The response includes both the before and after state so you have a full record of what changed.

Inputs:

- `template_id` (string, required) — The unique ID for the template
- `name` (string, required) — The name of the template
- `html` (string, required) — The raw HTML for the template. Supports Mailchimp Template Language
- `folder_id` (string, optional, default: null) — The ID of the folder to move the template to

output data schema:

E-commerce

Get information about all e-commerce stores in the account

Inputs:

- `count` (int, optional, default: 10) — Number of stores to return (max: 1000)
- `offset` (int, optional, default: 0) — Number of records to skip for pagination

output data schema:

{
  stores: {
    id: string | null;

Get detailed information about a specific e-commerce store

Inputs:

- `store_id` (string, required) — The unique ID for the store

output data schema:

{
  id: string | null;
  list_id: string | null;
  name: string | null;
  platform

Get information about all products in a specific e-commerce store

Inputs:

- `store_id` (string, required) — The unique ID for the store
- `count` (int, optional, default: 10) — Number of products to return (max: 1000)
- `offset` (int, optional, default: 0) — Number of records to skip for pagination

output data schema:

{
  products: {
    id: string

Get detailed information about a specific product in an e-commerce store

Inputs:

- `store_id` (string, required) — The unique ID for the store
- `product_id` (string, required) — The unique ID for the product

output data schema:

{
  id: string | null;
  title: string | null;
  handle: string |

Get information about all orders in a specific e-commerce store

Inputs:

- `store_id` (string, required) — The unique ID for the store
- `count` (int, optional, default: 10) — Number of orders to return (max: 1000)
- `offset` (int, optional, default: 0) — Number of records to skip for pagination
- `customer_id` (string, optional, default: null) — Restrict results to orders made by a specific customer
- `campaign_id` (string, optional, default: null) — Restrict results to orders with a specific campaign ID

output data schema:

Get detailed information about a specific order in an e-commerce store

Inputs:

- `store_id` (string, required) — The unique ID for the store
- `order_id` (string, required) — The unique ID for the order

output data schema:

{
  id: string | null;
  customer: {
    id: string | null;
    email_address

System

API Parameters Reference

Every tool returns the same top-level envelope. Only data varies per tool.

// Success
{
  "success": true,
  "statusCode": 200,
  "retriable": false,
  "retry_after_seconds": null,
  "error": null,
  "data": { ... }
}
 
// Error

list_automations and get_automation_info support field filtering to shrink the response payload.

fields — Comma-separated list of response fields to include
exclude_fields — Comma-separated list of response fields to omit

Example:

fields: "automations.id,automations.status"
exclude_fields: "_links"

The subscriber_hash parameter used by get_automated_email_subscriber is the MD5 hash of the subscriber's lowercase email address.

input: user@example.com → lowercase → user@example.com
Hash: md5("user@example.com") → b58996c504c5638798eb6b511e6f49af

Troubleshooting

Cause: OAuth token not provided in request headers, or the linked credential is missing its server_prefix extra
Solution:
1. Verify Authorization: Bearer YOUR_TOKEN and X-Mewcp-Credential-Id: CREDENTIAL-ID headers are present
2. Check that the credential's extras include a valid server_prefix matching your Mailchimp account's data center
3. Check the OAuth token has not expired — reconnect in your MewCP account if needed

Help Improve This Server

Missing a tool?

Found a bug?

Have an idea for an improvement?

Share your feedback directly with the maintainers - every feedback helps make this server better for everyone.

Open GitHub Issues →