Skip to main content
Glama
feifeigood

code-sandbox-mcp

by feifeigood
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
E2B_DOMAINYesYour E2B domain
E2B_API_KEYYesYour 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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
create_sandboxA
Create a new E2B sandbox and return its ID.

Args:
    timeout: Timeout for the sandbox in seconds, default is 300 seconds
    template: Optional template name or ID to use for creating the sandbox. If not provided, the default template is used.

Returns:
    JSON string containing the sandbox ID
kill_sandboxA
Kill an E2B sandbox by its ID.

Args:
    sandbox_id: The ID of the sandbox to kill
    
Returns:
    JSON string containing error message if failed, empty string if successful
run_commandA
Run a shell command in an E2B sandbox.

Args:
    command: Shell command to execute
    sandbox_id: Optional sandbox ID to connect to an existing sandbox. If not provided, a new sandbox will be created.

Returns:
    JSON string containing stdout, stderr, and exit code from command execution
run_codeA
Run python code in a secure sandbox by E2B. Using the Jupyter Notebook syntax.

Args:
    code: Python code to execute
    sandbox_id: Optional sandbox ID to connect to an existing sandbox. If not provided, a new sandbox will be created.
    
Returns:
    JSON string containing stdout and stderr from code execution

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 4 tools

Disambiguation4/5

Each tool has a clear primary purpose, but run_command and run_code can implicitly create sandboxes, which overlaps with create_sandbox's role. Descriptions are clear enough to avoid confusion, but the optional sandbox_id in both creates some ambiguity about which tool to use for sandbox creation.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern: create_sandbox, kill_sandbox, run_command, run_code. This makes the API predictable and easy to navigate.

Tool Count4/5

Four tools is slightly on the small side but well-matched to the server's narrow scope of sandbox lifecycle management and code execution. It falls within the typical well-scoped range, though one or two additional tools (e.g., list_sandboxes) would be reasonable.

Completeness2/5

The tool set has a significant lifecycle gap: run_command and run_code can create sandboxes implicitly but do not return the sandbox ID, making those sandboxes impossible to kill or reuse. There is also no way to list active sandboxes or check their status, limiting operational visibility and control.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources