Cursor and other IDEs

Connect your IDE to Customer.io MCP. Use the Customer.io plugin for Cursor, plus instructions for any IDE that supports MCP (Windsurf, VS Code, Gemini CLI, and more).

Using Cursor? Install the plugin

If you use Cursor, install the Customer.io plugin from the Cursor Marketplace. It’s the recommended setup and adds the Customer.io connector plus skills in one step. This page covers other MCP-capable editors, along with the legacy user-level Cursor install.

Cursor (legacy one-click setup)

Don't run this alongside the plugin

The Customer.io plugin for Cursor is the recommended way to connect Cursor. The one-click installer below adds a user-level MCP server instead. Use one or the other—running both makes the two servers fight each other. If you install the plugin, remove any server you added this way.

Cursor has a one-click installer in your Customer.io personal settings.

The MCP section of the personal settings page showing a button to enable MCP support for Cursor
  1. Go to Settings > Personal Settings.
  2. Click the Cursor tab and click Add to Cursor.
  3. In Cursor, click Needs Login to authenticate with Customer.io.
  4. Select the workspaces and permissions you want to grant access to and click Allow access. See permission scopes for details on permissions.
    The authorization screen where you select workspaces and set permission scopes for your MCP connection

Windsurf, VS Code, and other MCP-capable IDEs

For any IDE that supports MCP, you can add Customer.io as a custom MCP server by editing your tool’s MCP configuration.

You’ll need our MCP server URL: https://mcp.customer.io/mcp. You can use this URL for both US and EU accounts. When you sign in, Customer.io connects you to your account’s region.

If your tools don’t follow the redirect that sends EU requests to the EU region, use https://mcp-eu.customer.io/mcp instead.

If your tool asks for a transport type, choose Streamable HTTP, or set type to http in a configuration file. We don’t support the server-sent events (sse) transport type.

Add an entry like this to your MCP config:

JSON
{
  "mcpServers": {
    "CustomerIO": {
      "type": "http",
      "url": "https://mcp.customer.io/mcp"
    }
  }
}

After you save the config, your IDE will prompt you to authenticate with Customer.io. Select the workspaces and permissions you want to grant access to and click Allow access. See permission scopes for details on permissions.

The authorization screen where you select workspaces and set permission scopes for your MCP connection

Gemini CLI

The Gemini CLI connects to Customer.io MCP through its ~/.gemini/settings.json file.

You’ll need our MCP server URL: https://mcp.customer.io/mcp. You can use this URL for both US and EU accounts. When you sign in, Customer.io connects you to your account’s region.

If your tools don’t follow the redirect that sends EU requests to the EU region, use https://mcp-eu.customer.io/mcp instead.

If your tool asks for a transport type, choose Streamable HTTP, or set type to http in a configuration file. We don’t support the server-sent events (sse) transport type.

Add an entry like this:

JSON
{
  "mcpServers": {
    "customerio": {
      "url": "https://mcp.customer.io/mcp"
    }
  }
}

After saving the config, start the Gemini CLI and run /mcp auth customerio to authenticate with Customer.io. See permission scopes for details on permissions.

For more details, see the Gemini CLI docs on OAuth support for remote MCP servers.

Find your workspace

When you use Customer.io MCP, you’ll need to tell your AI tool which workspace to work in. You can select a workspace by name or by ID.

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

Manage your MCP sessions

To see active sessions or revoke a connection, go to Settings > Personal Settings and click View sessions under Connected clients. Revoking a session ends it immediately and forces the client to re-authenticate.

A cursor session shown in Customer.io
Updated October 28, 2026