# Iterable MCP connector

The Iterable connector brings campaigns, catalogs, catalog items and cart updates into Claude, ChatGPT, Cursor and Microsoft Copilot through one governed endpoint, so each person works in Iterable as themselves with every action logged.

Source: https://elaichi.ai/connectors/iterable/

## Facts

| | |
| --- | --- |
| Application | Iterable |
| Category | Marketing Automation |
| AI tools | 157 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Iterable is connected

- Show me metrics for last week's welcome campaign
- Schedule the spring sale campaign for Monday at 9am
- Which catalog items are missing a price?

## Connect Iterable in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Iterable.
2. Optionally set Share with, then press Connect.
3. Paste an Iterable API key. One person generates a token in Iterable and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Iterable tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Iterable MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Iterable MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Iterable MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Iterable MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Iterable MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Iterable to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Iterable tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Iterable through Elaichi

### Check how yesterday's send performed

Marketing. Ask for the metrics on the campaign that went out yesterday and get the numbers in the chat, without opening a report in Iterable.

### Schedule the welcome campaign for Monday

Lifecycle. Set a send time on a campaign that is ready to go, or trigger it right now for a specific audience.

### Keep the product catalog current

Merchandising. Add new products to an Iterable catalog in bulk, fix a price or description on one item, and remove items that are discontinued.

### Pull the plug on a campaign mid-send

Marketing ops. Abort a send that went out with the wrong offer, cancel a campaign that is scheduled for later, or archive campaigns that are finished.

### Record a cart update for a shopper

Ecommerce. Log what a customer added or removed from their cart so abandoned cart campaigns in Iterable fire with the right items.

### Map catalog fields before a launch

Growth. Review how fields are mapped in a catalog and update several mappings at once so new product data lands in the right place.

## Elaichi vs Zapier MCP vs Composio for Iterable

All three can connect Iterable to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Iterable tools | Allow or restrict single Iterable tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Iterable call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Iterable to Claude?

Connect Iterable in Elaichi by pasting an API key from your Iterable account, then paste the endpoint https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add. There is no OAuth application to register in Iterable and no client ID or secret to generate. Once added, Claude signs you in to Elaichi and your Iterable campaigns and catalogs are ready to work with.

### Does Iterable work with ChatGPT and Cursor as well as Claude?

Yes. An Iterable connection in Elaichi is exposed on one endpoint, https://api.elaichi.ai/mcp, and Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent all connect to that same address. Connect Iterable once and every client you use sees it.

### What can an AI agent actually do with my Iterable data?

An agent connected to Iterable can list your campaigns, open one and read its metrics, create, schedule, trigger, abort, cancel or archive a campaign, manage catalogs and the items inside them, and record a cart update for a shopper. Short, concrete asks work best, such as pulling the numbers on last week's promo send rather than a long paragraph of instructions.

### Does connecting Iterable give the AI access to everything in my Iterable project?

No. Every call to Iterable runs with the Iterable API key that was provided when the connection was made, so the agent can only reach what that key is allowed to reach, and each person signs in to Elaichi as themselves. Elaichi can narrow that access further by role or by person, and it can never widen it beyond what Iterable itself permits.

### Can my team share one Iterable connection?

Yes. One person connects Iterable in Elaichi and shares the connection with a team, and nobody else ever handles the Iterable API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who scheduled a campaign or deleted a catalog item, not the account owner.

### Can I stop an agent from deleting or changing things in Iterable?

Yes. In Elaichi you can restrict individual Iterable actions, such as deleting catalog items or aborting a campaign, on a role or on one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to an Iterable connection when someone leaves?

Offboarding someone in Elaichi ends their access to Iterable at once, across Claude, ChatGPT, Cursor, Microsoft Copilot and every other client. A shared Iterable connection keeps working for everyone else on the team. If you want it gone entirely, disconnect Iterable once in Elaichi and it disappears from every client.

### Does the Iterable MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Iterable is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Iterable?

Yes. Both let Claude, ChatGPT or Cursor use Iterable. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Iterable call.

### How is Elaichi different from Composio for Iterable?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Iterable: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 157 Iterable tools

