e2b-sandbox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| E2B_API_KEY | Yes | Your E2B API key from https://e2b.dev/dashboard | |
| GITHUB_TOKEN | No | GitHub personal access token for private repo access and git push |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sandbox_createA | Create a new E2B cloud sandbox (secure Linux VM). Returns a sandboxId to use with other tools. |
| sandbox_listA | List all active E2B sandboxes managed by this server. |
| sandbox_infoC | Get details about a specific sandbox. |
| sandbox_killA | Terminate and clean up a sandbox. The sandbox and all its data will be destroyed. |
| sandbox_keep_aliveA | Extend a sandbox timeout to prevent it from being automatically terminated. |
| sandbox_pauseA | Pause a sandbox to preserve its state. The sandbox can be resumed later with sandbox_resume using the same sandbox ID. Paused sandboxes persist across sessions and do not count against timeout. |
| sandbox_resumeA | Resume a previously paused sandbox. Reconnects to the sandbox and restores its state including filesystem and running processes. |
| sandbox_get_urlA | Get the public URL for a port running inside a sandbox. Use this to access dev servers, web apps, or any HTTP service running in the sandbox from a browser. |
| sandbox_upload_urlA | Get a presigned URL to upload a file to the sandbox. Send a POST request with the file as multipart/form-data to the returned URL. |
| sandbox_download_urlA | Get a presigned URL to download a file from the sandbox. Use this to retrieve build artifacts, logs, or any file from the sandbox. |
| sandbox_execA | Execute a shell command in a sandbox and return stdout, stderr, and exit code. Use for running builds, tests, installs, or any CLI command. |
| sandbox_exec_backgroundA | Start a background process in a sandbox (e.g., dev server, file watcher). Returns immediately without waiting for completion. |
| sandbox_process_listA | List all running processes (commands and PTY sessions) in a sandbox. Shows PID, command, and arguments for each process. |
| sandbox_process_killA | Kill a running process in a sandbox by its PID. Use sandbox_process_list to find the PID. |
| sandbox_file_readB | Read the contents of a file in a sandbox. |
| sandbox_file_writeA | Write content to a file in a sandbox. Creates parent directories automatically. Overwrites if file exists. |
| sandbox_file_listC | List files and directories in a sandbox path. |
| sandbox_file_mkdirB | Create a directory (and parent directories) in a sandbox. |
| sandbox_file_removeC | Delete a file or directory in a sandbox. |
| sandbox_file_infoA | Get metadata about a file or directory in a sandbox (size, type, permissions). |
| sandbox_file_existsA | Check if a file or directory exists in a sandbox. Returns true/false without throwing an error if not found. |
| sandbox_file_renameC | Rename or move a file or directory in a sandbox. |
| sandbox_git_cloneA | Clone a GitHub repository into a sandbox. Supports private repos when GITHUB_TOKEN is configured. |
| sandbox_git_statusA | Get the git status of a repository in a sandbox (current branch, modified/staged/untracked files). |
| sandbox_git_commitB | Stage files and create a git commit in a sandbox repository. |
| sandbox_git_pushA | Push commits to a remote repository. Requires GITHUB_TOKEN for authentication. |
| sandbox_git_branchB | Manage git branches: list, create, or switch branches in a sandbox repository. |
| sandbox_git_pullC | Pull latest changes from a remote repository in a sandbox. |
| sandbox_git_initB | Initialize a new git repository in a sandbox directory. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 29 tools
Each tool targets a distinct operation on sandboxes (create, exec, file ops, git, lifecycle management, process control). No overlapping purposes; even similar operations like sandbox_exec vs sandbox_exec_background are clearly differentiated by synchronous vs background execution.
All tools follow the consistent pattern of `sandbox_<action>`, using snake_case. Actions are clear verbs (create, exec, list, kill, etc.). This provides a predictable and intuitive naming scheme.
29 tools is on the higher side but justified by the broad scope of sandbox management (execution, file system, git, process management, lifecycle). The count is reasonable for a comprehensive server, though could be slightly trimmed by merging some rare operations.
The tool set covers the full lifecycle of sandboxes: create, list, info, keep-alive, pause/resume, kill. It includes file operations (CRUD), execution (command + background), process management, git operations (init, clone, branch, status, commit, pull, push), and utilities like download/upload URLs. No obvious gaps for typical sandbox usage.