Connect a module
Mailchimp
ShopMCP connects to Mailchimp's official Marketing API with OAuth, then exposes deep e-commerce retention tools under mailchimp_*.
OAuth-first
1. Configure OAuth
Register a Mailchimp app and set the redirect URI to https://my.shop-mcp.app/api/integrations/mailchimp/callback. Then configure the app environment.
bashMAILCHIMP_CLIENT_ID=... MAILCHIMP_CLIENT_SECRET=... MAILCHIMP_REDIRECT_URI=https://my.shop-mcp.app/api/integrations/mailchimp/callback
2. Connect
Open Settings - Integrations - Mailchimp and start the OAuth flow. ShopMCP stores the access token, server prefix, account metadata, and granted scopes encrypted at rest.
If OAuth is not configured yet, open the API-key fallback. Paste a Mailchimp Marketing API key that includes its data-center suffix, such as -us20. ShopMCP derives the server prefix, verifies the key against Mailchimp, and stores it encrypted.
3. What ShopMCP registers
- Audiences, members, member activity, tags, merge fields, interests, segments, abuse reports, and webhooks.
- Campaigns, content, send checklist, folders, templates, file manager, verified domains, and SMS campaign reads.
- Reports for campaigns, abuse, advice, opens, clicks, domains, e-commerce product activity, locations, sent-to, sub-reports, and unsubscribes.
- Classic automations plus the supported Customer Journey API trigger endpoint.
- E-commerce stores, customers, products, variants, images, carts, cart lines, orders, order lines, promo rules, and promo codes.
- Composite tools for retention command center, campaign postmortems, abandoned-cart readiness, product recommendations, promo code monitoring, customer timelines, and sync health.
4. Writes and sends
Writes are off by default. Enabling writes adds selected create/update tools plus campaign send, schedule, cancel, resend, and test actions. Destructive tools such as deleting stores, deleting campaigns, and permanently forgetting contacts are intentionally omitted from v1.

