Marketing & Social Media · Iterable + Claude
Iterable MCP with Claude: Run Smarter Cross-Channel Marketing Campaigns
The short answer
Claude works with Iterable through the Model Context Protocol (MCP), an open standard that lets Claude securely use software with permissions you control. Once connected with an API key, Claude can read campaign and message performance, update user profiles, track events and help manage campaigns through natural language requests from your marketing team.
What is Iterable?
Iterable is a cross-channel marketing platform used by marketing and growth teams. It lets them build campaigns across email, SMS, push notifications and in-app messages from one place. Teams use it to personalise customer journeys, respond to user behaviour such as sign-ups or purchases, and measure how well each message performs so they can improve engagement over time.
How Claude connects to Iterable through MCP
The Model Context Protocol, or MCP, is an open standard that acts like a universal adapter between Claude and other business software. It lets Claude use a tool securely, reading information and taking actions, with access limited to what your organisation allows. Claude does not get open-ended control of your systems.
Once Iterable is connected using an API key, Claude can typically look up user profiles, update attributes, record events, review campaign details and analyse how messages performed across channels. Your marketers can ask questions in everyday language, such as which email subject line drove the most conversions last month.
Permissions and approvals keep people in charge. Access is set to the least level needed for the job, and consequential actions such as launching or changing a live campaign can require a named person to approve them first. Activity can be logged so your team can see what was done, when and by whom.
What you can automate
Campaign performance summaries
Marketing managers ask Claude for a weekly summary of open, click and conversion rates across email, SMS and push. Claude pulls the figures from Iterable, highlights what changed and suggests where to focus testing. The team spends less time exporting reports and more time acting on them.
Keeping user profiles accurate
Customer support or CRM staff can ask Claude to update a customer's preferences, language or contact details in Iterable. Claude records the change against the right profile, reducing the risk of customers receiving messages they have opted out of or addressed incorrectly.
Event tracking for journeys
Product and growth teams can have Claude record key in-app events, such as a trial starting or a feature being used. These events can then trigger the right follow-up journey. Claude helps check that events are being logged consistently so journeys behave as designed.
Audience and segment checks
Before a send, a campaign planner can ask Claude how many users fall into a proposed audience and what their recent engagement looks like. This helps avoid sending to very small or unsuitable groups and supports cleaner, better-targeted campaigns.
Post-campaign reviews
After a campaign ends, Claude can compare results against earlier campaigns and summarise what worked for different customer groups. Teams use these reviews to build a shared record of lessons learned, which helps new campaigns start from stronger foundations.
An end-to-end workflow: Abandoned trial recovery with CRM follow-up
TriggerA user's free trial ends without an upgrade, as recorded in the CRM.
Claude reads the trial status from the CRM and checks the user's recent activity in Iterable.
Claude records a trial-ended event in Iterable so the correct journey starts.
The Iterable journey sends a tailored email and in-app message based on the features the user used.
Claude tracks the responses and reports weekly conversion rates to the growth team.
A marketing lead reviews any changes to the journey before they go live, keeping a human in control.
OutcomeTrial users receive timely, relevant follow-up across channels, and the growth team sees clearly which messages lead to upgrades. Results vary by business, but teams commonly find that consistent follow-up reduces the number of trials that end without a response.
How we set it up
Free automation audit
We review your current Iterable campaigns, journeys and reporting alongside your other systems, such as CRM and ticketing, to find the workflows worth automating first. You leave with a clear plan and no obligation.
Secure connection with an API key
We set up the connection using an Iterable API key, created with the permissions your team agrees on. Access is kept to the least level needed, and the key is stored securely.
Workflow design and approvals
We design the end-to-end workflow across Iterable and your other business systems. We agree which actions Claude can take alone and which need a named person's approval before they happen.
Testing against real cases
We test the workflow using real past campaigns and user records, checking results against what your team expected. Any issues are fixed before anything goes live.
Launch, monitoring and training
We launch with monitoring and audit logs in place, then train your marketing and operations staff to use Claude confidently and to review its outputs.
Who benefits
- Marketing managers
- Faster access to campaign performance and clearer summaries to guide decisions.
- Growth and lifecycle teams
- Easier coordination of journeys, events and audiences across channels.
- Customer support and CRM teams
- Accurate profile updates and fewer messages sent to the wrong customers.
- IT and operations leaders
- Controlled, auditable access to marketing data with clear approval steps.
Security and control
- Connect using an API key with least-privilege permissions, limited to the actions each workflow needs.
- Require named human approval for consequential actions such as launching or changing live campaigns.
- Keep audit logs of actions Claude takes so every change can be traced.
- Test all workflows against real past cases before launch, and monitor them after go-live.
- Review API key ownership and rotate keys on a regular schedule.
For teams in the US, UK, India and the Middle East
Organisations in the United States and the United Kingdom can have Claude connected to Iterable with data handled in line with their applicable privacy rules. In India, we design workflows to meet the Digital Personal Data Protection Act, 2023. For organisations in the UAE and Saudi Arabia, we align setups with local data protection laws. We choose the hosting region for your Claude deployment to meet your data residency and compliance requirements.
Learn more about Claude and MCP
Anthropic's AI model and assistant.
Secure links between Claude and business tools.
How engineers build and change software with Claude.
Hosted agents that run multi-step work.
The open standard Claude uses to connect to tools.
Frequently asked questions
What does the Iterable MCP server do?
The Iterable MCP server acts as a secure bridge between AI tools like Claude and your Iterable account. It lets Claude read campaign and performance information and carry out approved actions, such as updating user profiles or recording events, using the permissions you set. It does not give open access to your whole account.
Is connecting Claude to Iterable secure?
Security depends on how the connection is set up. We use an API key with the least permissions needed, store it securely, log actions and require human approval for important changes. Regular key rotation and monitoring further reduce risk. We cannot guarantee security outcomes, but these controls follow sound practice.
What can Claude do with Iterable once connected?
Typically, Claude can review campaign results, summarise performance across email, SMS, push and in-app channels, look up and update user profiles, and record events that trigger journeys. You can ask for these things in plain language. Actions that change live marketing are usually set to require approval.
How long does setup take?
Timelines depend on how many campaigns, journeys and systems are involved. A focused connection for a single workflow is often completed in a few weeks, including testing and training. Broader programmes take longer. Your free automation audit gives a realistic timeline for your situation.
Which plan or permissions do I need?
You need an Iterable account and an API key with permissions that match the workflows you want to automate. The exact requirements depend on your Iterable setup and your internal policies, so we check these during the audit. We recommend creating a dedicated key with only the access the project requires.