E2B Code Sandbox MCP

Name: E2B Code Sandbox MCP
Author: E2B

Run code in secure cloud sandboxes with E2B

Official

Developer Tools

Install Command

npx @e2b/mcp-server

Claude Desktop Config

{
  "mcpServers": {
    "e2b": {
      "command": "npx",
      "args": ["-y", "@e2b/mcp-server"],
      "env": { "E2B_API_KEY": "<YOUR_API_KEY>" }
    }
  }
}

E2B Code Sandbox MCP is an officially maintained MCP server in the Developer Tools category, developed by E2B. It runs locally on your machine, keeping your data private and giving you full control over the connection. Developers can use it to bring AI assistance directly into their build and coding environment.

About E2B Code Sandbox MCP

E2B MCP allows AI agents to execute code in secure, isolated cloud sandboxes — supporting Python, JavaScript, and more.

Features

Secure sandboxed code execution
Supports Python, Node.js, Bash, and more
File upload and download
Long-running process support
Package installation within sandbox
Real-time stdout/stderr streaming

Who Should Use E2B Code Sandbox MCP?

1Speed up coding workflows by letting Claude interact with your dev environment
2Run terminal commands, manage processes, and inspect logs via AI
3Integrate AI assistance directly into your build and CI pipelines
4Automate repetitive dev tasks like scaffolding, linting, and testing

How to Install E2B Code Sandbox MCP

Before you start

You will need Node.js (v18 or later) installed on your machine — download it from nodejs.org if you haven't already.

1Open a terminal (Terminal on Mac, Command Prompt or PowerShell on Windows).
2Paste the install command above and press Enter — Node.js will download and run the server automatically.
3Add the server to your Claude Desktop config file (see the JSON snippet above) and restart Claude.

The Claude Desktop config snippet above can be copied and pasted directly into your claude_desktop_config.json file — no editing required.

How E2B Code Sandbox MCP Compares

✦It is an officially maintained server — unlike community alternatives, it is built and supported by the original project team, ensuring compatibility with upstream changes.

✦It runs entirely on your local machine, so no data leaves your environment — important for teams with privacy or compliance requirements.

✦Authentication uses API keys, giving you fine-grained control over access without requiring a full OAuth setup.