Customer.io MCP Server for Claude

Overview

The Customer.io MCP Server is the official Model Context Protocol server from Customer.io. It gives Claude direct access to your Customer.io workspace — segments, customer profiles, campaigns, broadcasts, journeys, and the full Journeys UI and CDP Data Pipelines APIs — through natural language. Authentication is via OAuth with your Customer.io account; no API keys are required.

The server exposes three tool categories — read, write, and delete — so you can approve each category independently. By default, editing or deleting active campaigns and segments is restricted to prevent accidental audience changes.

Key capabilities

• Customer segments — create and manage segments using customer attributes and behavioral data.
• Customer profiles — inspect individual profiles, event history, and engagement patterns.
• Campaigns & broadcasts — create and send targeted broadcasts with personalization data.
• Journeys — build and manage multi-step messaging journeys.
• Full API access — the Journeys UI API and CDP Data Pipelines API are exposed via three tool categories: cio_read_api (GET), cio_write_api (POST/PUT/PATCH), and cio_delete_api (DELETE).
• Delivery metrics — retrieve real-time delivery and engagement metrics.

How it compares

Customer.io's MCP is notable for exposing the full API surface (read + write + delete) with explicit per-category permission controls, making it suitable for both analyst (read-only) and operator (full access) workflows.

Installation

Claude Code (OAuth)

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

Run /mcp in Claude Code to authenticate via OAuth with your Customer.io account.

Claude Desktop

Go to Settings → Connectors and add the Customer.io MCP connection, or manually add the server:

{
  "mcpServers": {
    "customerio": {
      "type": "http",
      "url": "https://mcp.customer.io/mcp"
    }
  }
}

EU region

Use https://mcp-eu.customer.io/mcp instead of the US endpoint.

Requirements

• A Customer.io account.
• A paid Claude plan (MCP is not available on Claude's free tier).
• An MCP client (Claude Code or Claude Desktop).

Security

• OAuth authentication — no API keys to manage or rotate.
• Approve read, write, and delete tool categories independently.
• Default restrictions prevent deleting profiles and editing live active campaigns.

Source Verification Notes

Verified on 2026-06-18:

• Customer.io's MCP getting-started guide at docs.customer.io/ai/mcp/get-started/ confirms the US and EU endpoints, OAuth auth, three API tool categories, and the default restrictions on editing live data.
• Customer.io's MCP integration page confirms full Journeys UI API + CDP Data Pipelines API access and the three-tool architecture.
• Customer.io's Claude setup guide at docs.customer.io/ai/mcp/claude/ documents the HTTP transport and Claude Code installation pattern.
• Claude Code's MCP documentation describes the --transport http installation pattern used above.