Every tool below is callable through https://api.elaichi.ai/mcp once Iterable is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Iterable browser token** (Create). Register a browser token for web push. Learn about identifying users by userId and email . Token limit : Maximum of 500 browser tokens per user profile. Returns a 400 response code when this limit has been exceeded.
- **Create a Iterable campaign abort** (Create). Abort a campaign. Abort a campaign given a campaign ID
- **Create a Iterable campaign archive** (Create). Archive campaigns. Archives one or more campaigns. This endpoint behaves the same as the archive feature in the UI. Scheduled or recurring campaigns will be cancelled, and running campaigns will be aborted.Archived campaigns will be hidden from the Campaigns page, but can still be viewed in the Archived tab. Rate limit : 5 requests/second, per API key.
- **List all Iterable campaign metrics** (List). Get metrics for campaigns. Get metrics for a single campaign or multiple campaigns. Rate limit : 10 requests/minute, per project. The body is a CSV export (the spec types it as a plain string); the connector returns the rows.
- **Create a Iterable campaign schedule** (Create). Schedule existing campaign to be sent
- **Create a Iterable campaign send** (Create). Send existing campaign now
- **Create a Iterable campaign trigger** (Create). Trigger a campaign. Trigger a campaign given lists
- **List all Iterable campaigns** (List). List campaign metadata. Get metadata about campaigns in a project. Use page and pageSize parameters to paginate results. If the unpaginated campaigns API is allowed for your project, then all campaigns are returned if no pagination parameters are provided. The unpaginated behavior is deprecated and may be removed in the future. Rate limit : 100 requests/second, per project.
- **Iterable campaigns cancel** (Cancel). Cancel a scheduled or recurring campaign. Cancel a campaign given a campaign ID
- **Create a Iterable campaign** (Create). Create a campaign. Creates a new blast or triggered campaign from an existing template. This endpoint can create email, push notification, web push notification, SMS, in-app message, and embedded message campaigns. Important note : Global suppression lists are not automatically added to campaigns created from this endpoint. To include a global suppression list, include it in the suppressionListIds request parameter. To learn more about creating a campaign with this API, see our API Overview .
- **Get single Iterable campaign by ID** (Get). Get a campaign. Get a campaign by ID. Rate limit : 100 requests/second, per project.
- **Create a Iterable cart update** (Create). Update a user's shopping cart items. Update the shoppingCartItems field on the user profile with shopping cart items. User profile is updated if it already exists (created otherwise) via the user field. Types of data fields must match the types sent in previous requests, across all data fields in the project. Learn about identifying users by userId and email .
- **List all Iterable catalog field mappings** (List). Get field mappings for a catalog. Field mappings (field to data types) and undefined fields of a catalog
- **Iterable catalog field mappings bulk update** (Update). Set a catalog's field mappings (data types). Set a catalog's field mappings (data types). After being set, a given field's data type may not be changed. Valid types: boolean, date, geo_location, long, double, object, and string.
- **Iterable catalog items bulk delete** (Delete). Bulk delete catalog items. Asynchronous. Delete the specified catalog items from the catalog.
- **List all Iterable catalog items** (List). Get the catalog items for a catalog. Get the catalog items for a catalog. Rate limit : 100 requests/second, per API key.
- **Iterable catalog items bulk create** (Create). Bulk create catalog items. Asynchronous. Create up to 1000 catalog items with a single request. Each of a catalog's items must have a unique ID that contains only alphanumeric characters and dashes and has a maximum length of 255 characters. If the catalog already contains an item with the same ID as one provided in the request body, the item in the catalog will be completely overwritten, unless replaceUploadedFieldsOnly is set to true. Do not use periods in field names. Rate limit : 100 requests/second, per API key.
- **Delete a Iterable catalog item by ID** (Delete). Delete a catalog item. Asynchronous. Deletes the specified item from the catalog. Data may not be deleted immediately.
- **Get single Iterable catalog item by ID** (Get). Get a specific catalog item. Get a specific catalog item from the given catalog.
- **Iterable catalog items partial update** (Update). Create or update a catalog item. Asynchronous. Create or update the specified catalog item in the given catalog. A catalog item's ID must be unique, contain only alphanumeric characters and dashes, and have a maximum length of 255 characters. If the catalog item already exists, its fields will be updated with the values provided in the request body. Previously existing fields not included in the request body will remain as is. Do not use periods in field names.
- **Update a Iterable catalog item by ID** (Update). Create or replace a catalog item. Asynchronous. Create or replace the specified catalog item in the given catalog. A catalog item's ID must be unique, contain only alphanumeric characters and dashes, and have a maximum length of 255 characters. If the catalog item already exists, it will be replaced by the value provided in the request body. Do not use periods in field names. Rate limit : 1000 requests/second, per API key.
- **List all Iterable catalogs** (List). Get catalog names. Get catalog names. Rate limit : 100 requests/second, per API key.
- **Delete a Iterable catalog by ID** (Delete). Delete a catalog. Delete the catalog with the specified name. Also deletes all collections that reference the specified catalog.
- **Create a Iterable catalog** (Create). Create a catalog. Create a catalog. Each catalog in a project must have a unique name. Catalog names can be no longer than 255 characters and must contain only alphanumeric characters and dashes.
- **List all Iterable channels** (List). Get channels. Get all message channels within the project. Rate limit : 100 requests/second, per project.
- **List all Iterable data exports CSV** (List). Export data to CSV. Export campaign analytics data in CSV format. Use of either 'range' or 'startDateTime' and 'endDateTime' is required. Rate limit : 4 requests/minute, per project.
- **List all Iterable data exports JSON** (List). Export data to JSON. Export campaign analytics data in JSON format, one entry per line. Use of either 'range' or 'startDateTime' and 'endDateTime' is required. Rate limit : 4 requests/minute, per project.
- **Create a Iterable device disable** (Create). Disable pushes to a mobile device. Disables push notifications to a given device. Learn about identifying users by userId and email .
- **Create a Iterable device token** (Create). Register a device token for push. Registers a device token for push. This will add the data if it doesn't exist yet. It will also update data fields on the device. Data will be merged; missing fields are not deleted. Also, note that there is a soft limit on the number of unique fields a user can have (default is 1,000). Types of data fields must match the types sent in previous requests, across all data fields in the project. Learn about identifying users by userId and email . Device limit : Maximum of 500 devices per user profile. Endpoint returns a 400 response code when this limit has been exceeded. Rate limit : 500 reques…
- **Create a Iterable double opt in subscription** (Create). Trigger a double opt-in subscription flow. This endpoint triggers a double opt-in subscription for a user. Once the user responds to the subscription confirmation message, they will be subscribed to the message types specified in the request body. This endpoint can only be used with SMS, double opt-in message types. To enable it, contact your customer success manager. Learn about identifying users by userId and email . Response Format Notes: 202 Accepted: Plain text (e.g., 'Request for double opt-in subscription accepted') 204 No Content: Returned when user is already subscribed to all requested message types (no body) 400 Bad Request…
- **Create a Iterable email send** (Create). Send an email to an email address. Send an email to a specific email address. Request data fields will override user profile data fields. A reference to the user profile is provided via the profile field, to help resolve field collisions. Learn about identifying users by userId and email .
- **Create a Iterable email template preview** (Create). Preview email template with custom data. Generate a fully rendered HTML preview of an email template using custom data. This endpoint simulates how a template would appear when sent to a user, allowing you to test template rendering with specific data fields and/or data feed data. Use this to preview templates before sending campaigns or to test template logic with different data scenarios. Note: If a template references a field that is not provided in the request data, that field will be rendered as an empty string, matching the behavior of actual email sends. Rate limit : 10 requests/second, per project.
- **Create a Iterable email template proof** (Create). Send a proof of an email template. Send a proof of an email template to a specific user. Rate limit : 20 requests/second, per API key.
- **List all Iterable email templates** (List). Get one email template by templateId (required query parameter; locale optional). Returns that template. Note: despite the .list name this returns ONE template (pass templateId, optional locale); use templates.list to list templates.

