Skip to content

0.6.0

Choose a tag to compare

View all tags
@damientilman damientilman released this 09 Jun 16:30
v0.6.0
f592811
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v0.6.0 — Customer Journey workarounds and automation summary

This release addresses one of the most-asked questions in the Mailchimp dev
community: how to read or manage Customer Journeys via the API. The honest
answer is you can't directly — Mailchimp only exposes the journey-step trigger
endpoint publicly. This release adds three tools that wrap the practical
workarounds so you don't have to glue them together by hand.

The server now exposes 115 tools (up from 112).

Fully backwards-compatible — no existing tool signatures changed.

The Customer Journey API gap

Mailchimp has two automation products:

  • Classic Automations — the original workflows. Public API: /automations/*,
    full read + control (list, pause, start, inspect emails and queues).
  • Customer Journeys — the newer (2020+) drag-and-drop journey builder.
    Public API: only POST /customer-journeys/journeys/{journey_id}/steps/{step_id}/actions/trigger,
    which enrolls a contact into a step but doesn't let you read or manage the journey itself.

In the UI, Mailchimp pushes everyone toward Customer Journeys. In the API,
there's no way to list, inspect, or report on them. This release doesn't fix
Mailchimp's API — it ships the recommended workarounds as first-class tools.

Highlights

Search automation-emitted campaigns

Every email a Classic Automation or a Customer Journey sends creates a
campaign object with type='automation'. search_automation_campaigns filters
/campaigns to surface only those, with optional filters by audience, status,
and date range.

search_automation_campaigns(
    list_id="abc123",
    status="sent",
    since_send_time="2026-04-01T00:00:00Z",
)

You get every campaign emitted by your automation stack (Classic + journeys),
ready to drill into with the existing campaign / report tools.

Filter member activity for journey-related events

get_member_journey_events wraps a member's activity feed and filters
client-side to actions whose type contains "automation" or "journey".
Useful to answer "what automation/journey emails has this contact received?"
without scanning their full activity.

get_member_journey_events(
    list_id="abc123",
    email_address="jane@example.com",
    count=100,
)

Audit-ready automation summary

get_automation_summary combines two API calls into a single overview:
counts of Classic workflows by status, plus aggregate send volume from
automation-type campaigns in a configurable lookback window.

get_automation_summary(days=30)

Returns the kind of summary you'd want at the top of an account audit —
how many Classic workflows are running, how much of recent send volume came
from automations (Classic + journeys combined), and the top automation
campaigns by emails sent.

What's in this release

Added

  • search_automation_campaigns — filtered /campaigns?type=automation listing
  • get_member_journey_events — automation/journey-filtered member activity
  • get_automation_summary — combined Classic workflows + recent automation
    send volume overview
  • 4 new smoke tests covering filter wiring, server-side action filtering,
    and the multi-call aggregation

Changed

  • list_automations docstring corrected — it returns Classic Automations only,
    not Customer Journeys (Mailchimp does not expose a public read endpoint for
    journeys). Updated to point at the new workaround tools.
  • README's "Automations" section renamed to "Automations & Customer Journeys",
    expanded to document the journey coverage gap honestly with pointers to the
    workarounds.
  • Tool count bumped to 115 (was 112) across README.md, glama.json,
    and the pyproject.toml description.

Install

Recommended (no install):

uvx mailchimp-mcp

Via pip:

pip install --upgrade mailchimp-mcp

Configure your MCP client to launch uvx mailchimp-mcp with MAILCHIMP_API_KEY
in the environment. See the
README for the
full configuration block.

Safety modes

All new tools are read-only. Existing safety modes still apply to write tools:

  • MAILCHIMP_READ_ONLY=true — blocks all writes
  • MAILCHIMP_DRY_RUN=true — returns a preview of the action without calling
    the API

Feedback

Bug reports, feature requests, and PRs are welcome — see
CONTRIBUTING.md.

Full Changelog: v0.5.0...v0.6.0

Assets 2
Loading