Work with Customer.io people, campaigns, broadcasts, and workspace configuration.
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.
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.
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.
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.
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'), 'METHOD /path', or '/path' for endpoint detail.
List available agent skills — task-specific instruction manuals maintained by Customer.io (routing rules, required params, multi-step workflows).
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.
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.
The Customer.io MCP integration connects your Dench AI CRM directly to Customer.io MCP, so agents can read and act on your Customer.io MCP data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
8 actions are available for agents to invoke on your behalf. Every call runs through Customer.io MCP's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Customer.io MCP and click Connect — you'll authorize access through Customer.io MCP's own sign-in flow. No API keys or code required.
Ask an agent to use Customer.io MCP in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Customer.io MCP integration connects your AI CRM to Customer.io MCP, so AI agents can work with your Customer.io MCP data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Customer.io MCP integration currently exposes 8 actions, including Cio auth status, Cio delete api, Cio prime, Cio read api, Cio schema, and Cio skills list. Agents invoke them on your behalf from chat or from automations.
No. You connect Customer.io MCP from your Dench workspace using Customer.io MCP's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Customer.io MCP's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Customer.io MCP connection from your workspace settings at any time.