Customer.io MCP connector
Connect Customer.io to Elaichi and Claude, ChatGPT, Cursor, and the Elaichi Agent can look up people, segments, campaigns, and broadcasts, update attributes, and trigger messages, all inside the access of whoever signed in.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
8 tools
How to connect
How to connect Customer.io to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Customer.io once
-
Open Connections, choose Add connection, and pick Customer.io.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Customer.io. Customer.io's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Customer.io MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Customer.io MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Customer.io MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Customer.io to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Customer.io through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Marketing
Check a campaign before it goes out
Ask which people a segment will reach and what each step of the campaign does, then fix the segment in Customer.io before the send.
-
Lifecycle
Catch a profile up after a conversation
Update a person's attributes in Customer.io after a call so the right onboarding flow picks them up without anyone opening the app.
-
Support
See what a customer was sent
Look up a person in Customer.io and see which campaigns and broadcasts reached them before you reply to their ticket.
-
Product
Record an event when something ships
Track an event against a person in Customer.io so the welcome or upgrade sequence starts without a manual hand-off.
-
Sales
Move a lead into the right segment
After a demo, update the lead's plan and stage attributes so Customer.io drops the nurture sequence and starts the trial one.
-
Operations
Remove people who asked to be deleted
Find people who requested deletion and remove them from Customer.io, with every removal recorded in the audit log.
Try asking
- “Which people in the trial segment have not opened the onboarding campaign?”
- “Show me every broadcast sent to enterprise customers this month.”
- “Set the plan attribute to pro for [email protected].”
Compare
Elaichi vs Zapier MCP vs Composio for Customer.io
All three can connect Customer.io 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.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Customer.io tools | Allow or restrict single Customer.io 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 Customer.io 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 | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Customer.io tools for your AI agents
8 tools are ready to call through Elaichi's MCP endpoint the moment you connect Customer.io, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Customer.io builds and runs these tools.
No tools match your search.
See it in Elaichi
What connecting Customer.io gets you
6 screens from the product, each doing one job for your Customer.io account.
The agent
Ask about people and campaigns in plain language.
Get answers from live Customer.io segments, campaigns, and broadcasts without opening the app.
- people
- segments
- campaigns
- broadcasts
Ask Elaichi to work across your apps.
Which people in the trial segment have not opened the onboarding campaign?
Show me every broadcast sent to enterprise customers this month.
Set the plan attribute to pro for [email protected].
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint connects Customer.io to every client.
Claude, ChatGPT, and Cursor reach Customer.io through one governed endpoint, no SDK, no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
8 tools cover Customer.io with no code.
Read, write, and delete people, segments, campaigns, and broadcasts without writing a line of code.
- Cio prime
- Cio schema
- Cio read API
- Cio write API
ElaichiToolsToolboxes
Every team gets its own Customer.io toolbox.
Marketing, lifecycle, and support each work from a toolbox scoped to their team.
- Marketing
- Lifecycle
- Support
- Product
ElaichiToolboxesShared connections
Teammates work through Customer.io without a credential.
One person connects Customer.io, shares it with teams, and nobody else sees a key.
- Marketing
- Lifecycle
- Support
- Product
ElaichiConnectionsAudit log
Every Customer.io action lands in the log.
See who read, updated, or deleted which person, segment, or campaign, and when.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule starts real Customer.io work.
New people are fetched, grouped, drafted into a digest, approved, then posted back to Customer.io.
Customer.io digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch people
Customer.io
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Customer.io
Queued
Collections and dashboards
Customer.io numbers arrive without anyone asking.
Four metrics, 14 days of people created, and a team breakdown, refreshed with no model involved.
Customer.io health
Refreshed 4 minutes ago · every 15 minutes · from the people collection
People
1,284 ↓ 12%
Segments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
People created
Last 14 days
By team
Share of activity
Marketing 34%
Lifecycle 27%
Support 21%
Product 18%
FAQ
Frequently asked questions
How do I connect Customer.io to Claude?
Connect Customer.io in Elaichi, which signs you in over OAuth with your own Customer.io login, so there is no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude then sees Customer.io alongside anything else you have connected.
Does Customer.io work with ChatGPT and Cursor as well as Claude?
Yes. Customer.io is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You do not repeat the Customer.io sign-in for each client.
What can an AI agent actually do with my Customer.io data?
An agent can look up a person in Customer.io and see their attributes, which segments they belong to, and which campaigns and broadcasts reached them. It can update attributes, record events, add people to segments, and trigger a message, and it can remove a person when asked. Short asks such as 'show me the trial segment' work better than long sentences.
Does connecting Customer.io give the AI access to my whole workspace?
No. Everything runs under the Customer.io login of the person who connected, so the agent sees only the workspaces, segments, and campaigns that person can already see. Elaichi can narrow that further, for example to reading only, but it can never widen access beyond what Customer.io already grants.
Can I stop an agent from deleting or changing things in Customer.io?
Yes. Restrictions in Elaichi apply per action, so you can allow reading people and campaigns in Customer.io while blocking updates, sends, or deletions. A restricted action is never advertised to Claude or any other client, so no prompt can reach it.
What happens to a Customer.io connection when someone leaves?
Offboarding someone in Elaichi ends their access to Customer.io at once, with no change needed in Customer.io itself. A connection shared with a team keeps working for everyone else. If you disconnect Customer.io in Elaichi, it disappears from Claude, ChatGPT, Cursor, and every other client in one step.
Does the Customer.io MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Customer.io 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, 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 Customer.io?
Yes. Both let Claude, ChatGPT or Cursor use Customer.io. 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 Customer.io call.
How is Elaichi different from Composio for Customer.io?
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 Customer.io: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Customer.io in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.