Access, auth, and limits
Auth is OAuth with your Customer.io account, and no API keys are involved. The protected-resource metadata advertises five scopes: configure, read, read:sensitive, write and write:live. That separation is the point. read:sensitive is distinct from read, so profile-level PII is a separate grant, and write:live is distinct from write, so an agent can build a campaign without being able to send it to real people.
Pick the endpoint that matches where your workspace data lives: mcp.customer.io for US, mcp-eu.customer.io for EU. Customer.io does not publish plan requirements for MCP access on the get-started page, so tier gating is the one thing to confirm against your own account.
Where it works and what to build
Customer.io documents setup for ChatGPT, Claude and Cursor, and the server is remote HTTP so any MCP-capable client can hold the connection. It also ships a CLI alongside the server for agents that would rather shell out than speak MCP.
The workflow this unlocks is auditing rather than authoring. Ask which segments overlap, which campaigns have not sent in ninety days, or which journeys branch on an attribute nobody sets any more, and the agent walks the API and answers. Doing that by hand means clicking through the Journeys UI segment by segment. Grant read and read:sensitive for that work and withhold write:live, and the blast radius of a misunderstood prompt stays at zero.
Which AI clients can use Customer.io MCP?
Not every AI assistant supports MCP natively. Per-client picture for Customer.io:
| Client | Support | Notes |
|---|---|---|
| ChatGPT | Native MCP | — |
| Claude (Desktop/Web) | Native MCP | — |
| Cursor | Native MCP | — |
How to connect Customer.io MCP to Claude Desktop
Add this block to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows), then restart Claude Desktop. Cursor and Codex use a similar schema.
{
"mcpServers": {
"customer-io": {
"command": "npx",
"args": ["mcp-remote", "<YOUR_MCP_URL>"]
}
}
}
// HTTP-transport MCP. Get your <YOUR_MCP_URL> from the vendor dashboard.
// Server source: https://mcp.customer.io/mcp
// Claude Code (one-liner): claude mcp add customer-io <YOUR_MCP_URL> --transport httpSome MCP servers require an API key. Check the source page for setup: mcp.customer.io/mcp.
Does Customer.io MCP cost extra?
Customer.io ships an official MCP server that uses your existing subscription credentials.
- No separate MCP licence to buy. You pay for your Customer.io plan, the MCP server queries that account.
- Whether it's gated to a specific tier wasn't extracted automatically — verify the access requirements on the MCP page or pricing docs.
Customer.io also publishes a REST API
Customer.io publishes an API, but per-tier gating wasn't extracted automatically.
See Customer.io API pageWhat you can do with Customer.io from an AI agent
Three shapes of agent workflow. Pick the row that matches how you actually use Claude / Cursor / Codex day to day.
Skip the dashboard, ask Claude
- "What campaigns underperformed this week?" answered in seconds
- Quick one-off questions without leaving the editor
- Pipe Customer.io data into your personal notes / docs without writing a script
Run client analysis at agent speed
- Hand the MCP server to your team — every consultant can ask Claude about any client's Customer.io account
- Multi-account workflows without context-switching the Customer.io UI
- Reports you'd normally spend hours on, done before standup
Production agent workflows
- Embed in your internal Codex / Cursor agents that triage Customer.io data daily
- Combine with other MCP servers in a multi-step agent chain
- Constrain agents to read-only roles to keep production Customer.io safe
Limits and gotchas
- Official MCP server — published by Customer.io themselves, so it should track product changes.
- Fallback: the REST API works for any flow the MCP server doesn't cover.
- Rate limits: MCP calls count against your underlying Customer.io API quota. Burst usage from a curious agent can drain a daily allowance fast.
Agent-readiness verdict
The most carefully permissioned MCP server in the email and CDP category. Region-split endpoints and five separate OAuth scopes mean you can hand an agent read access to production without also handing it send access.
Moderate agent potential with community MCP support. Customer.io has a public API with documentation and native Claude integration through a community MCP server, but lacks official MCP hosting, OpenAPI specs, and structured outputs that would make it more accessible to agent workflows.
Scored by Joonas (TMB).
Customer.io MCP & API FAQ
Is the Customer.io MCP server official?+
Can I use the Customer.io MCP with Cursor or Codex?+
Does Customer.io have a public API?+
Sources
- Customer.io official site: https://customer.io
- MCP server page: https://mcp.customer.io/mcp
- API docs: https://docs.customer.io/api/
Data verified by Joonas on the dates shown. MCP server status auto-rechecked weekly.
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.