Gamut
Customer.io logo
Analytics & MarketingAuth: OAuth

Customer.io MCP Server

Connect Customer.io to your AI agents with the Customer.io MCP server.

Updated

Use Customer.io on Gamut

What is Customer.io MCP?

The Customer.io MCP server is a Model Context Protocol server that connects Customer.io to AI agents and assistants as a set of tools. With it connected, an agent can work with Customer.io (customer engagement — messaging campaigns, journeys, segments, and broadcasts) directly — instead of you copying data in and out by hand.

It is a remote MCP server that uses OAuth, so you point your client at the server URL, authorize once, and the Customer.io tools become available to the model.

Connect the Customer.io MCP server

Connect Customer.io MCP to Claude Code

  1. 1

    Add the server

    Use `claude mcp add` with the Customer.io MCP server URL (or its `npx` command), following the official docs.

  2. 2

    Authorize

    Complete authentication (OAuth) so Claude Code can call the server.

  3. 3

    Verify

    Ask Claude to use a Customer.io tool to confirm the connection is live.

Connect Customer.io MCP to Cursor

  1. 1

    Open MCP settings

    In Cursor, go to Settings → MCP → Add new server.

  2. 2

    Add Customer.io

    Provide the Customer.io MCP server URL or command and complete authentication.

  3. 3

    Test

    Reference Customer.io from chat to confirm Cursor can reach the tools.

Sample use cases

Using Customer.io MCP with Gamut

On Gamut, the Customer.io MCP server becomes a tool your agents use inside an automated, event-driven workflow — triggered by an event or a schedule, acting through Customer.io and your other connected MCP servers, with the connection managed by Gamut rather than a local config file.

Frequently asked questions

What Customer.io data can an agent access via MCP?

The integration lets an agent interact with Customer.io's messaging and data platform — including campaigns, segments, customer profiles, events, and delivery metrics. Exact capabilities depend on the MCP server implementation and your Customer.io plan.

Can the agent send messages through Customer.io?

Write capabilities depend on the MCP server's tool set. Some implementations support triggering campaigns or sending transactional messages; others are read-only for analytics and debugging. Check the server documentation for supported operations.

Does the integration work with Customer.io Journeys and Data Pipelines?

The MCP server typically connects via Customer.io's REST API, which covers both the Journeys (messaging) and Data Pipelines (CDP) products. Feature availability depends on your Customer.io plan tier and which API endpoints the server exposes.

Is customer PII exposed to the agent?

The agent can access whatever your Customer.io API key permits — which may include email addresses, names, and custom attributes. Use a restricted API key with minimal scopes and follow your organization's data handling policies.