Skip to main content

Set up the Iterable MCP server

The Iterable MCP server (@iterable/mcp) gives AI agents access to Iterable's cross-channel marketing platform — campaigns, metrics, templates, lists, journeys, and catalogs. This guide covers creating a server-side API key in Iterable and configuring the connector in MintMCP.

Prerequisites​

  • A MintMCP admin account
  • An Iterable account with at least one project
  • Org admin access, or a member role with the API Keys permission (Project Configuration → API Keys)
  • Your Iterable data center: US (api.iterable.com) or EU (api.eu.iterable.com)

Create a server-side API key​

API keys in Iterable are project-scoped — create one key per project you want to connect.

  1. Sign in to Iterable and open the project you want to connect.
  2. Go to Integrations → API Keys and click New API key.
  3. Set the key type to Server-side — client-side types (Mobile, Web, JavaScript) can only access a limited subset of endpoints and won't work with the connector's tools.
  4. Name the key something identifiable, for example mintmcp-connector.
  5. Copy the key — it's a 32-character lowercase hex string. You'll need it in the next step.

Add Iterable to MintMCP​

  1. Go to app.mintmcp.com/vmcps?tab=manage-store.

  2. Find Iterable in the list and click to install it.

  3. Set the following environment variables in the connector settings:

    VariableRequiredDescription
    ITERABLE_API_KEYYesThe server-side API key from the previous step
    ITERABLE_BASE_URLNoDefaults to the US data center (https://api.iterable.com). Set to https://api.eu.iterable.com for EU-hosted projects

  4. Click Save. The connector starts with the read-only tool set, covering campaigns, metrics, templates, lists, journeys, and catalogs. To go beyond read-only, set the permission flags described in the next section.

Expand permissions (optional)​

By default, the connector runs in read-only mode. Add any of these environment variables to the connector settings to expand access — changes take effect on the next session:

FlagEffect
ITERABLE_USER_PII=trueExposes tools that read user profile data (email addresses, phone numbers, custom data fields)
ITERABLE_ENABLE_WRITES=trueAdds tools to create, update, and delete campaigns, templates, lists, and journeys
ITERABLE_ENABLE_SENDS=trueAdds tools to send messages and trigger campaigns and journeys

Iterable's MCP tools don't declare read-only or destructive annotations, so clients can't visually distinguish tools that send messages from those that only read data. The permission flags and MintMCP's per-tool toggles are the primary guardrails — enable ITERABLE_ENABLE_SENDS only for deployments that genuinely need to trigger messages to real users.

Security considerations​

  • Server-side API keys have the highest access level in Iterable. MintMCP stores the key encrypted — never put it in client-side code or version control.
  • Keys are project-scoped and carry no per-user identity; all connector users act with the same key. Deploy one connector per Iterable project you want to connect.
  • The connector defaults to read-only. Writes, sends, and user-PII access are each separate opt-ins — enable only what your use case requires.
  • To revoke access, delete the key in Iterable at Integrations → API Keys.

Next steps​