v1.1.0
Reliability, robustness and distribution release. Minor bump, no breaking changes to tool signatures.
Fixed
- False success on writes — around 20 write/destructive tools (
send_campaign,send_test_email,schedule_campaign,cancel_send,delete_campaign,pause_automation, and thedelete_*family) discarded the API result and always reported success. A rejected send read assent, a failed delete asdeleted, a failed GDPR erase aspermanently_deleted. They now surface the real API error. - Malformed JSON in
batch_subscribe/create_segment/update_segment/create_batchreturns a readable error instead of raising. - Path parameters containing
..are rejected before dispatch. - Audit log redacts subscriber PII (
email_address,email,merge_fields) at any depth. tag_memberno longer claims "read scope required"; idempotency hints match their docstrings;delete_member/delete_member_permanentdocs corrected.
Added
- Automatic retries on 429/5xx with exponential backoff and
Retry-After(MAILCHIMP_MAX_RETRIES, default 3). Timeouts are not retried. - Connection pooling — one keep-alive session per account.
- Response size cap for campaign bodies (
MAILCHIMP_MAX_CONTENT_CHARS, default 100000) so a large template can't blow the context window. - Tool profiles —
MAILCHIMP_TOOLSexposes a subset (by risk tier or name) to shrink the tool-list payload. - Docker image on GHCR (
ghcr.io/damientilman/mailchimp-mcp-server) each release.
Changed
create_batchis now classifieddestructive(it can wrap arbitrary DELETEs);batch_subscribestayswrite.- Email addresses are validated before use;
batch_subscribeenforces the 500-member cap;offsetmust be non-negative. - Leaner tool descriptions trim the tool-list footprint by ~18%.
Install: `uvx mailchimp-mcp` or `docker run --rm -i -e MAILCHIMP_API_KEY=... ghcr.io/damientilman/mailchimp-mcp-server:latest`
Full changelog: https://github.com/damientilman/mailchimp-mcp-server/blob/main/CHANGELOG.md