Customer.io plugin for Claude

Install the official Customer.io plugin for Claude to add the Customer.io MCP connector, skills, and slash commands so Claude can work in your workspace in chat, Cowork, and Claude Code.

Connect Claude to your Customer.io workspace with the official Customer.io plugin. It adds the Customer.io MCP connector, skills, and slash commands so Claude can work in your Customer.io workspaces, within the permissions you grant when you sign in. Its skills point Claude to the right Customer.io guidance for each task, and its slash commands start common workflows. The plugin works in Claude chat on the web, desktop, and mobile, in Cowork, and in Claude Code.

Before you start

A Customer.io account with MCP enabled. If MCP is off, ask an account admin to turn it on. See Get started with MCP for the toggle, permission scopes, and live-data settings.
A Claude Pro, Max, Team, or Enterprise plan. Claude’s plugin directory isn’t available on the Free plan.
If you already added Customer.io to Claude Code by hand, remove that server first. See Already using Customer.io MCP in Claude?.

Install the plugin

In claude.ai or the Claude desktop app:

Go to Customize > Plugins and select Discover.
Click Customer.io and click Add.

A plugin you add in claude.ai is saved to your Claude account, so you don’t need to install it again in Cowork or Claude Code. Cowork loads it the next time you start a task. Claude Code downloads it the next time you start a session signed in to the same account. Run /reload-plugins to load it into a session that’s already open.

On a Team or Enterprise plan, an Owner of your Claude organization can install the plugin for everyone in your organization, either installed by default or required.

In Claude Code, you can also run /plugin and install Customer.io from the directory, or add it from our marketplace:

BASH

/plugin marketplace add customerio/claude-plugin
/plugin install customerio@customerio

Restart Claude Code if it asks you to. A plugin you install from the Claude Code command line stays on that computer and isn’t added to your Claude account.

Connect your account

In claude.ai or the Claude desktop app:

Go to Customize > Plugins, open Customer.io, and click the Connectors tab.
Click Add or Connect to add the Customer.io connector. If it shows Connected, then you’re already connected.
Sign in to Customer.io.
Choose the workspaces and permission scopes you want to grant and click Allow access. See permission scopes for details.

In Claude Code:

Ask Claude anything Customer.io-related, or run /mcp and connect the customerio server.
Sign in to Customer.io in the browser tab that opens. Choose the workspaces and permission scopes you want to grant, then allow access.
Confirm /mcp shows a single Customer.io server, connected.

The connector is mcp.customer.io. After you log in, the session uses your account’s home region automatically—EU and US accounts use the same flow, and you never pick a data center or type a region-specific URL.

What you can ask

Once you’re connected, describe what you want in plain language. A few examples:

List my Customer.io workspaces—which region am I on?
List the active automations in my workspace.
Find people who haven’t opened an email in 30 days and create a win-back segment.
Draft or review a Design Studio welcome email.
Add a JavaScript or React Native source in Pipelines.
Set up Customer.io for my React Native app.

Or start from a slash command. In Cowork and Claude Code, type the command. In chat, type / in the message box and pick the command from the list.

Command	What it does
`/customerio:campaign-report`	Metrics and recommendations for an automation
`/customerio:build-segment`	Build a segment from a plain-English audience description
`/customerio:draft-email`	Create a Design Studio draft with a QA review
`/customerio:workspace-health`	Read-only deliverability and pipeline diagnosis

The agent looks up Customer.io skills and API schema instead of guessing endpoints. It previews writes with a dry run, and Claude Code asks for your permission before a live write changes anything.

The plugin’s skills cover:

Journeys — automations, people, segments, broadcasts, transactional, and in-app messages
Design Studio — emails, components, global styles, review, and publish
Pipelines — sources, destinations, reverse ETL, and moving data in and out
SDKs — JavaScript SDK setup, sandbox testing, and going live
Mobile — iOS, Android, React Native, Flutter, and Expo setup, push, and troubleshooting

Already using Customer.io MCP in Claude?

Keep one Customer.io server in Claude Code. Two servers for the same host fight each other—duplicate tools, OAuth stuck on an old workspace, or tools that quietly hit the wrong session.

If you previously added Customer.io to Claude Code by hand (with claude mcp add, an .mcp.json edit, or a pasted URL):

Remove that server—for example, run claude mcp remove customerio, or delete it from wherever you added it.
Install the plugin and connect as described above.

Claude Code also loads the connectors you added in claude.ai. If your claude.ai Customer.io connector uses https://mcp.customer.io/mcp, Claude Code connects through the plugin. If you added the connector with our EU MCP server URL, Claude Code shows two Customer.io servers. Remove the connector in Customize > Connectors and connect Customer.io from the plugin’s Connectors tab instead.

Troubleshooting

Symptom	What to do
No Customer.io plugin in the directory	On a Team or Enterprise plan, your organization might not include the plugin directory. Ask an Owner of your Claude organization to make the Customer.io plugin available. In Claude Code, you can install it with `/plugin marketplace add customerio/claude-plugin`, then `/plugin install customerio@customerio`. Don’t fall back to pasting `mcp.customer.io` as a custom server.
OAuth doesn’t open or “needs login”	Confirm an admin enabled Customer.io MCP. Then connect again from the plugin’s Connectors tab, or run `/mcp` in Claude Code and retry the connection.
Claude can’t see any Customer.io tools	In chat, check that the plugin’s Connectors tab shows Customer.io as Connected. In Claude Code, run `/mcp` and confirm customerio is connected, and check the plugin is enabled under `/plugin`. Restart Claude Code if needed.
Duplicate Customer.io tools or servers	Another Customer.io server is running next to the plugin’s. Remove the extra server as described in Already using Customer.io MCP in Claude?.
Writes are blocked, or you get a 403 about live data	The workspace’s Allow agent to edit live data setting is off. That’s an admin setting—see Get started with MCP.
You have an EU account and worry you need a different URL	You don’t. It’s the same connector; your region follows your account after OAuth.

The plugin is open source—see github.com/customerio/claude-plugin (MIT).

Updated November 13, 2026