← All integrations

Customer.io MCP server

23 operations0 webhooks

Customer engagement platform for sending targeted email, SMS, and push messages, with endpoints for profiles, segments, broadcasts, transactional messages, newsletters, collections, snippets, and CDP tracking.

Use Customer.io in Claude, ChatGPT, Cursor or another MCP client

Connect Customer.io once in Corsair, then add one MCP address to your agent.

Connect Customer.io
Setup steps for Claude, ChatGPT, Cursor and Claude Code

Building your own app on the Corsair SDK? Get API keys

Try Customer.io with your agent

Connect Customer.io, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Customer.io on my account, then run one read-only example and show me the result.

Runs once, when you ask

Customer.io tools and triggers

Tools are what your agent can do in Customer.io through Corsair's MCP server. Triggers are the Customer.io events a routine can start from.

Profiles

  • AliasWrite

    Merge two profiles by aliasing the secondary into the primary

    profiles.alias

  • IdentifyWrite

    Identify a person and assign traits (creates or updates the profile)

    profiles.identify

  • Report PushWrite

    Report delivery metrics via the metrics endpoint (push events endpoint is deprecated)

    profiles.reportPush

  • SuppressDestructive

    Suppress a profile: permanently deletes it and blocks re-adding

    profiles.suppress

  • Track EventWrite

    Record an event for a person

    profiles.trackEvent

  • UnsubscribeWrite

    Unsubscribe a person from emails for a specific delivery

    profiles.unsubscribe

Broadcasts

  • Get TriggerRead-only

    Get details of a specific broadcast trigger

    broadcasts.getTrigger

  • List TriggersRead-only

    List API trigger instances for a broadcast

    broadcasts.listTriggers

  • TriggerWrite

    Trigger a Customer.io broadcast to a defined audience

    broadcasts.trigger

Cdp

  • BatchWrite

    Send multiple CDP calls (identify, track, page, screen, group, alias) in one batch

    cdp.batch

  • PageWrite

    Track a website page view via the CDP API

    cdp.page

  • ScreenWrite

    Track a mobile screen view via the CDP API

    cdp.screen

Connect Customer.io to Claude, ChatGPT or Cursor

  1. 1

    Connect Customer.io in Corsair

    Add your Customer.io API key once in Corsair. Corsair stores the credential encrypted and makes the Customer.io API calls for your agent, so it never goes into a prompt or a config file. Connect Customer.io

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Customer.io. On a ChatGPT personal plan, connect Customer.io here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Customer.io's read and write operations run right away and its 1 destructive operation waits for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/customerio, add the Customer.io plugin, and connect with an API key. Then call methods like corsair.customerio.api.broadcasts.getTrigger() from your app. Corsair keeps each tenant isolated.

Yes. Customer.io requires an API key from your Customer.io account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Customer.io, GitHub, Notion, Stripe, and the rest. Trigger Customer.io from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for customer engagement platform for sending targeted email, sms, and push messages, with endpoints for profiles, segments, broadcasts, transactional messages, newsletters, collections, snippets, and cdp tracking. Common builds include sync jobs, admin tooling, and agents that call Customer.io APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Customer.io API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/customerio in the open repo. When Customer.io ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Customer.io data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Customer.io data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Customer.io on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 1 destructive Customer.io operation. You can change a link's mode at hub.corsair.dev/me.