The Customer.io MCP Server

BetaThis feature is new and we're actively working to improve it. Contact us if you'd like to try it out. Updated

How it works

Our Model Context Protocol (MCP) Server helps you interact with Customer.io through your favorite AI tools—Claude, Cursor, and so on.

Where you might be able to use our APIs to do some things, the MCP server is a layer of tools that includes features that aren’t possible with our APIs today.

 Make sure you trust your AI tools

Our MCP server works with your AI provider of choice and it includes tools that return information about people in your workspace. While our LLM subprocessors don’t store this data, the AI providers you use might. Make sure that you use AI tools that are approved by your organization to ensure the safety of your—and your customers’—data.

What tools does the MCP server support?

The table below shows the tools that are currently available to our MCP server, and the actions that each tool can perform. As we expand the capabilities of our MCP server, we won’t just add more tools, but more actions to the existing tools; this helps us limit the number of tools we provide, so we don’t overwhelm you or your LLM with a lengthy MCP toolchain.

We’re actively working on our MCP server and related tools. If you have a specific MCP feature or use case in mind, let us know!

Tool NameDescription
createCreate new resources like segments, campaigns, and other workspace entities.
Action: create_segment
getGet detailed information about single resources like user profiles, segments, campaigns etc.
Action: get_profile
integrationThis tool helps you integrate Customer.io into mobile and web applications, including authentication and adding necessary code to your app to support push notifications and in-app messages.*
Available actions: sources_list, sources_search, source_get, source_add, test_inapp, test_push, troubleshoot
listList workspace resources and metadata, like profile attributes, segments, events etc.
Available actions: list_attributes, list_segments, list_events
list_workspacesLists the workspaces the user has access to. Always call this first to get a workspace_id for workspace-scoped actions.
searchSearch across documentation and workspace data for specific content and patterns.
Available actions: search_docs, search_workspace

* Summary of tool's description. See the tool in your environment for the full description.

Enable MCP support for your account

You must be an account admin to enable MCP support for your account. This enables the feature for your account, but you and other users still need to set up your clients to use it.

  1. Go to > Account Settings and then click Privacy & Data.

  2. Enable Customer.io MCP.

    The Privacy & Data Settings page showing the Customer.io MCP setting enabled
    The Privacy & Data Settings page showing the Customer.io MCP setting enabled

Set up your MCP client

Before you can use the MCP server, you’ll need to Enable MCP support for your account. If you haven’t done that yet, you won’t see MCP support in your personal settings.

Cursor and other IDEs (Windsurf, VS Code, etc)

Adding MCP support to your integrated development environment (IDE) depends on whether you use Cursor—for which we have a one-click setup—or another tool like Windsurf.

The MCP section of the personal settings page showing a button to enable MCP support for Cursor
The MCP section of the personal settings page showing a button to enable MCP support for Cursor

  1. Go to > Personal Settings.

  2. Click the Cursor tab and enable support for your IDE:

    • If you use Cursor, click Add to Cursor.
    • If you use another tool like Windsurf, you’ll add some JSON to your MCP file. The example below is for Cursor; the exact JSON for your tool might change but, no matter which tool you use, you’ll need to add our MCP url.
    • If your application requires you to set the type, make sure you set it to http. We don’t support the server-sent events (sse) transport.
     {
   "mcpServers": {
     "CustomerIO": {
       "type": "http",
       "url": "https://mcp.customer.io/mcp"
     }
   }
 }

  3. When you’ve added MCP support, your IDE will show that you need to login or authenticate with Customer.io. In Cursor, you’ll click Needs Login to authenticate with Customer.io.

  4. Pick the workspaces you want to use with the MCP server.

    The list of workspaces you can select from when you authenticate with Customer.io
    The list of workspaces you can select from when you authenticate with Customer.io

Claude Desktop and similar tools

The instructions below focus on Claude Desktop, but the exact path to add Customer.io MCP support depends on the tool you use, but you’ll need to add the URL of our server to any tool you use: https://mcp.customer.io/mcp or https://mcp-eu.customer.io/mcp if your Customer.io account is in the EU.

Note that MCP support is not available on Claude’s free plan. You need a paid Claude plan to use custom MCP servers like Customer.io’s.

  1. Go to > Personal Settings.

  2. Click the Claude Desktop tab and enable support for your tool.

    1. For Claude Desktop, go to Settings > Connectors and click Add custom connector.
    2. Add the MCP server URL: https://mcp.customer.io/mcp or https://mcp-eu.customer.io/mcp if your Customer.io account is in the EU. If your application requires you to set a type or transport method, make sure you set it to http. We don’t support the server-sent events (sse) transport.
    3. Click Connect.

  3. Pick the workspaces you want to use with the MCP server.

    The list of workspaces you can select from when you authenticate with Customer.io
    The list of workspaces you can select from when you authenticate with Customer.io

Find your workspace

When you use our MCP server, you’ll often need to tell it which workspace you want to work in. Otherwise, the MCP server may ask you to select a workspace. You can select your workspace by name or by ID. You can even use the MCP server to list your available workspaces.

You’ll find the name of your workspace in the upper-left corner of our interface. You’ll find the ID of your workspace in the URL when you’re on the Dashboard page.

The workspace name in the upper-left and the ID in the URL
The workspace name in the upper-left and the ID in the URL

See MCP sessions

We log MCP sessions so you can control and revoke your own MCP sessions.

  1. Go to > Personal Settings.
  2. Under Connected clients, click View sessions.

From here you can see active sessions for a client. Click Revoke to end a session and require the client to re-authenticate with Customer.io

A cursor session shown in Customer.io
A cursor session shown in Customer.io
Copied to clipboard!
  Contents
Is this page helpful?