Customer.io MCP server
Remote endpoint mcp.customer.io/mcp. Checked September 2026.
Scopes decide what Customer.io's server may do. The default grant reads automations, segments, people, content, and delivery metrics across email, SMS, push, and in-app, through the Journeys UI API and the CDP Data Pipelines API; separate grants add PII, draft edits, live sends, subscription management, and workspace settings.
Customer.io MCP options
Every fact in a row comes from the publisher's own documentation.
Connect Customer.io to your assistant
Each card lists the servers whose setup guide covers that assistant.
Connect Customer.io to ChatGPT, Codex, or Gemini
- Customer.io MCP (opens in a new tab)
Guide covers ChatGPT, Codex, Gemini CLI
Connect Customer.io to Claude
- Customer.io MCP (opens in a new tab) Add from Claude's connector directory (opens in a new tab)
Claude Code
claude mcp add --transport http customer-io https://mcp.customer.io/mcp
Connect Customer.io to Cursor
- Customer.io MCP (opens in a new tab)
.cursor/mcp.json
{"mcpServers":{"customer-io":{"url":"https://mcp.customer.io/mcp"}}}
Connect Customer.io to VS Code
- Customer.io MCP (opens in a new tab)
.vscode/mcp.json
{"servers":{"customer-io":{"type":"http","url":"https://mcp.customer.io/mcp"}}}
Customer.io's setup guides also name Windsurf.
Other ways to reach Customer.io data
One MCP server per tool still can't answer a cross-channel question.
Each server brings its own sign-in, its own definition of revenue, and data your assistant can't join to the rest.
SourceMedium connects 63 commerce and marketing sources, keeps one set of maintained definitions, and gives ChatGPT, Claude, and other assistants a single connection to all of it. Customer.io is not a SourceMedium source today.