# Customer Io (npm · @pipeworx/mcp-customer-io)

MCP server for customer-io

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 80/100, [markdown](https://verifymcp.io/servers/pipeworx-io-customer-io/customer-io-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-customer-io/customer-io-mcp)
- npm · `@pipeworx/mcp-customer-io`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-customer-io/pipeworx-mcp-customer-io.md), [page](https://verifymcp.io/servers/pipeworx-io-customer-io/pipeworx-mcp-customer-io)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-customer-io`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-customer-io).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 510 tokens (~127/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 81% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Customer Io MCP server?

Customer Io runs locally as an npm package, launched with npx -y @pipeworx/mcp-customer-io. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-customer-io -- npx -y @pipeworx/mcp-customer-io
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-customer-io": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-customer-io"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-customer-io": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-customer-io"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-customer-io -- npx -y @pipeworx/mcp-customer-io
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-customer-io": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-customer-io"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-customer-io --command npx --arg -y --arg @pipeworx/mcp-customer-io
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-customer-io:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-customer-io"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-customer-io": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-customer-io"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-customer-io -t stdio -c npx -a -y @pipeworx/mcp-customer-io
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-customer-io": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-customer-io"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 81, +26)

- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-10-31 (score 55, −25)

- [security regression] Known CVEs: pass → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (4)

### `cio_list_campaigns` (~76 tokens)

Return Customer.io lifecycle campaigns with IDs, names, state, trigger configuration, actions, tags, and timestamps. Answers which automations exist and whether they are running, drafted, or stopped.

Input parameters:

- `_apiKey` (string, required): Customer.io App API key
- `_region` (string): Workspace region; defaults to us

### `cio_campaign_metrics` (~144 tokens)

Return time-bucketed Customer.io delivery, bounce, open, click, unsubscribe, and conversion metrics for one campaign. Answers how a lifecycle campaign performed and when engagement changed.

Input parameters:

- `_apiKey` (string, required): Customer.io App API key
- `_region` (string): Workspace region; defaults to us
- `campaign_id` (number, required): Customer.io campaign ID
- `end` (number): End as Unix seconds
- `message_type` (string)
- `resolution` (string): Metric bucket; defaults to daily
- `start` (number): Start as Unix seconds
- `timezone` (string): IANA timezone such as America/Los_Angeles

### `cio_list_segments` (~72 tokens)

Return Customer.io audience segments with IDs, names, descriptions, dynamic or manual type, build progress, tags, and timestamps. Answers which audiences are available for targeting or analysis.

Input parameters:

- `_apiKey` (string, required): Customer.io App API key
- `_region` (string): Workspace region; defaults to us

### `cio_list_messages` (~163 tokens)

Return a bounded page of Customer.io message deliveries with recipients, channel, campaign or newsletter parent, and delivery engagement timestamps. Answers which messages reached, bounced, opened, clicked, converted, or unsubscribed recipients.

Input parameters:

- `_apiKey` (string, required): Customer.io App API key
- `_region` (string): Workspace region; defaults to us
- `campaign_id` (number)
- `end_ts` (number): Delivery creation range end as Unix seconds
- `limit` (number): Maximum deliveries, default 50 and maximum 100
- `message_type` (string)
- `metric` (string)
- `start` (string): Cursor from the previous response next field
- `start_ts` (number): Delivery creation range start as Unix seconds

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-customer-io/pipeworx-mcp-customer-io#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 55
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the Customer Io MCP server?

Customer Io is an MCP server listed in the public MCP registry as io.github.pipeworx-io/customer-io. MCP server for customer-io. This page covers its npm package (@pipeworx/mcp-customer-io).

### Is the Customer Io MCP server safe to use?

Customer Io scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Customer Io MCP server expose?

Customer Io exposes 4 tools: cio_list_campaigns, cio_campaign_metrics, cio_list_segments, cio_list_messages. Their descriptions and schemas cost roughly 455 tokens of context every time the server is loaded.

### Is the Customer Io MCP server still maintained?

Customer Io is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Customer Io MCP server under?

Customer Io declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-customer-io
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-customer-io
- Repository: https://github.com/pipeworx-io/mcp-customer-io
- Website: https://pipeworx.io/packs/customer-io
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-customer-io/pipeworx-mcp-customer-io.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-customer-io/pipeworx-mcp-customer-io.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-customer-io/pipeworx-mcp-customer-io