---
title: Customer.io MCP Server for Claude and ChatGPT | SourceMedium
description: "Customer.io MCP at mcp.customer.io uses OAuth scopes: read by default, with separate grants for PII, draft edits, live sends, and workspace settings."
url: "https://sourcemedium.com/mcp-directory/customer-io/"
type: static
generatedAt: "2026-09-29T01:21:01.000Z"
---

[MCP Directory](https://sourcemedium.com/mcp-directory/) Email and SMS Official
# 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.

| Option | Audience | Reads or changes | Sign-in | Setup |
| --- | --- | --- | --- | --- |
| Customer.io MCP `https://mcp.customer.io/mcp` Customer.io | Merchants | Covers the Journeys UI API and CDP Data Pipelines API: reads automations, segments, people, content, and delivery metrics by default, and with extra scopes creates or edits drafts, sends messages, manages subscriptions, and changes workspace settings. Can write | OAuth sign-in | [Setup guide →](https://docs.customer.io/ai/mcp/get-started/) |

## 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 →](https://docs.customer.io/ai/mcp/get-started/)
Guide covers ChatGPT, Codex, Gemini CLI

### Connect Customer.io to Claude

- [Customer.io MCP →](https://docs.customer.io/ai/mcp/get-started/) [Add from Claude's connector directory](https://claude.com/marketplace/connectors/customer-io)
Claude Code

```
claude mcp add --transport http customer-io https://mcp.customer.io/mcp
```

### Connect Customer.io to Cursor

- [Customer.io MCP →](https://docs.customer.io/ai/mcp/get-started/)
.cursor/mcp.json

```
{"mcpServers":{"customer-io":{"url":"https://mcp.customer.io/mcp"}}}
```

### Connect Customer.io to VS Code

- [Customer.io MCP →](https://docs.customer.io/ai/mcp/get-started/)
.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

- [Customer.io APIs overview →](https://docs.customer.io/integrations/api/customerio-apis/)
- [Customer.io CLI for AI agents →](https://docs.customer.io/ai/cli/get-started/)

## 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.
## More in Email and SMS

- [Iterable MCP server →](https://sourcemedium.com/mcp-directory/iterable/)
- [Klaviyo MCP server →](https://sourcemedium.com/mcp-directory/klaviyo/)
- [Mailchimp MCP server →](https://sourcemedium.com/mcp-directory/mailchimp/)