How to integrate Esputnik MCP with Codex

Framework Integration Gradient
Esputnik Logo
Codex Logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Esputnik 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 Esputnik 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 Esputnik MCP server, and what's possible with it?

The Esputnik MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Esputnik account. It provides structured and secure access to your marketing automation tools, so your agent can perform actions like sending broadcasts, managing contacts, importing data, and handling push notifications on your behalf.

  • Bulk contact import and management: Quickly add or update thousands of contacts at once, check import status, and keep your lists up to date with minimal effort.
  • Broadcast and message control: Retrieve, review, and manage your marketing broadcasts and app inbox messages, ensuring your campaigns run smoothly.
  • Order and transactional data automation: Import and synchronize large batches of order data, keeping your marketing segmentation and triggers accurate and relevant.
  • Push and SMS notification management: Activate or deactivate push tokens, delete outdated SMS templates, and fine-tune your notification workflows directly through your agent.
  • Domain and integration setup: Register domains for web tracking or widgets, helping you expand and customize your communication reach seamlessly.

Supported Tools & Triggers

Tools
ADD_DOMAINTool to register a domain for web tracking or widgets.
Add Orders BulkTool to transfer orders in bulk to eSputnik.
Bulk Add or Update ContactsTool to bulk add or update up to 3000 contacts asynchronously.
Change Token ActivityAction to change (activate/deactivate) the activity state of a mobile push token.
Delete ContactTool to delete a contact by its Yespo ID.
Delete Contact by External IDTool to delete a contact by externalCustomerId.
Delete SMS MessageTool to delete a base SMS message by ID.
Get App Inbox MessageTool to retrieve an App Inbox message by ID.
Get BroadcastsTool to list broadcasts from eSputnik.
Get Contact Import StatusTool to retrieve the status of a contact import session.
Get Contact SubscriptionsTool to retrieve subscription categories for a contact.
Get Organization BalanceTool to retrieve the current organization balance.
Get Organization Billing HistoryTool to retrieve the organization billing history by day and media channel.
Get Preprocessor File StatusTool to retrieve the status of a preprocessor file upload session.

Conclusion

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

How to build Esputnik MCP Agent with another framework

FAQ

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

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

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

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