- **Update a Iterable email template by ID** (Update). Update email template
- **Create a Iterable email template** (Create). Create email template. Create email template if it doesn't exist already, otherwise update all email templates that match the name provided.
- **List all Iterable email views** (List). View a previously sent email. View a rendered version of a previously sent email. Learn about identifying users by userId and email . Rate limit : 100 requests/second, per project.
- **Iterable emails cancel** (Cancel). Cancel an email to a user. Cancels an email to a specific user. Request must include a campaignId and an email or userId , or just a scheduledMessageId . Learn about identifying users by userId and email .
- **Create a Iterable embedded message click** (Create). Track an embedded message click. This endpoint tracks a click on an embedded message. It creates an embeddedClick event. For test messages (proofs), no events are created. Learn about identifying users by userId and email .
- **Create a Iterable embedded message receipt** (Create). Track an embedded message received event. This endpoint tracks that a given embedded message was received on a device. It creates an embeddedReceived event in Iterable. An embeddedReceived event indicates that a device has retrieved a message. It does not mean that the message has been displayed. Iterable's SDKs automatically call this endpoint for each embedded message they retrieve. If you're not using an SDK, call this endpoint once per embedded message you retrieve from Iterable's API. For test messages (proofs), no events are created. Learn about identifying users by userId and email .
- **Create a Iterable embedded message session** (Create). Track an embedded message session and related impressions. This endpoint tracks a single embeddedSession event, and one embeddedImpression event for each of the session's impressions. An embeddedSession event represents a period of time when a user is viewing a page or a screen where embedded messages can be displayed (in one or many placements). An embeddedImpression event represents the number of times a given embedded message was visible during the session, and the total amount of time the message was visible (in seconds) across all those appearances. This endpoint does not create events for test messages (proofs). Learn about identifying users by…
- **List all Iterable embedded messages** (List). Get a user's embedded messages. This endpoint returns embedded messages for which the specified user is eligible, grouped by placementId . By default, it returns data for all placements that have messages for the user. To constrain the response to specific placements, provide one or more placementIds query parameters. Learn about identifying users by userId and email .
- **List all Iterable embedded templates** (List). Get one embedded template by templateId (required query parameter; locale optional). Returns that template. Note: despite the .list name this returns ONE template (pass templateId, optional locale); use templates.list to list templates.

