Log inSubmit server
E2b Sandbox MCP logo

E2b Sandbox MCP

by asif-nvc

Runs commands, manages files, and performs Git operations inside isolated E2B Linux sandboxes through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install E2b Sandbox MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "asif-nvc-e2b-sandbox-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "e2b-sandbox-mcp"
      ],
      "env": {
        "E2B_API_KEY": "YOUR_VALUE_HERE",
        "GITHUB_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y e2b-sandbox-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

The asif-nvc/e2b-sandbox-mcp MCP server gives Claude Code access to E2B cloud-based Linux VMs through 29 MCP tools. It can create and manage sandboxes, execute foreground or background processes, transfer and edit files, and perform Git operations without using the local machine. Sandboxes can be paused, resumed, extended, or destroyed, and running services can receive public preview URLs. Reach for it when an agent needs an isolated environment for repository work, testing, experiments, or temporary development servers.

Use cases

  • Clone and test a GitHub repository without installing it locally
  • Run risky dependency upgrades or migration scripts in a disposable VM
  • Start a development server and open its public preview URL
  • Pause a development environment and resume it later
  • Commit and push repository changes from an isolated sandbox

Key features

  • Create and manage isolated E2B Linux sandboxes
  • Execute foreground and background shell commands
  • Read, write, transfer, and manage sandbox files
  • Clone repositories and perform Git operations
  • Expose sandbox ports through public URLs
  • Pause, resume, extend, and destroy sandboxes

Tools29

What E2b Sandbox MCP lets your agent do. Expand a tool for its parameters.

Self-reported~373 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

10/10 checks healthy over the last 80d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 10d ago via OSV.dev · e2b-sandbox-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads67Package downloads in the last 30 days.
Last commit6mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed29Callable tools this server registers over MCP.
Directory activity7 viewsConfig copies, upvotes, and views on AllMCPs.

How E2b Sandbox MCP works

What asif-nvc/e2b-sandbox-mcp MCP server does

The asif-nvc/e2b-sandbox-mcp MCP server connects Claude Code to E2B cloud sandboxes. Each sandbox is an isolated Linux virtual machine where the agent can inspect a repository, install dependencies, run tests, modify files, and interact with Git. These actions take place in the E2B environment rather than on the developer’s local machine.

The server supports disposable experimentation as well as longer-lived sessions. An agent can create several sandboxes for parallel work, pause one while preserving its state, resume it later, or terminate it when the work is complete. It can also expose a port through a public URL for previewing a development server in a browser.

Typical workflows include cloning a GitHub repository, running its build or test commands, investigating failures, applying a change, committing it, and pushing the result. GitHub access tokens can be supplied for private repository access and pushes.

How it works

The asif-nvc/e2b-sandbox-mcp MCP server uses the MCP stdio transport and keeps a registry of active sandbox instances. Tools refer to sandboxes by ID, which allows multiple isolated environments to be used concurrently. The E2B API key authenticates access to the cloud sandbox service.

Command execution returns standard output, standard error, and an exit code. Foreground commands return their results directly, while background commands return a process ID that can later be inspected or terminated. Tool output is structured and capped: each output stream is limited to 100 KB, with a 200 KB combined limit. Directory listings are limited to 1,000 entries.

The environments are real Linux VMs with network access. As a result, Git pushes, network requests, package installation, and similar operations affect external systems as they normally would.

Setup and configuration

The package requires Node.js 18 or newer, Claude Code, and an E2B API key. Register it with Claude Code using the npm package:

Terminal
claude mcp add e2b-sandbox -s user \
  -e E2B_API_KEY=your-e2b-api-key \
  -e GITHUB_TOKEN=your-github-token \
  -- npx -y e2b-sandbox-mcp

E2B_API_KEY is required. GITHUB_TOKEN is optional and is used for private repositories and Git pushes. Restart Claude Code after registering the server.

The package can alternatively be installed globally with npm and launched as e2b-sandbox-mcp, but the npx registration is the documented no-separate-install path.

Tools and capabilities

The asif-nvc/e2b-sandbox-mcp MCP server groups its tools into these areas:

  • Sandbox lifecycle: create, list, inspect, extend, pause, resume, and destroy Linux sandboxes.
  • Commands and processes: run shell commands, start background processes, list processes, and kill processes by PID.
  • Files: read, write, list, create directories, remove, inspect metadata, check existence, and rename or move files.
  • Networking and transfer: obtain a public URL for a sandbox port and presigned upload or download URLs.
  • Git: clone, initialize, inspect status, create or switch branches, commit, pull, and push.

Sandboxes have a default five-minute timeout. The keep-alive operation can extend that timeout, while pause and resume preserve a sandbox for later work. Killing a sandbox destroys it and its current environment.

Limitations and notes

This server does not make sandbox activity private from the internet. Network requests and repository operations remain real, so an agent can affect remote services or repositories if given the relevant credentials. A GitHub token is not required for public repository cloning, but the material only identifies it as optional support for private access and pushing.

E2B billing and sandbox expiration are operational considerations. The default timeout is five minutes, and users should check E2B pricing for usage costs. The server is licensed under MIT.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about E2b Sandbox MCP

Use Node.js 18 or newer and register `npx -y e2b-sandbox-mcp` with Claude Code. Set `E2B_API_KEY`; `GITHUB_TOKEN` is optional.

No. Commands and file operations run inside E2B cloud Linux VMs.

`E2B_API_KEY` is required. `GITHUB_TOKEN` is optional for private repository access and Git pushes.

Yes. Start a background process in a sandbox and use the public URL tool for its port.

Yes. The default timeout is five minutes; the keep-alive tool can extend it.

Related MCP servers

All in Code Execution All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewE2b Sandbox MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/asif-nvc-e2b-sandbox-mcp?style=directory)](https://allmcps.com/mcp/asif-nvc-e2b-sandbox-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/asif-nvc-e2b-sandbox-mcp"><img src="https://allmcps.com/api/badge/asif-nvc-e2b-sandbox-mcp?style=directory" alt="E2b Sandbox MCP on AllMCPs" /></a>