Can my team share one Customer.io (EU) connection?

Yes. One person connects Customer.io (EU) and shares it with a team in Elaichi, and nobody else ever sees or handles a credential. Each teammate still signs in to Elaichi as themselves, so every call to Customer.io in EU is logged under their own name.

Marketing Automation

Customer.io (EU) MCP connector

Connect Customer.io (EU) to Elaichi once and Claude, ChatGPT, Cursor, and the Elaichi Agent can read and update people, segments, campaigns, and messages in your EU workspace, inside your own sign-in, with every call logged.

Connect on Elaichi How to connect

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 (EU) to Claude, ChatGPT or Cursor

Two steps, about a minute.

In Elaichi

Connect Customer.io (EU) once

Open Connections, choose Add connection, and pick Customer.io (EU).
Optionally set Share with to give a team access, then press Connect.
Approve it in Customer.io (EU). Customer.io (EU)'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.

customer.io (eu)

All categories

Customer.io (EU)

Attentive

Beamer

beehiiv

Bird

Buffer

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 (EU) 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 (EU) 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 (EU) 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 (EU) 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.

Connect Customer.io (EU) on Elaichi See pricing

Use cases

What teams do with Customer.io (EU) 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 the morning standup

Ask which campaigns in Customer.io (EU) sent the most messages yesterday and how each one is set up, without opening five tabs.
Lifecycle

Find out why someone got an email

Look up a person in Customer.io (EU), see their attributes and the segments they belong to, and explain which campaign reached them.
Support

Fix a customer profile during a ticket

Correct a misspelled name or a wrong plan attribute on a person's record in Customer.io (EU) while the customer is still on the line.
Product

Confirm an event is actually arriving

Ask whether the new signup event is landing on people in Customer.io (EU) and which attributes it carries, before you build a trigger on it.
Sales

Pull the right people for an outreach list

Get the members of a segment in Customer.io (EU), with the attributes you care about, ready to paste into a call sheet.
Operations

Clean up stale records in bulk

Review test accounts and duplicate people in Customer.io (EU), then remove them one at a time with each deletion written to the log.

Try asking

“Which segments in Customer.io gained the most people this week?”
“Why did Ana Lopez receive the onboarding campaign email?”
“Update the plan attribute for [email protected] to Enterprise.”

See all 8 Customer.io (EU) tools below

Compare

Elaichi vs Zapier MCP vs Composio for Customer.io (EU)

All three can connect Customer.io (EU) to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Customer.io (EU), by what to check
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 (EU) tools	Allow or restrict single Customer.io (EU) 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 (EU) 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 (EU) tools for your AI agents

8 tools are ready to call through Elaichi's MCP endpoint the moment you connect Customer.io (EU), governed by the same roles, restrictions, and audit log as everything else in Elaichi. Customer.io (EU) builds and runs these tools.

See it in Elaichi

What connecting Customer.io (EU) gets you

6 screens from the product, each doing one job for your Customer.io (EU) account.

The agent

Ask about people and campaigns in plain language.

Live answers from Customer.io (EU) on segments, attributes, and messages, without opening the app.

people
segments
campaigns
messages

Ask Elaichi to work across your apps.

Which segments in Customer.io gained the most people this week?

Why did Ana Lopez receive the onboarding campaign email?

Update the plan attribute for [email protected] to Enterprise.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One endpoint reaches Customer.io (EU) from any client.

Claude, ChatGPT, and Cursor share one governed endpoint, with no SDK and no shared API key.

ElaichiMCP clients

Claude

ChatGPT

Cursor

Copy the endpoint

https://api.elaichi.ai/mcp

Client	Connected by	Status	Last used
Claude	E Emily Carter	• Connected	4 minutes ago
Cursor	M Megan Brooks	• Connected	2 hours ago
ChatGPT	R Ryan Hayes	• Connected	Yesterday

Tool catalog

8 tools cover Customer.io (EU) end to end.

People, segments, campaigns, and messages are read, written, and removed with no custom code.

Cio prime
Cio schema
Cio read API
Cio write API

ElaichiTools

Tool	Action	Description
Cio prime	Action	Loads the AI-ready reference for the Customer.io API. Your AI tool should call this at the start of a task.
Cio schema	Action	Discovers API endpoints—list resources, find endpoints, and inspect parameters before making calls.
Cio read API	Action	Makes authenticated GET requests. Use for listing, reading, and inspecting resources. Supports filtering, pagination, and dry-run previews.
Cio write API	Action	Makes authenticated POST, PUT, and PATCH requests. Use for creating and editing resources. Supports dry-run previews.
Cio delete API	Delete	Makes authenticated DELETE requests. Use for removing resources. Supports dry-run previews.

Toolboxes

Every team gets its own Customer.io (EU) toolbox.

Marketing, support, and sales each see only the tools their work in Customer.io (EU) needs.

Marketing
Lifecycle
Support
Product

ElaichiToolboxes