- **Update a Iterable embedded template by ID** (Update). Update embedded message template
- **Create a Iterable embedded template** (Create). Create an embedded message template. Create an embedded message template if it doesn't exist yet, otherwise update all embedded message templates that match the name provided.
- **Create a Iterable event** (Create). Track an event. Events are created asynchronously and processed separately from single event (non-bulk) endpoint . To make sure events are tracked in order, send them all to the same endpoint (either bulk or non-bulk). There is a soft limit (default is 8,000) on the number of unique fields a custom event can have. For events of the same name, identically named data fields must be of the same type. Learn about identifying users by userId and email . Rate limit : 2000 requests/second, per project.
- **Iterable events bulk create** (Create). Bulk track events. Events are created asynchronously and processed separately from single event (non-bulk) endpoint . To make sure events are tracked in order, send them all to the same endpoint (either bulk or non-bulk). There is a soft limit (default is 8,000) on the number of unique fields a custom event can have. For events of the same name, identically named data fields must be of the same type. Learn about identifying users by userId and email . Rate limit : 10 requests/second, per project.
- **Create a Iterable experiment deletion** (Create). Delete an experiment. Deletes a campaign experiment that's in draft or ready status and returns the experiment as it was before deletion. This endpoint doesn't support journey experiments.
- **List all Iterable experiment metrics** (List). Get metrics for experiments. Get metrics for a single experiment or for multiple experiments. Note that we currently only support exporting email experiment metrics.
- **Iterable experiment settings bulk update** (Update). Update experiment settings. Updates settings on a campaign experiment that's in draft or ready status. Iterable changes only the fields you send. Omitted fields keep their current values, and null removes a setting when the field allows it. Blast campaigns accept blast and holdout settings, and triggered campaigns accept trigger settings. This endpoint works only with experiments that test message content: the subject line, preheader text, from name and sender, email body, or all content. It doesn't work with send time or Send Time Decisioning experiments. This endpoint doesn't support journey experiments.
- ...and 107 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
