Is this an official Customer.io MCP server?

No. It is Memtro's MCP server with Memtro's Customer.io connector behind it: the connector reads Customer.io through its API with the credentials you connect on Dashboard → Connections, and Customer.io publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Customer.io?

Not yet. Today every Customer.io tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · Marketing automation

Customer.io MCP server

Customer.io in any MCP client, through Memtro: Customer.io does not publish this server. Memtro's Customer.io connector reads Customer.io through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Read-only messaging automation: campaigns, newsletters and broadcasts with delivery/open/click/conversion metrics, segments with counts, and customer profiles with attributes, segments, activity and messages.

Reads

customerio_campaignsCustomer.io campaigns (automations): trigger type, state, channels, segments and dates…
customerio_sendsNewsletters (one-time sends, newest first) or API-triggered broadcasts, optionally with metric totals.
customerio_metricsMetrics for one campaign, newsletter or broadcast over the last N periods (hours/days/weeks/months): totals plus a per-period series for sent…
customerio_segmentsSegments (dynamic and manual) with descriptions, build state and, by default, the current number of people in each (first 25).
customerio_customerLook up people by email (all profiles sharing it, up to 3 detailed) or one person by id/cio_id: attributes, unsubscribe status, devices…
customerio_customer_activityRecent activity for one person (events, page views, attribute changes, message sends/opens/clicks…

Connect it

First connect Customer.io on Dashboard → Connections, then add Memtro to your client once. The Customer.io tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

One command registers the server; the tools are then available in every session.

claude mcp add --transport http memtro https://platform.memtro.com/api/mcp \
  --header "Authorization: Bearer sk-memtro-..."

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Customer.io connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› How did the onboarding campaign perform over the last 14 days?
› Which segments is sam@fable.dev in and what did we send them?
› How many people are in the Trial expiring soon segment?
› Which newsletters went out this month and what were their open rates?

Questions

Is this an official Customer.io MCP server?: No. It is Memtro's MCP server with Memtro's Customer.io connector behind it: the connector reads Customer.io through its API with the credentials you connect on Dashboard → Connections, and Customer.io publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Customer.io?: Not yet. Today every Customer.io tool reads, searches or lists; when it gains actions, each is marked, granted by name and used only when you ask, so nothing is created, sent, updated or deleted until you say so.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.