Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider’s consent screen.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration. These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

​
Setup

  1. Register a Mailchimp app: Sign in to Mailchimp (the free plan works for testing) and go to Account → Extras → Registered apps (https://admin.mailchimp.com/account/oauth2/). Click Register An App.
  2. Set the redirect URI: Set the app’s Redirect URI to your app URL ending in /api/auth/mailchimp/callback.
  3. Copy credentials: Copy the Client ID and Client Secret into MAILCHIMP_CLIENT_ID and MAILCHIMP_CLIENT_SECRET.
  4. Find your data center and verify: Note the usXX prefix in your Mailchimp admin URL (e.g. us21.admin.mailchimp.com → us21). Connect your account and run List Audiences with that dc value.

​
Provider notes

  • Mailchimp access tokens do not expire and no refresh tokens are issued; reauthorize to rotate
  • The OAuth flow uses no scopes; the token grants the user’s account access
  • The API host is data-center-specific (usXX.api.mailchimp.com). The dc is NOT in the token response - Mailchimp returns it from GET https://login.mailchimp.com/oauth2/metadata. Tools therefore take dc as a required parameter (the usXX prefix in your admin URL); the tradeoff is the agent must supply it on every call
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as mailchimp__list_audiences with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.