E2b Sandbox MCP

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:

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. The README states that E2B has a free tier, but sandbox usage can incur charges. 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.