E2B MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| E2B_API_KEY | Yes | Your E2B API key |
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 |
|---|---|
| e2b_list_sandboxes_v2C | List sandboxes (v2). |
| e2b_create_sandboxD | Create a sandbox from a template. |
| e2b_connect_sandboxB | Connect to a sandbox. If paused, resumes it and returns fresh sandbox details. |
| e2b_delete_sandboxC | Kill/delete a sandbox permanently. |
| e2b_pause_sandboxB | Pause a running sandbox so it can be resumed later. |
| e2b_set_sandbox_timeoutA | Set the sandbox timeout: it will expire N seconds from now. Overwrites any previous TTL. |
| e2b_refresh_sandboxB | Refresh a sandbox, extending its time to live. |
| e2b_get_sandbox_logsC | Get structured logs for a sandbox (v2 endpoint), with pagination/filtering. |
| e2b_get_templateD | Get a template and its builds. |
| e2b_get_template_by_aliasB | Check whether a template with the given alias/name exists and get its id. |
| e2b_list_dirC | List the contents of a directory in a sandbox. |
| e2b_make_dirC | Create a directory in a sandbox (including parent directories). |
| e2b_moveB | Move or rename a file/directory in a sandbox. |
| e2b_removeC | Remove a file or directory in a sandbox. |
| e2b_statB | Get metadata (type, size, permissions, owner, mtime...) about a file or directory in a sandbox. |
| e2b_read_fileC | Read a file from a sandbox. Returns its content as UTF-8 text or base64. |
| e2b_upload_fileA | Upload/write a file into a sandbox, creating parent directories as needed. Overwrites if it already exists. |
| e2b_run_commandB | Run a command in a sandbox and wait (up to timeoutMs) for it to finish, returning collected stdout/stderr/exit status. Uses the streaming process.Process/Start RPC under the hood. |
| e2b_list_processesB | List running processes started via envd in a sandbox. |
| e2b_send_signalA | Send SIGTERM or SIGKILL to a process running in a sandbox, selected by pid or tag. |
| e2b_send_stdinA | Send input to the stdin of a running process, selected by pid or tag. Note: field names are inferred from the related Start/SendSignal schemas; if this errors, check the E2B docs for the exact process.Process/SendInput request shape. |
| e2b_close_stdinB | Close stdin (send EOF) for a non-PTY process running in a sandbox, selected by pid or tag. |
| e2b_resize_ptyB | Resize the PTY of a running process (cols/rows), selected by pid or tag. Note: shape inferred from process.PTY.Size; verify against E2B docs (api-reference/process/update) if it errors. |
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 23 tools
Most tools clearly target distinct resources and actions, but a few overlap: refresh_sandbox and set_sandbox_timeout both adjust TTL, and get_template vs get_template_by_alias are similar. Overall, the purposes are still largely separable.
All tools share the e2b_ prefix and snake_case verb_noun structure, making the set predictable. Minor deviations include list_sandboxes_v2 vs get_sandbox_logs, and make_dir vs create_sandbox, but these do not seriously harm usability.
23 tools is on the heavy side and spans sandboxes, templates, filesystems, and process control. The count is defensible given the breadth, but it starts to feel large for an agent to scan.
Sandbox lifecycle, filesystem, and process interaction are well covered. The main gap is template management: only get operations exist, with no create/update/delete template tools, though this may be intentionally outside the server's scope.