Customer.io plugin for Cursor and Grok bot

Install the official Customer.io plugin in Cursor or Grok bot to add the Customer.io MCP connector and skills so your agent can work in your workspace.

Connect Cursor or Grok bot to your Customer.io workspace with the official Customer.io plugin. It adds the Customer.io MCP connector and skills so your agent can work with automations, profiles, Design Studio, Pipelines, and SDKs—right inside your editor. The same plugin works in both Cursor and Grok bot; the steps below use Cursor’s UI, and the Grok bot flow is equivalent.

You need a Customer.io account with MCP enabled. Your editor installs the plugin; you still Connect once to authorize workspaces and permission scopes.

Before you start

• A Customer.io account with MCP enabled. If MCP is off, ask an account admin to turn it on. See Get started with MCP for the toggle, permission scopes, and live-data settings.
• Cursor Desktop. The Marketplace plugin loads in the editor—this isn’t a paste-a-URL MCP snippet.
• If you already connected Customer.io under Settings > Tools & MCP or in ~/.cursor/mcp.json, remove that server first. See Already using MCP in Cursor?.

Install the plugin

1. Open the Cursor Marketplace ↗.
2. Install Customer.io.
3. Reload the window if Cursor asks you to.

You don’t need to clone anything from GitHub to install the plugin.

Connect your account

1. Go to Settings > Tools & MCP.
2. Connect the customerio server.
3. Complete Customer.io OAuth. Choose the workspaces and permission scopes you want to grant, then allow access. See permission scopes for details.
4. Confirm Cursor shows a single Customer.io server named customerio.

You should see the Customer.io consent screen, then a connected server. If Connect opens a GitHub “search issues” page instead, see Troubleshooting.

The connector is mcp.customer.io. After you log in, the session uses your account’s home region automatically—EU and US accounts use the same Connect button. You never pick a data center or type a region-specific URL.

What you can ask

Once you’re connected, describe what you want in plain language. A few examples:

• List my Customer.io workspaces—which region am I on?
• List the active automations in my workspace.
• Find people who haven’t opened an email in 30 days and create a win-back segment.
• Draft or review a Design Studio welcome email.
• Add a JavaScript or React Native source in Pipelines.
• Set up Customer.io for my React Native app.

The agent looks up Customer.io skills and API schema instead of guessing endpoints, and it previews writes with a dry run before changing anything. When it does make a live change, Cursor shows you an approval first.

The plugin’s skills cover:

• Journeys — automations, profiles, segments, broadcasts, transactional, and in-app messages
• Design Studio — emails, components, global styles, review, and publish
• Pipelines — sources, destinations, reverse ETL, and moving data in and out
• SDKs — JavaScript and mobile SDK setup, sandbox testing, and going live

Using Grok bot

The same Customer.io plugin works in Grok bot, which installs plugins from the Cursor Marketplace. Install and connect it the same way:

1. From the Cursor Marketplace ↗, install Customer.io.
2. In Grok bot’s MCP or tools settings, connect the customerio server.
3. Complete Customer.io OAuth—choose your workspaces and permission scopes, then allow access.
4. Confirm a single Customer.io server named customerio is connected.

Everything else on this page—example prompts, the single-server guidance, and troubleshooting—applies to Grok bot too. Some menu and button labels may differ from Cursor’s, so match them to Grok bot’s current UI.

Already using MCP in Cursor?

Don’t add a second Customer.io MCP server. Two servers for the same host fight each other—typical symptoms are Connect opening a GitHub issues search, or OAuth getting stuck on an old workspace.

If you previously used Add to Cursor (in your Customer.io personal settings) or a hand-edited mcp.json:

1. Remove the user-level Customer.io / CustomerIO server from Settings > Tools & MCP, and from ~/.cursor/mcp.json if it’s there.
2. Install and connect the plugin as described above.

If you need Windsurf, VS Code, or the Gemini CLI, those stay on Cursor and other IDEs.

Troubleshooting

The plugin is open source—see github.com/customerio/cursor-plugin ↗ (MIT).