How to integrate E2b MCP with Claude Code

GET STARTED FOR FREE
Framework Integration Gradient
E2b Logo
Claude Code Logo
divider

Introduction

Manage your E2b directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Rube - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Why Rube?

Rube is a universal MCP server with access to 850+ SaaS apps. It ensures just-in-time tool loading so Claude can access the tools it needs, a remote workbench for programmatic tool calling and handling large tool responses out of the LLM context window, ensuring the LLM context window remains clean.

Connect E2b to Claude Code with Rube

1. Get the MCP URL

Copy and paste the below command in Claude Code to add Rube MCP.

Terminal

2. Authenticate Rube

Run /mcp to view Rube

bash
/mcp
Run /mcp to view Rube in Claude Code
Click on Rube to authenticate
Authentication flow complete

3. Ensure it's connected

Run /mcp again to verify the connection. Now, do whatever you want with Claude Code and E2b.

Rube connected successfully

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.

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.

Connecting E2b via Tool Router

Tool Router is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here E2b) for even more tool search precision. It's secure and reliable.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A E2b account
  • Basic knowledge of Python or TypeScript

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)

Install Composio library

pip install composio-core python-dotenv

Install the Composio Python library to create MCP sessions.

  • composio-core provides the core Composio functionality
  • python-dotenv loads environment variables from your .env file

Generate Composio MCP URL

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["e2b"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http e2b-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Create a script to generate a Composio MCP URL for E2b. This URL will be used to connect Claude Code to E2b.

What's happening:
  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for E2b
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it

Run the script and copy the MCP URL

python generate_mcp_url.py

Run your Python script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output

Add E2b MCP to Claude Code

bash
claude mcp add --transport http e2b-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (e2b-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

Verify the installation

bash
claude mcp list

Check that your E2b MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your e2b-composio entry in the list
  • This confirms that Claude Code can now access E2b tools

If everything is wired up, you should see your e2b-composio entry listed:

Claude Code MCP list showing the toolkit MCP server

Authenticate E2b

The first time you try to use E2b tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with E2b
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the E2b authorization flow
  • Return to the terminal and start using E2b through Claude Code

Once authenticated, you can ask Claude Code to perform E2b operations in natural language. For example:

  • "Run a Python script to analyze CSV data"
  • "Execute JavaScript code to validate user input"
  • "Start a sandbox and list installed packages"

Complete Code

Here's the complete code to get you started with E2b and Claude Code:

import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
USER_ID = os.getenv("USER_ID")

composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=USER_ID,
    toolkits=["e2b"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url

print(f"MCP URL: {COMPOSIO_MCP_URL}")
print(f"\nUse this command to add to Claude Code:")
print(f'claude mcp add --transport http e2b-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"')

Conclusion

You've successfully integrated E2b with Claude Code using Composio's MCP server. Now you can interact with E2b directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for E2b operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various E2b operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

How to build E2b MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use E2b MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use E2b MCP with Claude Agent SDK

Google ADK

Google ADK

Use E2b MCP with Google ADK

LangChain

LangChain

Use E2b MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use E2b MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use E2b MCP with Mastra AI

LlamaIndex

LlamaIndex

Use E2b MCP with LlamaIndex

CrewAI

CrewAI

Use E2b MCP with CrewAI

Codex

Codex

Use E2b MCP with Codex

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 Claude Code?

Yes, you can. Claude Code 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.

Book a call↗Get started for free