Claude Code How to use Customer.io with Claude Code
You want Customer.io inside Claude Code so it can triage customer lifecycle activity, update customer profiles from support outcomes, send a transactional customer update, and measure and trigger a lifecycle campaign — without you copy-pasting between tabs. Here is the whole setup, once.
Create your Customer.io gateway
The gateway is the thing Claude Code connects to, and it is where you decide which Customer.io tools an agent may use. You create it once and every client reuses it.
-
Create an Arcade account
Sign up and open the dashboard. The free tier is enough to follow this through.
-
Create an MCP Gateway and select your Customer.io tools
In the dashboard, create a gateway and pick the Customer.io tools you want to expose. The gateway is what your client connects to, and it is where tool access is decided.
-
Copy your gateway URL
Every client below needs it.
https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>
Connect the gateway to Claude Code
-
Add the gateway as a remote HTTP MCP server
claude mcp add arcade --transport http "<YOUR_ARCADE_GATEWAY_URL>"
-
Verify it was added
claude mcp get arcade claude mcp list
-
Try it out
Open Claude Code in your project and ask it to use one of your Customer.io tools.
Full Claude Code guide in the docs steps verified 2026-08-13
Get started with these Customer.io prompts
Claude Code can now act on your Customer.io account. Click a prompt to copy it.
Use scoped credentials and tool permissions to control which Customer.io actions an agent can take. Pair it with Contextual Access policies to require approval before an agent triggers a broadcast, sends transactional email, or deletes a person record.
