Skip to main content
Watch: I Built an AI App Without Leaving Databricks

Communication - official Customer.io server

Customer.io MCP server

Hosted MCP server that gives AI tools access to the Customer.io Journeys UI API and CDP Data Pipelines API, split into read, write and delete tools plus schema discovery and Customer.io-maintained skills. Users authenticate with OAuth and pick workspaces and permission scopes. Customer.io hosts it at https://mcp.customer.io/mcp with OAuth auth.

Last verified 8 tools6 sources

Install

Claude Code

About Claude Code
Snippet
/plugin marketplace add customerio/claude-plugin
/plugin install customerio@customerio

Generic

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

Tools

cio_prime
Loads the AI-ready reference for the Customer.io API; call at the start of a task.
cio_schema
Discovers API endpoints: list resources, find endpoints, and inspect parameters.
cio_read_api
Makes authenticated GET requests for listing, reading and inspecting resources.
cio_write_api
Makes authenticated POST, PUT and PATCH requests for creating and editing resources, with dry-run previews.
cio_delete_api
Makes authenticated DELETE requests for removing resources, with dry-run previews.
cio_skills_list
Lists available agent skills for multi-step operations like creating automations.
cio_skills_read
Reads the full content of a specific skill so the AI tool can follow step-by-step workflows.
cio_auth_status
Shows the current authentication state, including which workspaces the token can access.

As documented on October 17, 2026. A running server reports its current list through tools/list.

Notes and caveats

  • An account admin must turn on Customer.io MCP under Settings > AI.
  • Region endpoints: US https://mcp.customer.io/mcp, EU https://mcp-eu.customer.io/mcp (the plugins use the US entry point and route by account region after OAuth).
  • SSE transport is not supported.
  • OAuth scopes: read (default), read:sensitive, write, write:live and configure; editing live data and reading sensitive attributes each require an admin setting.
  • Recommended installs are first-party plugins: Claude Code/Cowork (customerio/claude-plugin, MIT; directory listing awaiting Anthropic review as of the docs), ChatGPT and Codex (installed from the Plugins UI, repo customerio/openai-plugin, MIT), and Cursor (Cursor Marketplace plugin, no config snippet).
  • The generic JSON is documented for Windsurf, VS Code and other MCP-capable IDEs.
  • The server itself has no public repository.
  • Customer.io first launched the server as early access; current docs carry no status label.
  • Docs suggest the Customer.io CLI may suit terminal-based agents better.

More MCP servers for communication

Related reading

FAQ

What does the Customer.io MCP server do?

Hosted MCP server that gives AI tools access to the Customer.io Journeys UI API and CDP Data Pipelines API, split into read, write and delete tools plus schema discovery and Customer.io-maintained skills. Users authenticate with OAuth and pick workspaces and permission scopes. The vendor documents 8 tools, including cio_prime, cio_schema, cio_read_api and cio_write_api.

How do I add the Customer.io MCP server to Claude Code?

Customer.io documents a Claude Code config; copy it from the Claude Code section of this page. Snippets for Generic are there too.

Does the Customer.io MCP server need authentication?

Yes, OAuth. Transport: Streamable HTTP. Status: Unlabelled, last checked October 17, 2026.

Sources

Last verified against 6 Customer.io pages, then re-checked independently.

Newsletter

New MCP servers, the week they ship

One email per week. New official MCP servers, the coding tools that support them and how developers wire them up.