# 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. Source: https://elaichi.ai/connectors/customer-io-eu/ ## Facts | | | | --- | --- | | Application | Customer.io (EU) | | Category | Marketing Automation | | AI tools | 8 | | Authentication | Connects over OAuth | | Bring your own OAuth app | No | | Native MCP | Yes. Customer.io (EU) builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top | | Support for its tools | customer.io/support | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once Customer.io (EU) is connected - 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 maria@acme.com to Enterprise. ## Connect Customer.io (EU) in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Customer.io (EU). 2. Optionally set Share with, then press Connect. 3. Approve it in Customer.io (EU). Customer.io (EU)'s own window opens. Whoever approves it decides what this connection can reach. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Customer.io (EU) tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Customer.io (EU) MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 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 Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Customer.io (EU) to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Customer.io (EU) tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Customer.io (EU) through Elaichi ### Check a campaign before the morning standup Marketing. Ask which campaigns in Customer.io (EU) sent the most messages yesterday and how each one is set up, without opening five tabs. ### Find out why someone got an email Lifecycle. Look up a person in Customer.io (EU), see their attributes and the segments they belong to, and explain which campaign reached them. ### Fix a customer profile during a ticket Support. 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. ### Confirm an event is actually arriving Product. 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. ### Pull the right people for an outreach list Sales. Get the members of a segment in Customer.io (EU), with the attributes you care about, ready to paste into a call sheet. ### Clean up stale records in bulk Operations. Review test accounts and duplicate people in Customer.io (EU), then remove them one at a time with each deletion written to the log. ## 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. | What to check | Elaichi | Zapier MCP | Composio | | --- | --- | --- | --- | | Where the AI connects | One address for the whole organization. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026. Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/). ## 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 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. ### 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. ## All 8 Customer.io (EU) tools Every tool below is callable through https://api.elaichi.ai/mcp once Customer.io (EU) is connected, subject to the toolbox it is in and the restrictions on the caller. - **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. - **Cio skills list** (List). Lists available agent skills—task-specific instructions for multi-step operations like creating automations. - **Cio skills read** (Action). Reads the full content of a specific skill so the AI tool can follow step-by-step workflows. - **Cio auth status** (Action). Shows the current authentication state, including which workspaces the token can access.