How to integrate Customerio MCP with Codex

Customerio logo
Codex logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Customerio MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate Customerio with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Customerio MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on connect.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

What is the Customerio MCP server, and what's possible with it?

The Customerio MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Customer.io account. It provides structured and secure access to your customer engagement workspace, allowing your agent to send targeted communications, manage segments, retrieve messaging analytics, and automate customer data management on your behalf.

  • Targeted message analytics and tracking: Retrieve detailed lists of messages sent, including delivery metrics, to monitor campaign performance and engagement.
  • Segment discovery and membership management: Let your agent fetch all segments, get details for a specific segment, and list all customers in a segment for precise audience targeting.
  • Integration and webhook management: Have your agent list and review all integrations and webhooks in your workspace to streamline system connectivity and reporting.
  • Customer profile suppression: Direct your agent to permanently suppress (delete and block) customer profiles, ensuring compliance and data privacy.
  • Collection metadata retrieval: Retrieve up-to-date details for all collections in your workspace, keeping your AI-powered workflows and automations in sync with your data sources.

Supported Tools & Triggers

Tools
Suppress Customer ProfileTool to suppress a person.
Get IntegrationsTool to retrieve a list of integrations in your workspace.
Get MessagesTool to retrieve a list of messages sent from your workspace.
Get Segment DetailsTool to retrieve details of a specific segment.
Get Segment MembershipTool to retrieve people in a specific segment.
Get SegmentsTool to retrieve a list of segments in your workspace.
Get TriggerTool to retrieve details about a specific trigger.
Get TriggersTool to retrieve a list of triggers for a specific broadcast.
Get Customer.io Workspace WebhooksTool to retrieve a list of webhooks.
List CollectionsTool to list all collections metadata.
List NewslettersTool to list all newsletters.
List SnippetsTool to list all snippets in your workspace.
List Transactional MessagesTool to list all transactional message templates.
Trigger BroadcastTool to manually trigger a broadcast.

Conclusion

You've successfully integrated Customerio with Codex using Composio's MCP server. Now you can interact with Customerio directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Customerio operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Customerio operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Customerio MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Customerio MCP?

With a standalone Customerio MCP server, the agents and LLMs can only access a fixed set of Customerio tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Customerio and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Codex?

Yes, you can. Codex fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Customerio tools.

Can I manage the permissions and scopes for Customerio while using Tool Router?

Yes, absolutely. You can configure which Customerio scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Customerio data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.