Iterable Launches a Hosted MCP Server for Claude, ChatGPT and Cursor

Iterable has announced a hosted MCP server that brings its cross-channel marketing platform into Claude, ChatGPT and Cursor. Marketers install it from the connector directory of those tools, sign in with their own Iterable login, and can then build journeys, proof emails and audit campaigns from a chat. Iterable presented it on 12 November 2026 as the headline of its Winter 2026 product launch.

Iterable already offered a self-hosted MCP server that each person ran on their own machine with a personal API key. The new version is managed by Iterable, connects remotely, and is built for whole teams rather than for one technical user at a time. Every request goes through Nova Agent, part of Iterable's Nova Intelligence.

What the hosted Iterable MCP server does

The Model Context Protocol (MCP) is the open standard that lets AI assistants call external tools. With the hosted server, the assistant does not talk to the Iterable API directly: requests run through Nova Agent, which Iterable says builds its own marketing best practices into the answers. Iterable says the agent can complete multi-step work, such as taking a journey from a first draft to a launch-ready state.

The examples Iterable gives in its community announcement are concrete, day-to-day email operations:

• Journeys: build and stage a journey from the chat, then preview and proof its email;
• Quality checks: QA-check and proof emails before they go out;
• Audits: review live campaigns and find every campaign that uses a given data field;
• Reporting: analyse campaign performance with plain-language questions.

Iterable also says its own interface is available inside these AI tools, so a marketer can stay in the assistant while working on the account.

Permissions: one login per person, not one key per team

The main change from the self-hosted server is how access is controlled. The old setup relied on a personal API key stored on each machine. The hosted server uses per-user authentication: each person signs in with their own Iterable account, including through SSO, and in Iterable's words each agent is "limited to that person's existing permissions". Admins decide whether the connector is enabled and whether it can only read data or also write changes. Iterable stresses that there are no shared API keys, and that teams no longer need to build a custom connection for each individual.

Hosted or self-hosted

Iterable keeps both options. The self-hosted server, which runs locally and sends requests straight to the API with a personal key, remains available and free. Switching to the hosted server is an opt-in setup. Iterable's announcements do not mention pricing or plan restrictions for the hosted version.

The rest of the Winter 2026 release

The MCP server is part of a wider release that touches email teams in several ways:

• AI Summary preview: a new filter in Preview on Devices shows how supported inbox experiences are likely to summarise an email, so teams can adjust content before sending. Iterable says it is a prediction, not a guarantee.
• Spam testing discontinued: Iterable's community post says spam testing is being discontinued in its preview tools, and that Preview on Devices moves to a new rendering provider with fewer clients and devices.
• AI-assisted SDKs: version-matched guidance for the iOS, Android and React Native SDKs, plus a skill for coding agents, with a target of a verified first message in under an hour.
• Integrations Hub: Iterable says it is tripling the number of integrations, adding sources such as HubSpot, Microsoft Dynamics 365, Intercom, Chargebee, Recurly, BigCommerce and WooCommerce, and paid media audiences on Reddit Ads, Snapchat, Microsoft Advertising and ChatGPT Ads, matched on hashed email.

Why it matters for email platforms

Iterable is the latest email platform to move from a developer-oriented MCP server to a managed connector that ordinary marketers can install. The direction is the same across the market: campaign work moves into the AI assistant, and the controls around who can change what become the real safeguard. Iterable's answer is to reuse the role-based permissions customers already have, and to let admins keep the connector read-only.

Action checklist

• Decide read-only or write access before you enable the connector, and start with read-only if your team is new to AI agents.
• Review Iterable roles, because the agent inherits each user's existing permissions: anyone who can launch a journey in the interface can do it from the chat.
• Retire shared API keys once your team has moved to the hosted server, if it opts in.
• Keep a human proof step before any journey or campaign built in a chat goes live.
• Plan a replacement for spam testing if you used it in Iterable's preview tools, for example a separate seed or placement test.
• Read the release notes on 2 December for availability and setup details.

Sources

1. Iterable: Winter Product Launch, Your AI Advantage Just Went Team-Wide, 12 November 2026 (primary source)
2. Iterable Community: Winter 2026 Product Release Spotlight, 12 November 2026

Related on SMTPedia

• Selzy launches an MCP server that lets AI assistants send campaigns
• Best email inbox for AI agents: Mailtrap vs AgentMail vs Mailgun
• How to add an Iterable unsubscribe link