E2B MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Environment (enables file logging in production) | development |
| LOG_LEVEL | No | Logging level (debug, info, warn, error) | info |
| 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_pythonB | Execute Python code in an E2B sandbox environment |
| execute_javascriptB | Execute JavaScript/Node.js code in an E2B sandbox environment |
| create_fileB | Create a file in the sandbox environment |
| read_fileB | Read a file from the sandbox environment |
| list_filesB | List files in a directory in the sandbox environment |
| install_packagesA | Install packages in the sandbox environment (Python pip or Node.js npm) |
| get_sandbox_infoA | Get information about sandbox status and resource usage |
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 7 tools
Each tool targets a clearly distinct operation: executing code by language, managing files, installing packages, or retrieving sandbox metadata. There is no overlap or ambiguity between tool responsibilities.
All tool names use a consistent lowercase snake_case verb-first pattern, such as execute_python, create_file, and list_files. The convention is uniform and predictable across the entire set.
Seven tools is well-scoped for a sandbox execution server, covering code execution, file operations, package installation, and environment introspection without unnecessary redundancy. Each tool earns its place.
The tool surface covers the core sandbox workflow: executing code, managing files, installing packages, and checking sandbox status. Minor gaps like missing delete_file or explicit file update operations exist, but agents can work around them using code execution or existing file writes.