Connect Customer.io MCP to your AI agent

CRM 8 actions available

Work with Customer.io people, campaigns, broadcasts, and workspace configuration.

We set up the connection using your own Customer.io MCP account, with keys you control, and keep it running. Your agent picks it up and starts doing the work.

Book a setup call → See pricing
Actions

What your agent can do in Customer.io MCP

Each one is a real action the agent can take on its own, the same things a person clicking around Customer.io MCP could do. Read-only by default; write actions are confirmed against your policy.

  • Cio auth status Show the active authentication state. Reports the authenticated user and account, the workspaces the current OAuth token is allowed to access, and whether an agent service-account JWT can be minted. Use this to diagnose…
  • Cio delete api Delete a resource via the Customer.io API (DELETE only). Always run with dry_run first to preview. Use cio_schema to find the correct path.
  • Cio prime Print LLM-ready instructions for using the Customer.io API. ALWAYS call this first in a new task — it contains the authoritative, version-specific rules for how to drive the API via the other cio_* tools.
  • Cio read api Read from the Customer.io API (GET only). Use cio_schema first to find the correct path and placeholders. Workspace routing is enforced server-side via the caller's OAuth token.
  • Cio schema Introspect the Customer.io API schema. Use this to discover endpoints before calling cio_read_api / cio_write_api / cio_delete_api — never guess paths or field names. Pass no query to list resources; pass a resource nam…
  • Cio skills list List available agent skills — task-specific instruction manuals maintained by Customer.io (routing rules, required params, multi-step workflows).
  • Cio skills read Read the full content of a specific agent skill. Paths look like 'campaigns' for the main skill or 'campaigns/examples.md' for a sub-file — see cio_skills_list for available paths.
  • Cio write api Write to the Customer.io API (POST, PUT, or PATCH). Always run with dry_run first to preview. Use cio_schema to find the correct path, method, and body shape.
Setup

How we connect it

  1. 1

    Connect your account

    You log in with your own Customer.io MCP account. We never see your password, and you can revoke access from Customer.io MCP at any time.

  2. 2

    Set the guardrails

    Read-only by default. You choose which write actions the agent may take, and anything outside that policy gets confirmed with you first.

  3. 3

    We keep it running

    Health checks on every connection, updates handled for you, and we watch the first week of activity to make sure the work lands.

FAQ

Customer.io MCP questions, answered.

You sign in with your own Customer.io MCP account. Permissions are scoped to the minimum the agent needs, the connection is health-checked, and you can revoke access from Customer.io MCP at any time.
The actions Customer.io MCP's API allows, the same things a person clicking around the app could do. Connections start read-only by default; write actions are confirmed against the policy you set before the agent takes them.
Connections are priced per tool on top of the base plan. Some are included, some are premium. See pricing for how connection charges work.
Standard tools are ready inside 7 business days of the setup call. We test the connection end to end, walk you through how the agent uses it, and watch the first week of activity.

Ready to put Customer.io MCP to work?

Tell us what your team runs on. We set up the connection, secure it, and your agent takes it from there.

Book a setup call → Browse all connections

All product names, logos, and brands are property of their respective owners; used for identification only. ZeroToClaw is not affiliated with or endorsed by Customer.io MCP.