The Mailchimp connector.
Audiences, campaigns and email reports. Connect once with your own key. Every agent your team runs reads the same 5 tools under one permission model.
How access is governed
5
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
Mailchimp exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
Mailchimp defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every Mailchimp tool
5 tools, named as the agent sees them.
- list_audiencesread
List the account's audiences (lists) with subscriber counts and engagement rates. Start here: the `id` returned for an audience is the `list_id` that list_audience_members and get_audience_growth require.
- list_audience_membersread
List members of one audience. Contains personal data, so this returns only the fields needed to identify and rate a subscriber and defaults to 10 members — narrow with `status` or `since_last_changed` instead of paging a whole audience. `list_id` comes from list_audiences.
- list_campaignsread
List campaigns, most recently sent first, with a headline performance summary. Use `status: "sent"` for what actually went out. The `id` returned here is the `campaign_id` that get_campaign_report takes.
- get_campaign_reportread
Get the full report for one sent campaign: opens, clicks, bounces, unsubscribes, and how it compares to the audience and industry averages. `campaign_id` comes from list_campaigns.
- get_audience_growthread
Get month-by-month growth history for one audience — subscribes, unsubscribes, imports, cleans. Use it to answer whether a list is actually growing. `list_id` comes from list_audiences.
Use it from any agent
The same Mailchimp tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a Mailchimp API Key in your Mailchimp account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect Mailchimp once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.