How to integrate E2b MCP with Codex

Framework Integration Gradient
E2b Logo
Codex Logo
divider

Introduction

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

The E2b MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your E2b account. It provides structured and secure access so your agent can perform E2b operations on your behalf.

Supported Tools & Triggers

Tools
Connect to SandboxTool to connect to an existing E2B sandbox and retrieve its details.
Create TemplateTool to create a new E2B template with specified configuration.
Create WebhookTool to register a new webhook to receive sandbox lifecycle events for the team.
Delete SandboxTool to terminate and permanently delete a running E2B sandbox instance.
Delete WebhookTool to unregister a webhook and stop receiving lifecycle events.
Check API HealthTool to check the health status of the E2B API.
Get SandboxTool to retrieve detailed information about a specific sandbox by its ID.
Get Sandbox LogsTool to retrieve logs from a specific E2B sandbox instance.
Get Sandbox Lifecycle EventsTool to retrieve the latest lifecycle events for a particular sandbox instance.
Get Sandbox MetricsTool to retrieve timestamped CPU, memory, and disk usage metrics for a sandbox.
Get Team MetricsTool to retrieve timestamped CPU, memory, and disk usage metrics for a team.
Get Team Maximum MetricsTool to retrieve the maximum value for a specific team metric in a given interval.
Get Template Build StatusTool to get the status of a template build.
Get Template FilesTool to get an upload link for a tar file containing build layer files.
Get Webhook ConfigurationTool to retrieve the current webhook configuration for a specific webhook.
List All SandboxesTool to list all running and paused sandboxes associated with your team.
List Sandboxes MetricsTool to retrieve timestamped CPU, memory, and disk usage metrics for multiple sandboxes.
List Team Sandbox Lifecycle EventsTool to retrieve the latest lifecycle events across all sandboxes associated with the team.
List All TemplatesTool to list all available E2B templates for your team.
List All WebhooksTool to retrieve all registered webhooks for your team.
Pause SandboxTool to pause a running E2B sandbox preserving its filesystem and memory state.
Create SandboxTool to create a new E2B sandbox from a template.
Set Sandbox TimeoutTool to set the timeout for an E2B sandbox.
Refresh SandboxTool to refresh an E2B sandbox and extend its time to live.
Start Template BuildTool to start a build for an E2B template.
Update TemplateTool to update an E2B template configuration.
Update Webhook ConfigurationTool to update an existing webhook configuration including URL, enabled status, and subscribed events.

Conclusion

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

How to build E2b MCP Agent with another framework

FAQ

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

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

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

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