How to integrate Kit MCP with Codex

Framework Integration Gradient
Kit Logo
Codex Logo
divider

Introduction

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

Composio removes the Authentication handling completely from you. We handle the entire integration lifecycle, and all you need to do is just copy the URL below, authenticate inside Codex, and start using it.

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 Kit MCP in Codex

Codex CLI

Run the command in your terminal.

Terminal

This will auto-redirect you to the Rube authentication page.

Rube authentication redirect page

Once you're authenticated, you will be able to access the tools.

Verify the installation by running:

codex mcp list

If you otherwise prefer to use config.toml, add the following URL to it. You can get the bearer token from rube.app → Use Rube → MCP URL → Generate token

[projects."/home/user/composio"]
trust_level = "untrusted"

[mcp_servers.rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex in VS Code

If you have installed Codex in VS Code.

Then: ⚙️ → MCP Settings → + Add servers → Streamable HTTP:

Add the Rube MCP URL: https://rube.app/mcp and the bearer token.

VS Code MCP Settings

To verify, click on the Open config.toml

Open config toml in Codex

Make sure it's there:

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
Codex App MCP Settings
  1. Restart and verify if it's there in .codex/config.toml
[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"
  1. Save, restart the extension, and start working.

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

The Kit MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Kit account. It provides structured and secure access to your subscriber lists, tags, forms, and automations, so your agent can perform actions like managing subscribers, creating tags, updating custom fields, and handling broadcasts on your behalf.

  • Subscriber management and automation: Add new subscribers to forms, remove subscribers, or update their details to keep your audience lists accurate and engaged.
  • Custom field and tag creation: Automatically create, update, or delete custom fields and tags, making it easy to segment and personalize your communications.
  • Webhook and event setup: Set up or remove webhooks so your agent can listen for subscriber or purchase events and trigger automations as needed.
  • Broadcast and campaign control: Delete obsolete broadcasts or manage your messaging campaigns directly through your agent for streamlined outreach.
  • Account insights and configuration: Retrieve detailed account information, including plan details and primary contact, to keep your integrations and automations running smoothly.

Supported Tools & Triggers

Tools
Add Subscriber to FormTool to add a subscriber to a specific form by id.
Create Custom FieldTool to create a new custom field for subscriber data.
Create TagTool to create a new tag in the account.
Create WebhookTool to create a new webhook subscription.
Delete BroadcastTool to delete a specific broadcast.
Delete Custom FieldTool to delete a specific custom field.
Delete SubscriberTool to delete (unsubscribe) a subscriber by id.
Delete TagTool to delete a tag by id.
Delete WebhookTool to delete a webhook by id.
Get AccountTool to retrieve current account information.
Get Account ColorsTool to retrieve list of colors associated with the account.
Get BroadcastTool to retrieve details of a specific broadcast by id.
Get Broadcast StatsTool to retrieve statistics for a specific broadcast by id.
Get Creator ProfileTool to retrieve the creator profile information for the account.
Get Email StatsTool to retrieve email statistics for the account.
List BroadcastsTool to retrieve a paginated list of all broadcasts.
List Custom FieldsTool to retrieve a paginated list of custom fields.
List FormsTool to list all forms.
List SegmentsTool to retrieve a paginated list of segments.
List SequencesTool to retrieve a paginated list of all sequences.
List SubscribersTool to retrieve a list of subscribers.
List Subscribers For FormTool to retrieve subscribers for a specific form by id.
List TagsTool to retrieve a list of all tags.
List Tag SubscribersTool to retrieve subscribers for a specific tag.
Tag SubscriberTool to associate a subscriber with a specific tag by id.
Tag Subscriber by EmailTool to associate a subscriber with a tag using an email address.
Update Account ColorsTool to update the list of colors for the account.
Update Custom FieldTool to update a custom field's label.
Update TagTool to update a tag's name by id.

Conclusion

You've successfully integrated Kit with Codex using Composio's Rube MCP server. Now you can interact with Kit 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 Kit operations
  • Managed authentication through Composio's Rube
  • 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 Kit operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Kit MCP Agent with another framework

FAQ

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

With a standalone Kit MCP server, the agents and LLMs can only access a fixed set of Kit tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Kit 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 Kit tools.

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

Yes, absolutely. You can configure which Kit 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 Kit 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.