Full read-write Claude connector for Customer.io
Let Claude build segments and stage broadcasts in Customer.io
Stop bouncing between the Customer.io dashboard and spreadsheets to shape audiences and draft messages. Claude builds the segment, updates people and their attributes, and stages the broadcast where the work already lives, and only triggers a send once you approve.
Customer.io is a messaging automation platform teams use to run behavior-triggered email, push, SMS, and in-app campaigns. People want Claude to do more than read campaign metrics: to build segments, draft and stage broadcasts, and update people and their attributes where the work already lives.
What is a Customer.io MCP server?
A Customer.io MCP server is a small hosted service that exposes Customer.io's data and actions to Claude over the Model Context Protocol, so Claude can campaigns, lists, and audiences inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.
What can Customer.io's current connector do today?
There is an official Customer.io connector for Claude, and it covers a fixed, generic slice of the platform with a standard tool set. What it does not do is fit your team's exact segments, attributes, broadcast staging, and approval flow. A custom connector wraps the Track and App APIs so Claude reads and, with your confirmation, writes the specific actions your workflow needs.
What does full read-write Customer.io access unlock?
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
Can Claude build and update segments in Customer.io?
Yes, for manual segments. The App API lets Claude create or update a manual segment and add or remove the specific people you name, using your scoped credentials. Condition or filter based segments stay defined in the dashboard, so Claude resolves your rules to a person list it then pushes into a manual segment you approve.
Can Claude update people and their attributes in Customer.io?
Claude can identify or update a person and their attributes through the Track API, so the profile changes you used to make by hand happen in conversation. Reads and writes are kept as separate tools, and the connector only touches the people and attribute endpoints your provisioned credentials allow.
Will Claude trigger a Customer.io broadcast without my approval?
No. Claude can draft email, push, or in-app variants and stage them in a broadcast, but triggering an API-driven send is a separate, gated action that runs only after you confirm. Drafting and audience work flow freely while every outbound send waits for a human before anything reaches a recipient.
How a Customer.io connector works
We build a small MCP server that authenticates to Customer.io with scoped App and Track API credentials restricted to the endpoints the work needs. Read tools (segments, people, campaign metrics) and write tools (update person, stage broadcast, trigger send) are kept separate, and outbound or destructive actions like sending and deleting require your confirmation. Claude never has more access than the credentials you provision, and we can lock the server to allowlisted IPs against your workspace and region.
Frequently asked questions
Can Claude build and update Customer.io manual segments, not just read reports?
Will Claude send a Customer.io broadcast without my approval?
Does the Customer.io connector get more access than my API credentials allow?
Related connectors
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.