---
title: "Customer.io MCP integration | Growf"
description: "Work with Customer.io people, campaigns, broadcasts, and workspace configuration. Connect Customer.io MCP to Growf."
url: "https://www.growf.io/integrations/customerio_mcp/"
language: "en"
---

Integration / CRM

![Customer.io MCP logo](https://logos.composio.dev/api/customerio_mcp)

# Customer.io MCP integration

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

[Get a demo](https://www.growf.io/demo/)

About Customer.io MCP

## Customer.io MCP is a behavioral messaging platform for managing people, campaigns, broadcasts, and workspace configuration. Use it to automate targeted lifecycle messaging, personalize communications, and orchestrate campaigns at scale.

[All integrations](https://www.growf.io/integrations/)

Category

CRM, Collaboration & Communication, Developer Tools & DevOps

Connection

OAuth

Type

Tool

Actions

362

Tags

library

Example prompts

## What you can ask Growf to do with Customer.io MCP

- “Add user to onboarding campaign now”

- “Create broadcast for new feature announcement”

- “Update person attributes and trigger campaign”

Available actions

## 362 actions your agents can run in Customer.io MCP

- 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 auth errors.
- 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 name ('campaigns') to list its endpoints; pass 'resource.method' ('campaigns.list')…
- 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.

## Put Customer.io MCP to work inside Growf.

Connect it once and every workspace, agent and workflow can use it — securely, with your team in the loop.

[Get a demo](https://www.growf.io/demo/)