How to Connect Customer.io to Claude (and What It Can't Do)
Customer.io now ships an official MCP server, and Claude can connect to it. As of mid-2026, Customer.io publishes first-party MCP support with a dedicated Claude setup guide, hosted at mcp.customer.io/mcp for US workspaces and mcp-eu.customer.io/mcp for EU ones. Depending on your organization, it shows up in Claude’s connector list to enable directly, or you add it as a custom connector by URL. Either way, MCP connectors require a paid Claude plan — the free tier is out.
What the connection is not: an automation engine. Claude only talks to Customer.io inside a chat you’re actively having. Nothing listens for a trial_started event overnight, and nobody nudges the churn-risk segment at 6am unless you’re sitting there typing. That distinction matters more for Customer.io than for almost any other tool, because Customer.io’s entire job is event-triggered messaging.
What the official connector does well
Once authorized, Claude can pull your workspace into the conversation: people and their attributes, segments, campaign and broadcast performance, delivery data. The scopes you grant during the OAuth handshake decide what Claude can touch — Customer.io asks you to pick workspaces and permission levels when you connect, and you can revoke a session later from your Personal Settings.
In practice that makes Claude a fast query-and-drafting layer over your messaging workspace:
- “Which campaigns in our onboarding journey had the worst click rate last month? Show me the copy for the losers.”
- “Compare deliveries and opens for the win-back broadcast against the version we sent in March, then suggest three subject lines to test.”
- “Pull up this person’s attributes and tell me which segments and journeys they’re currently in.”
Write access is scope-dependent. Customer.io gates everything behind permission scopes rather than promising blanket write capability, so review what a given scope allows before assuming Claude can edit a live journey or change people data from chat.
Enabling it
- In Claude (web or desktop), open Settings → Connectors.
- Find Customer.io in the connector list and enable it. If your workspace doesn’t surface it, choose Add custom connector and paste
https://mcp.customer.io/mcp— or themcp-euendpoint if your account lives in Customer.io’s EU region. - Sign in to Customer.io, choose the workspaces and permission scopes Claude should get, and allow access.
- Ask Claude something about your campaigns to confirm the tools loaded.
One technical footnote from Customer.io’s docs: the server speaks streamable HTTP, not SSE — only relevant if you’re wiring it into a different MCP client than Claude.
The gap: Customer.io runs on events, this connector doesn’t
Customer.io’s core loop is “user does X, message goes out.” The Claude connector sits entirely outside that loop:
- A user hits trial day 3 without inviting a teammate. Your journeys fire; Claude doesn’t notice, because no Claude connector reacts to events.
- Delivery on your biggest broadcast tanks at 2am. Claude can diagnose it beautifully — when you ask the next morning. It can’t flag it as it happens.
- You can have Claude draft the re-engagement email in seconds, but the “watch the segment, send when someone enters it” half stays with Customer.io’s own workflow builder or with a human.
None of this is a bug. It’s the shape of every Claude connector: chat in, answer out, no background process, no schedule, no webhook listening on your behalf.
When you need the loop closed: Carly
If what you actually want is messaging work that happens without you prompting — react when a user enters a segment, chase a failed delivery, sync new signups into Customer.io from your other tools — that calls for an agent with triggers, not a chat connector.
Carly is an AI executive assistant built around exactly that. It runs in the cloud, wakes on events (an email arrives, a form is submitted, a schedule fires), and executes multi-step workflows: update people and segments in Customer.io, draft and send email through Gmail or Outlook, log tasks, tie it back to your calendar. You describe the workflow in plain English — “when someone books a demo, add them to our Customer.io trial segment and send a prep email” — and Carly interviews you, then builds it. No MCP server to babysit, no scopes to audit.
AI agents start at $35/month, and workflow steps that don’t use AI run free and unlimited. Carly connects to 200+ tools — see the Customer.io integration page or browse all integrations.
Side by side
| Claude + Customer.io MCP | Carly | |
|---|---|---|
| Query people, segments & campaign metrics | Yes (scope-dependent) | Yes |
| Draft lifecycle email copy | Yes, in chat | Yes, inside workflows |
| React when a user enters a segment | No | Yes |
| Send follow-up email automatically | No | Yes (Gmail + Outlook) |
| Runs overnight / laptop closed | No | Yes (cloud) |
| Setup | Enable connector on a paid Claude plan | Describe the workflow in plain English |
| Pricing | Paid Claude plan | AI agents from $35/mo |
Frequently Asked Questions
Does Claude integrate with Customer.io?
Yes. Customer.io publishes an official MCP server (setup docs here) that you enable from Claude’s connector settings or add by URL as a custom connector. You need a paid Claude plan, and the connection only works inside chats you start.
Can Claude trigger a Customer.io campaign when a user does something?
No. Claude connectors have no event triggers — nothing fires when a user converts, churns, or enters a segment. Event-driven sends stay in Customer.io’s own journeys, or in an agent platform like Carly that acts on triggers.
My workspace is in Customer.io’s EU region — does the connector still work?
Yes. Use the EU endpoint, https://mcp-eu.customer.io/mcp, instead of the US one when adding the connector.
Do I need a paid Claude plan for this?
Yes. MCP connectors, including Customer.io’s official one, aren’t available on Claude’s free tier. The server itself costs nothing extra on Customer.io’s side.
What if I want lifecycle messages handled while I’m not in a chat?
That’s beyond any Claude connector — they respond in conversation and never act on their own. Carly fires on events 24/7 in the cloud, updating segments and sending messages as things happen. AI agents start at $35/month.
More: Claude connectors · Can Claude send emails · Claude vs Carly · Claude Cowork alternatives · Best AI email tools · Claude + Kit · Claude + Lemlist · Claude + MailerLite
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
