# Mailchimp for AI agents. Managed auth, ready-made tools.

> Manage audiences and contacts, build and send campaigns and read their reports in Mailchimp on behalf of each of your users.

- Page: https://www.agent200.com/tools/mailchimp/
- Category: Email and calendar
- Authentication: Managed OAuth
- Identifier in code: `mailchimp`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-15

## Instructions for AI agents

Connector: Mailchimp, through Agent200. In code: "mailchimp".
What it does: Manage audiences and contacts, build and send campaigns and read their reports in Mailchimp on behalf of each of your users.
Page: https://www.agent200.com/tools/mailchimp/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Mailchimp's own page, through the authorization link Agent200 returns. Never ask a user for a Mailchimp password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: mailchimp_list_audiences, mailchimp_search_members, mailchimp_get_report. Write tools: mailchimp_upsert_member, mailchimp_tag_member, mailchimp_create_campaign, mailchimp_set_campaign_content, mailchimp_send_campaign, mailchimp_schedule_campaign. Name "mailchimp" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/tools/mailchimp/framework/claude/
   https://www.agent200.com/tools/mailchimp/framework/chatgpt/
   https://www.agent200.com/tools/mailchimp/framework/claude-code/
   https://www.agent200.com/tools/mailchimp/framework/muse/
   https://www.agent200.com/tools/mailchimp/framework/grok-bot/
   https://www.agent200.com/tools/mailchimp/framework/openai-dots/
   https://www.agent200.com/tools/mailchimp/framework/claude-duet/
   https://www.agent200.com/tools/mailchimp/framework/hermes-agent/
   https://www.agent200.com/tools/mailchimp/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

## About

With the Mailchimp connector, your agent works in each user's own Mailchimp account. It can add and tag contacts, find a subscriber, build and send or schedule a campaign, and report how it did, using only the tools your project allows.

Mailchimp is Intuit's email marketing platform for audiences, campaigns and automations.

## Mailchimp tools

- **List audiences** (`mailchimp_list_audiences`, read): List the account's audiences.
- **Search contacts** (`mailchimp_search_members`, read): Find contacts by name or email.
- **Add or update a contact** (`mailchimp_upsert_member`, write): Add a contact to an audience or update their details.
- **Tag a contact** (`mailchimp_tag_member`, write): Add or remove tags on a contact.
- **Create a campaign** (`mailchimp_create_campaign`, write): Create a campaign for an audience or segment.
- **Set campaign content** (`mailchimp_set_campaign_content`, write): Set a campaign's HTML or template content.
- **Send a campaign** (`mailchimp_send_campaign`, write): Send a campaign now.
- **Schedule a campaign** (`mailchimp_schedule_campaign`, write): Schedule a campaign for a set time.
- **Get a campaign report** (`mailchimp_get_report`, read): Read a sent campaign's opens, clicks and bounces.

## Limits you can set

**Turn single tools on or off.** Let the agent build and schedule campaigns, and switch off `mailchimp_send_campaign` so nothing goes out at once.

**Restrict what the agent reaches.** Choose the endpoints and scopes a project may use, for example contacts and reports but not campaigns. A call outside them is refused.

## Get started

### Step 1: Set up the SDK

Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Let your user connect Mailchimp

Each end user authorizes their own Mailchimp account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

File `connect.js`:

```js
// Each end user authorizes their own Mailchimp account, once.
const connection = await agent200
  .user("user_123")
  .connect("mailchimp");

if (connection.authorizationUrl) {
  // Show this link to your user; Agent200 handles the rest.
  console.log(connection.authorizationUrl);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 3: Run with the Mailchimp tools

Name the user, the model and the tools. The model decides which Mailchimp tools to call, and Agent200 executes them with that user's connection.

File `run.js`:

```js
const result = await agent200
  .user("user_123")
  .run({
    model: "openai/gpt-5.6-sol",
    input: "How did last Tuesday's newsletter do?",
    tools: ["mailchimp"],
  });

console.log(result.output);
```

(Conceptual example of the Agent200 SDK.)

## Sign-in and permissions

**Who signs in.** Each of your users, once, on Mailchimp's own sign-in page. You never see or store their Mailchimp password.

**What access is requested.** Access to the Mailchimp account the user signs in to. Mailchimp's authorization covers the whole account, so the endpoints you allow in your project are what narrow it.

## Example requests

- "How did last Tuesday's newsletter do?"
- "Add these event attendees to the main audience and tag them Summit"
- "Draft a campaign announcing the spring sale and schedule it for Friday morning"

## Guides: Mailchimp with your AI framework

- [Mailchimp + Claude](https://www.agent200.com/tools/mailchimp/framework/claude.md): Connect Mailchimp to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Mailchimp + ChatGPT](https://www.agent200.com/tools/mailchimp/framework/chatgpt.md): ChatGPT cannot send an API key to a custom MCP server, so this guide builds Mailchimp into your own agent with OpenAI's models and the Agent200 SDK.
- [Mailchimp + Claude Code](https://www.agent200.com/tools/mailchimp/framework/claude-code.md): Have Claude Code build a Mailchimp agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [Mailchimp + Muse](https://www.agent200.com/tools/mailchimp/framework/muse.md): Connect Mailchimp to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Mailchimp + Grok Bot](https://www.agent200.com/tools/mailchimp/framework/grok-bot.md): Connect Mailchimp to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Mailchimp + OpenAI Dots](https://www.agent200.com/tools/mailchimp/framework/openai-dots.md): Dots cannot send an API key to a custom MCP server, so this guide builds an always-on Mailchimp agent with OpenAI's models and the Agent200 SDK.
- [Mailchimp + Claude Duet](https://www.agent200.com/tools/mailchimp/framework/claude-duet.md): Connect Mailchimp to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Mailchimp + Hermes Agent](https://www.agent200.com/tools/mailchimp/framework/hermes-agent.md): Connect Mailchimp to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Mailchimp + OpenClaw](https://www.agent200.com/tools/mailchimp/framework/openclaw.md): Connect Mailchimp to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### Who handles the Mailchimp OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Mailchimp.

### Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Mailchimp connection, never another user's. It cannot reach anything the user or Mailchimp has not authorized.

### Can I limit what my agent can do in Mailchimp?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

## Related connectors

- [Gmail](https://www.agent200.com/tools/gmail.md): Read, search, draft and send email from each user's own Gmail account.
- [Outlook](https://www.agent200.com/tools/outlook.md): Work with mail and calendar in each user's Microsoft Outlook account.
- [Google Calendar](https://www.agent200.com/tools/google-calendar.md): Check availability and create, update or cancel events in your users' calendars.
- [Calendly](https://www.agent200.com/tools/calendly.md): Find open times, share booking links, and book, review or cancel meetings in Calendly on behalf of each of your users.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
