Connect Customer.io to Claude Code

Let Claude build segments and stage broadcasts in Customer.io. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Customer.io to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Customer.io, you add a Customer.io MCP server: a small hosted service that exposes Customer.io's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Customer.io account. No API keys pasted into config files.

claude mcp add --transport http customer-io https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Customer.io once connected?

Full read-write Customer.io access lets Claude build and update manual segments by adding or removing the people you name, identify or update people and their attributes, draft and stage broadcast or campaign messages, and trigger an API-driven send once you approve. The audience work and message drafting that used to live in the dashboard and spreadsheets happen where they belong.

Build or update a manual segment by adding or removing the people you describe
Identify or update a person and their attributes through the Track API
Draft email, push, or in-app message variants and stage them in a broadcast
Trigger an API-driven broadcast to a defined segment after you approve
Send a transactional message to a single person once you confirm
Export delivery and campaign metrics for analysis

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Customer.io access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Customer.io API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Customer.io changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Customer.io connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Customer.io connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Customer.io account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Customer.io's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Customer.io?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Customer.io account it signs in with. Revoking access is one click in Customer.io.

More on the Customer.io connector

Customer.io connector for claude.ai Braze + Claude Code Iterable + Claude Code Brevo + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us