Customer.io

Customer.io plugin for ChatGPT and Codex

Install the official Customer.io plugin for ChatGPT and Codex to explore your workspace and work with Journeys, Design Studio, Pipelines, and the SDKs conversationally.

Awaiting OpenAI review

We’ve submitted the Customer.io plugin to OpenAI and are waiting for them to review and publish it. Until it’s live, Customer.io may not appear in the plugin directory yet. Until then, use the direct ChatGPT MCP setup for approved development or testing access. The rest of this page stays accurate once the listing is published.

Install the Customer.io plugin to explore your Customer.io account, work with Journeys and Pipelines, build messages, and get SDK implementation help—right inside ChatGPT or Codex.

The same official listing works in both ChatGPT and Codex. You connect your account with Customer.io OAuth, choose the workspaces and permission scopes you want to authorize, and supported changes are previewed before they run live.

Plugin vs. custom MCP connection

The plugin is the recommended way to use Customer.io in ChatGPT and Codex. If you previously added Customer.io as a custom MCP connection in the same OpenAI environment, don’t keep both—see Already connected Customer.io as a custom MCP server? For direct or advanced MCP setup, see ChatGPT setup. For other tools, see Cursor and Grok bot, Cursor and other IDEs, and Claude.

Before you start

  • Access to a Customer.io account.
  • A Customer.io account admin has enabled MCP access. See Get started with MCP for admin enablement, permission scopes, and workspace access.
  • Permission to the workspaces you want to work in.
  • Access to Plugins in your ChatGPT or Codex surface.

Install the plugin

  1. Open Plugins in ChatGPT or Codex.
  2. Search for Customer.io.
  3. Open the listing published by Customer.io.
  4. Select Install.
  5. Review the listed permissions and capabilities.

You don’t need GitHub, a terminal, JSON, or a Customer.io API token to install the plugin. The exact button labels can differ slightly between ChatGPT and Codex, but the steps are the same.

Connect your account

  1. Select Connect for Customer.io.
  2. Sign in to Customer.io if you’re prompted.
  3. Choose the account and workspaces you want, and the permission scopes you want to grant. See permission scopes for details.
  4. Approve the connection.
  5. Return to ChatGPT or Codex and start a Customer.io request.

You never pick a data center or type a region-specific URL. Every Customer.io account is tied to US or EU, and after you sign in, requests route to the right region automatically. EU and US accounts use the same Connect flow.

Try it

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

  • List my active Customer.io automations and summarize what each one does.
  • Review the last seven days of delivery metrics for my onboarding automation.
  • Find people who signed up this week but haven’t started onboarding.
  • Review my welcome email design and suggest accessibility improvements.
  • Show me the sources and destinations configured in Pipelines.
  • Help me plan a Customer.io SDK integration for a React Native app.
  • Draft the Customer.io changes needed for this request and show me the preview before anything goes live.

The plugin’s skills cover:

  • Customer.io and Journeys — inspect workspaces, profiles, segments, automations, broadcasts, and transactional messages; review delivery and engagement metrics; and troubleshoot configuration.
  • Design Studio — inspect and revise email designs, follow Customer.io design conventions, and preview changes before a live update.
  • Pipelines — inspect sources, destinations, and schemas; configure or troubleshoot integrations; and reason about data quality and delivery.
  • SDKs — plan an integration, get platform-specific setup guidance, and reason about identification, events, push, and in-app messaging using current Customer.io resources.

The skills guide ChatGPT or Codex through the right workflow, while the hosted Customer.io MCP server stays the source of current tools and account data—so the agent works from live schema instead of stale, memorized instructions.

How ChatGPT and Codex use the same plugin

  • There’s one Customer.io public plugin listing, shared by both products.
  • In ChatGPT, it supports conversational research and Customer.io workflows.
  • In Codex, the same connection can support implementation work along with the included Customer.io workflow skills.
  • Availability and presentation can differ by OpenAI surface, but you don’t need a separate regional endpoint or a Customer.io token in either one.

Already connected Customer.io as a custom MCP server?

If you previously added Customer.io as a custom MCP connection, disable or remove that duplicate connection before using the official plugin. Keeping both enabled in the same OpenAI environment can produce duplicate tools or make it unclear which connection handled a request.

This applies only to duplicate Customer.io connections within the same OpenAI environment—you don’t need to remove Cursor, Claude, or other clients. For the direct or advanced MCP path, see ChatGPT setup; most users should choose the official plugin once it’s public.

Safety, permissions, and privacy

  • Customer.io only exposes the workspaces and permission scopes you approve during connection.
  • Read, write, and delete access depend on the scopes you grant.
  • Supported write and delete operations can return a dry-run preview, so you can review the proposed effect before anything runs live. Treat this as a safety feature, not blanket authorization.
  • Review generated content and proposed changes before you approve them.
  • See Customer.io’s privacy policy and terms of service.

Troubleshooting

SymptomWhat to do
Customer.io doesn’t appear in PluginsThe public listing may still be in OpenAI review. Confirm Plugins are available for your OpenAI account or workspace. Use the direct ChatGPT MCP setup only as a development or testing fallback.
Connect is unavailable or authorization failsConfirm an admin enabled Customer.io MCP and that you have access to at least one workspace, then retry the OAuth connection.
The plugin can’t access an expected object or actionCheck the selected workspace and the granted scopes, and reconnect if you need different scopes. Not every object supports every operation.
Customer.io tools appear twiceLook for a duplicate custom Customer.io MCP connection. Keep either the official plugin or the manual connection enabled in that OpenAI environment—not both.
You have a US or EU account and worry about the endpointYou don’t choose an endpoint. Reconnect the intended Customer.io account; routing follows the authenticated account automatically. Don’t point at mcp-eu.customer.io or edit host environment variables.

For implementers

The plugin connects to one universal Customer.io MCP entry point, https://mcp.customer.io/mcp. You don’t need to enter it during the normal install—it’s here only as a reference for advanced setups. See Get started with MCP for the underlying MCP concepts.

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

Updated August 25, 2026