How to use Customer.io with Cursor
You want Customer.io inside Cursor 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 Cursor 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 Cursor
Cursor does not refresh MCP OAuth tokens automatically. For a persistent connection, set Authorization to “Arcade Headers” on the gateway in the dashboard.
-
Open MCP settings
Command Palette (⌘⇧P / Ctrl+Shift+P) → Open MCP Settings, then click “New MCP Server”.
-
Add the gateway to mcpServers
{ "mcpServers": { "mcp-arcade": { "url": "https://api.arcade.dev/mcp/<YOUR-GATEWAY-SLUG>" } } } -
Try it out
Ask Cursor to use one of your Customer.io tools.
Full Cursor guide in the docs steps verified 2026-08-13
Get started with these Customer.io prompts
Cursor 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.