Customer.io MCP for AI agents
Agents read Customer.io MCP at once. Changes and sends are held for a person's approval by default.
About Customer.io MCP
Work with Customer.io people, campaigns, broadcasts, and workspace configuration.
What an agent can do in Customer.io MCP
Every Customer.io MCP action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in Customer.io MCP without asking first. 6 actions.
- Cio auth statusShow 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. U
- Cio primePrint 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_* to
- Cio read apiRead 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 schemaIntrospect 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;
- Cio skills listList available agent skills — task-specific instruction manuals maintained by Customer.io (routing rules, required params, multi-step workflows).
- Cio skills readRead 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.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 2 actions.
- Cio delete apiDelete 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 write apiWrite 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.
Changes wait in Needs you
Changes and sends in Customer.io MCP are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Related connectors
Customer.io MCP questions
Can an agent change data in Customer.io MCP on its own?
Not by default. Changes and sends in Customer.io MCP are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in Customer.io MCP?
This connector lists 6 read actions. Reads run at once, without waiting for approval.
How does Customer.io MCP connect?
It connects with dcr oauth. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.