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": ["-y", "<server-package-name>"],
"env": {
"CUSTOMER_IO_API_KEY": "your-api-key-here"
}
}
}
}
// Server source: https://github.com/ShadowWalker2014/openmail
// Check the server's README for the exact "command" and required env vars.Some MCP servers require an API key. Check the source page for setup: github.com/ShadowWalker2014/openmail.
Does Customer.io MCP cost extra?
The Customer.io MCP server is community-built — free to run, but you still pay for your Customer.io subscription.
- Community MCPs are normally self-hosted from a GitHub repo. There's no extra license fee.
- Your Customer.io account still needs whatever plan is required to access the data the MCP server queries.
- Trade-off: zero MCP cost, but no guarantee it'll keep working when Customer.io changes their UI or API.
Customer.io subscription pricing
| Plan | Monthly | Annual / mo |
|---|---|---|
| Essentials | $100 | — |
| Premium | — | $1,000 |
| Enterprise | Contact sales | — |
Source: customer.io/pricing. Verified 2026-05-31.
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
- Community MCP — not maintained by Customer.io. Check the README and last-update date before depending on it.
- 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
Moderate agent fit with community MCP support. Customer.io has a documented public API and native Claude integration through a community MCP server, but lacks official MCP hosting, OpenAPI specs, and structured output support. The missing OpenAPI spec means agents can't auto-discover endpoints, requiring manual integration work.
Scored 2026-05-31 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?+
Which LLMs does Customer.io integrate with directly?+
Sources
- Customer.io official site: https://customer.io
- MCP server page: https://github.com/ShadowWalker2014/openmail
- API docs: https://docs.customer.io/api/
- Pricing source: https://customer.io/pricing (verified 2026-05-31)
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.

