Customer.io

View saved version →

---
name: customerio
description: >
  Customer.io MCP bootstrap. Use for Customer.io, Journeys, CDP Pipelines,
  Design Studio, sandbox testing, app integration, SDK setup, transactional
  messaging, sources, destinations, identify/track events, and Customer.io
  workspace errors.
---

# Customer.io

Use the official Customer.io MCP server bundled with this plugin, then drive the workspace with its live tools and hosted skills.

## Connect

1. Confirm the `customerio` MCP server is enabled and complete Customer.io OAuth.
2. Select the workspaces and minimum permission scopes needed for the task.
3. The plugin uses the Universal `mcp.customer.io` entry point for both US and EU accounts. OAuth identifies the selected account's data center, and Customer.io routes EU requests to `mcp-eu.customer.io`; do not ask the user to choose a region manually.
4. Do not paste personal MCP URLs, API keys, or service-account tokens into plugin files.

## First calls

Call `cio_prime` before other Customer.io tools. It returns the current rules for schema lookup, pagination, dry-run writes, and hosted skill discovery.

Then use:

- `cio_auth_status` when authentication or workspace access is unclear.
- `cio_schema` to discover endpoints. Never guess paths or field names.
- `cio_skills_list` and `cio_skills_read` for task-specific workflows.
- `cio_read_api` for GET requests.
- `cio_write_api` and `cio_delete_api` with `dry_run: true` before execution.

## Route to live skills

| Need | Read with `cio_skills_read` |
| --- | --- |
| Builder, SDK, sandbox, first send, go-live | `cio` |
| Automations, campaigns, broadcasts, profiles, segments, messaging | `fly-api` |
| Design Studio emails, components, global styles, publishing | `design-studio` |
| CDP sources, destinations, reverse ETL, identify/track | `cdp-api` |
| Analysis, campaign review, goals, Liquid | `recipes` |

Prefer the hosted skills over copied playbooks so instructions stay current with Customer.io.

## Terminology and safety

- Automations are the `campaigns` API resource.
- Profiles are the `customers` API resource.
- Dry-run every write and delete before executing it.
- Do not embed service-account tokens (`sa_live_...`) in application code.
- Use CDP source write keys for SDK identify/track/page/screen calls.
- Use workspace-scoped App API keys for backend transactional sends.
- Do not return raw customer PII unless the user explicitly requests it.

View saved version →

---
name: customerio-design-studio
description: >
  Customer.io Design Studio. Use to create, edit, review, or publish emails,
  components, global styles, connected emails, or email accessibility and QA.
---

# Customer.io Design Studio

1. Confirm the `customerio` MCP server is connected.
2. Call `cio_prime`.
3. Read `design-studio` with `cio_skills_read`, then the relevant subfile such as `design-studio/nodes.md`, `design-studio/email_review.md`, or `design-studio/journeys.md`.
4. Discover endpoints with `cio_schema`.
5. Read with `cio_read_api`. Mutate with `cio_write_api` and `dry_run: true` first.

Wiring a finished email into an automation, broadcast, or transactional message uses Journeys. Audience and send logic belongs in `customerio-journeys`.

View saved version →

---
name: customerio-journeys
description: >
  Customer.io Journeys. Use to create, list, edit, or review automations,
  campaigns, broadcasts, profiles, people, segments, newsletters,
  transactional messages, and in-app messages.
---

# Customer.io Journeys

1. Confirm the `customerio` MCP server is connected.
2. Call `cio_prime`.
3. Read `fly-api` with `cio_skills_read`, then the relevant subfile. Common routes include `fly-api/automations.md`, `fly-api/customers.md`, `fly-api/segments.md`, `fly-api/messaging.md`, `fly-api/transactional_send.md`, and `fly-api/in_app.md`.
4. Discover the endpoint with `cio_schema`.
5. Read with `cio_read_api`. Mutate with `cio_write_api` or `cio_delete_api`, always using `dry_run: true` first.

Use `customerio-design-studio` for email content and `customerio-pipelines` for sources and destinations.

View saved version →

---
name: customerio-pipelines
description: >
  Customer.io Data Pipelines. Use to add or inspect sources, destinations,
  reverse ETL, database syncs, identify/track/page/screen calls, and data-in or
  data-out integrations.
---

# Customer.io Pipelines

1. Confirm the `customerio` MCP server is connected.
2. Call `cio_prime`.
3. Read `cdp-api` with `cio_skills_read`, then the relevant subfile such as `cdp-api/sources.md`, `cdp-api/destinations.md`, `cdp-api/reverse_etl.md`, or `cdp-api/journeys_integrations.md`.
4. Prefer a native Pipelines source for ongoing data ingestion.
5. Discover endpoints with `cio_schema`. Mutate with `dry_run: true` first.

Use `customerio-journeys` for automations, profiles, and segments. Use `customerio-sdk` for application SDK installation.

View saved version →

---
name: customerio-sdk
description: >
  Customer.io SDK and app integration. Use to install or troubleshoot
  JavaScript, Node, iOS, Android, React Native, Expo, or Flutter SDKs, sandbox
  testing, first sends, Live Activities, or going live.
---

# Customer.io SDK

1. Confirm the `customerio` MCP server is connected.
2. Call `cio_prime`.
3. Read `cio` with `cio_skills_read`, then the matching subfile such as `cio/sdk_setup.md`, `cio/integration.md`, `cio/integration_web.md`, `cio/integration_mobile.md`, `cio/integration_backend.md`, `cio/sdk_troubleshooting.md`, `cio/sandbox.md`, or `cio/go-live.md`.
4. For Pipelines source settings and write keys, also read `cdp-api/sources.md`.
5. Do not put service-account tokens in application code. Use source write keys for behavioral data and App API keys for backend transactional sends.