Name	Source template	Tools	Created
Marketing toolbox Customer.io (EU) · campaigns and broadcasts	Customer.io (EU) starter	18	Mar 4, 2026
Lifecycle toolbox Customer.io (EU) · segments and journeys	—	9	Mar 2, 2026
Support toolbox Customer.io (EU) · people and attributes	—	24	Feb 27, 2026
Product toolbox Customer.io (EU) · events and triggers	Customer.io (EU) starter	6	Feb 19, 2026
Sales toolbox Customer.io (EU) · segments and outreach lists	—	31	Jan 30, 2026
Operations toolbox Customer.io (EU) · record cleanup and deletions	—	12	Jan 22, 2026

Shared connections

Teammates work through a connection without a credential.

One person connects Customer.io (EU), shares it, and nobody else ever handles a secret.

Marketing
Lifecycle
Support
Product

ElaichiConnections

Connection	Scope	Status	Access
CU Customer.io (EU) (Marketing) Connected by Emily Carter	Personal	• Active	1 team · 6 members
CU Customer.io (EU) (Lifecycle) Connected by Jake Morgan	Organization	• Active	3 teams · 24 members
CU Customer.io (EU) (Support) Connected by Megan Brooks	Organization	• Active	2 teams · 11 members
CU Customer.io (EU) (Product) Connected by Tyler Reed	Personal	• Needs re-auth	1 team · 3 members
CU Customer.io (EU) (Sales EMEA) Connected by Ryan Hayes	Personal	• Active	Not shared
CU Customer.io (EU) (Operations) Connected by Ashley Parker	Personal	• Active	2 teams · 9 members

Audit log

Every change in Customer.io (EU) names a person.

When, who, what happened, and which record, in an append-only log you can answer from.

When
Who
What happened
Type

ElaichiAudit log

When	Who	What happened	Type
2 minutes ago Mar 6, 2026, 3:10 PM	E Emily Carter [email protected]	Restriction Created	Access
8 minutes ago Mar 6, 2026, 3:04 PM	J Jake Morgan [email protected]	Restriction Updated	Access
14 minutes ago Mar 6, 2026, 2:58 PM	M Megan Brooks [email protected]	Role Assigned	Access
20 minutes ago Mar 6, 2026, 2:52 PM	T Tyler Reed [email protected]	Customer.io (EU) Users Updated	MCP
26 minutes ago Mar 6, 2026, 2:46 PM	R Ryan Hayes [email protected]	Customer.io (EU) People Created	MCP
32 minutes ago Mar 6, 2026, 2:40 PM	A Ashley Parker [email protected]	Customer.io (EU) People List	Toolbox

Launching 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 work in Customer.io (EU).

New people are fetched, grouped, drafted into a digest, approved, then posted back.

Customer.io (EU) digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

Run now

✓

Schedule

Every weekday at 8:00 AM

0.2s
✓

Fetch people

Customer.io (EU)

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 (EU)

Queued

Collections and dashboards

Customer.io (EU) health, computed without a model.

Four metrics, fourteen days of people created, and a team breakdown, refreshed on a schedule.

Customer.io (EU) health

Refreshed 4 minutes ago · every 15 minutes · from the people collection

Live

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%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect Customer.io (EU) to Claude?

Connect Customer.io (EU) in Elaichi by signing in to your Customer.io EU account over OAuth, with no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and Customer.io (EU) is available in your next conversation.

Does Customer.io (EU) work with ChatGPT and Cursor as well as Claude?

Yes. Once Customer.io (EU) is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Customer.io in EU once and every client picks it up.

What can an AI agent actually do with my Customer.io (EU) data?

It can look up people, their attributes, and the segments they belong to in Customer.io (EU), check how campaigns, broadcasts, and messages are set up, update a person's record, and remove records you no longer want. Short, concrete asks work best, such as the name of a person or a campaign rather than a long paragraph.

Does connecting Customer.io (EU) give the AI my whole workspace?

No. Every request to Customer.io (EU) runs as the person who signed in, so the AI can only reach the workspaces and records that person can already reach in Customer.io in EU. Elaichi can narrow that access further with roles and restrictions, and it can never widen it.

Can I stop an agent from deleting or changing things in Customer.io (EU)?

Yes. Restrictions in Elaichi apply per action, so you can allow reading people and campaigns in Customer.io (EU) while blocking updates or deletions. A restricted action is never advertised to Claude, ChatGPT, or Cursor at all, so no prompt can reach it.

What happens to a Customer.io (EU) connection when someone leaves?

Offboarding a person in Elaichi ends their access to Customer.io (EU) at once, across every client they used. A shared Customer.io in EU connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client.

Does the Customer.io (EU) MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Customer.io (EU) 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 (EU)?

Yes. Both let Claude, ChatGPT or Cursor use Customer.io (EU). 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 (EU) call.

How is Elaichi different from Composio for Customer.io (EU)?

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 (EU): 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 (EU) in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Connect Customer.io (EU) Talk to us

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.