# Agent Sandbox > Agent-Sandbox is an E2B compatible easy-to-use enterprise-grade sandboxes for AI Agents. Allows Agents to securely run untrusted LLM-generated Code, Browser use, Computer use, and deploy Website etc. - **Type:** MCP server - **Install:** `agentstack add mcp-agent-sandbox-agent-sandbox` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [agent-sandbox](https://agentstack.voostack.com/s/agent-sandbox) - **Installs:** 0 - **Category:** [Cloud & Infrastructure](https://agentstack.voostack.com/c/cloud-infrastructure) - **Latest version:** 0.1.0 - **License:** Apache-2.0 - **Upstream author:** [agent-sandbox](https://github.com/agent-sandbox) - **Source:** https://github.com/agent-sandbox/agent-sandbox - **Website:** https://agent-sandbox.github.io ## Install ```sh agentstack add mcp-agent-sandbox-agent-sandbox ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About Agent-Sandbox is an open-sourced Blaxel Sandbox or E2B like solution! 🎉🎉🎉 Complete compatible with E2B protocol and SDKs.✅ Agent-Sandbox is an enterprise-grade ai-first, cloud-native, high-performance runtime environment designed for AI Agents. It combines the Kubernetes with container isolation. Allows Agents to securely run untrusted LLM-generated Code, Browser use, Computer use, and Shell commands etc. with stateful, long-running, multi-session and multi-tenant. UI path is https://agent-sandbox.domain.com/ui Default UI admin login token: sys-2492a85b10ed4cb083b2c76b181eac96 Your browser does not support the video tag. Agent Use Sandbox Demo --- # Why Agent-Sandbox? When we are developing AI Agents, one of the critical challenges is providing an Enterprise-Grade&Production-Grade environment for executing untrusted code and performing various tasks, that is **Multi-Session and Multi-Tenant**. Sandbox must be isolated on a **Per-Agent** even **Per-User** basis to ensure security and prevent interference **between different conversation or task**. Additionally, the sandbox environment should support state persistence, allowing agents to maintain context and data across multiple interactions or multi agents etc. Therefore, **Multi-Session and Multi-Tenant** is very critical, Each sandbox is isolated on a per-agent or per-user basis, ensuring security and preventing interference between different conversations or tasks. I found [kubernetes-sigs/agent-sandbox](https://github.com/kubernetes-sigs/agent-sandbox) leverages [AIO Sandbox](https://github.com/agent-infra/sandbox) and Kubernetes to provide a similar solution. But it seems not friendly for AI Agents to manage the sandbox lifecycle and not friendly for commonly users to use it, because it faces to Kubernetes directly. So, We decide created this **Agent-Sandbox** project, which provides a RESTful API and MCP(Model Context Protocol) server to manage the sandbox lifecycle easily. It abstracts the complexity of Kubernetes and provides a simple interface for AI Agents and users to create, access, and delete sandboxes as needed. And we refer to some design ideas from [Blaxel Sandbox](https://docs.blaxel.ai/Sandboxes/Overview) and [E2B](https://e2b.dev/) provide similar features like lifecycle management and API design. Making it more suitable for AI Agents to use, but is opensource and self-hosted. ## Full sandbox lifecycle manage by Agent-Sandbox MCP Server ## Architecture ```mermaid flowchart TD A1([Agent A]):::agent -->|Execute Code| ASB A2([Agent B]):::agent -->|Browse Web| ASB A3([Agent C]):::agent -->|Terminal Access| ASB(Agent-Sandbox Auto CRUD Sandboxes) A4([Agent ...]):::agent -->|...| ASB ASB -->SB1{{Code Sandbox}} ASB -->SB2{{Browser Sandbox}} ASB -->SB3{{Computer Sandbox}} ASB -->SB4{{Customized Sandbox}} SB1 |File R/W| V SB2 |State Persistence| V SB3 |Shared Storage| V SB4 V[Unified Storage NAS / OSS / S3] V --- K[Kubernetes Cluster] style ASB fill:#bd3cfe,stroke:#333,stroke-width:0,color:#fff; classDef agent fill:#f9f,stroke:#333,stroke-width:3px; ``` # Features - **🎉 E2B Fully-Compatible** - Fully compatible with [E2B](https://e2b.dev/) protocol and SDKs, allowing seamless integration with existing E2B-based AI Agents and tools, please refer to usage in `examples/` directory. - **Ai-First** - Agents automatically manage whole Sandbox's lifecycle by the MCP( Model Context Protocol ) , making it easy to manage various Sandbox environments and access them automatically. - **AI-Agent Runtimes** - Supports various AI agent runtimes, including code execution, browser automation, computer use, and shell command execution and easy to customize more runtimes. - **Enterprise-Grade** - Support multiple Sandbox lifecycle manage for each tenant or session, allowing Agents to run different tasks simultaneously without interference for different tenant or session. - **Cloud-Native** - Leverages Kubernetes built to run in cloud environments, leveraging the benefits of cloud infrastructure such as scalability, flexibility, resilience and efficient resource management. - **Fast and Lightweight** - Designed to be lightweight and fast, minimizing Kubernetes's objects to deploy. easy to use and maintain. # Quick Start ## 1, Installation You can install Agent-Sandbox by applying the provided [install.yaml](https://github.com/agent-sandbox/agent-sandbox/blob/main/install.yaml) file to your Kubernetes cluster. requires **Kubernetes version 1.26** or higher. ```bash kubectl create namespace agent-sandbox kubectl apply -nagent-sandbox -f install.yaml ``` You can create an ingress or port-forward to access the Agent-Sandbox API server. Ingress like this: ```yaml apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: agent-sandbox namespace: agent-sandbox spec: ingressClassName: ingress-nginx rules: - host: agent-sandbox.your-host.com http: paths: - backend: service: name: agent-sandbox port: number: 80 path: / ``` Now you can access the Agent-Sandbox API server at `http://agent-sandbox.your-host.com`. ## 2, Usage The Agent-Sandbox provides a RESTful API or MCP to manage sandboxes. The typical workflow involves creating a sandbox, accessing it, and then deleting it when no longer needed. ```mermaid flowchart LR A[Create Sandbox] -->|mcp ro restful api| B(Access Sandbox)-->|mcp or timeout or restful api| C[Delete Sandbox] ``` ### 2.1, Use Agent-Sandbox MCP Server You can manage sandboxes using the Model Context Protocol (MCP) with your AI Agents. The MCP server allows Agents to create, access, and delete sandboxes automatically. MCP Server Address: `http://agent-sandbox.your-host.com/mcp`. Now support SSE(Streamable-http). #### MCP Demos: ##### 1, Code Execution Agents automatically create a sandbox when code needs to be executed and delete it when execution completes, ensuring isolated and secure code runs. [code execution](https://github.com/user-attachments/assets/d6ee410f-e12c-4c40-9dcc-f16b3b1abade) ##### 2, Browser Use Agents automatically create a sandbox when website access is needed and delete it when the task is finished, providing isolated browser sessions for web interactions. [browser use](https://github.com/user-attachments/assets/e75daeb0-2bce-4144-9c2e-9c7979c21a05) This MCP integration enables agents to manage sandbox resources without manual intervention, supporting multi-session and multi-tenant operations with automatic cleanup. --- ### 2.2, Use RESTful API You can also manage sandboxes manually using the RESTful API provided by Agent-Sandbox. #### I, Create a Sandbox You can create a new sandbox by sending a POST request to the `/api/v1/sandbox` endpoint with the desired configuration. For example, to create an `aio` sandbox and name it `sandbox-01`, you can use the following curl command or programmatically call the API: **Shell** ```shell curl --location '/api/v1/sandbox' \ --header 'Content-Type: application/json' \ --data '{"name":"sandbox-01"}' ``` for China user, please specify the local aio image registry to improve the pull speed: ```shell curl --location '/api/v1/sandbox' \ --header 'Content-Type: application/json' \ --data '{"name":"sandbox-01","image":"enterprise-public-cn-beijing.cr.volces.com/vefaas-public/all-in-one-sandbox:latest"}' ``` **Python** ```python import requests import json url = "/api/v1/sandbox" payload = json.dumps({ "name": "sandbox-01" }) headers = { 'Content-Type': 'application/json' } response = requests.request("POST", url, headers=headers, data=payload) print(response.text) ``` **Result** ```json { "code": "0", "data": "Sandbox sandbox-01 created successfully" } ``` #### II, Access to Sandbox `/sandbox/{sandbox_name}` endpoint to get the access of the sandbox, including the connection details such as URL, WebSocket URL, VNC URL, or other relevant information based on the sandbox template. Now you can access to the previously created **sandbox-01** sandbox using `/sandbox/sandbox-01`. **You will see:** **Use agent sandbox SDK access this sandbox:** ```python from agent_sandbox import Sandbox # Initialize client client = Sandbox(base_url="http://agent-sandbox.your-host.com/sandbox/sandbox-01") home_dir = client.sandbox.get_context().home_dir # Execute shell commands result = client.shell.exec_command(command="ls -la") print(result.data.output) # File operations content = client.file.read_file(file=f"{home_dir}/.bashrc") print(content.data.content) # Browser automation screenshot = client.browser.screenshot() ``` And this created Sandbox's MCP Server address is: `/sandbox/sandbox-01/mcp`. you can use this MCP Server with your AI Agent to access this sandbox. For more usage, please refer to: https://github.com/agent-infra/sandbox #### III, Delete a Sandbox You can delete a sandbox by sending a DELETE request to the `/api/v1/sandbox/{sandbox_name}` endpoint. For example, to delete the `sandbox-01` sandbox, you can use the following curl command or programmatically call the API: **Shell** ```shell curl --location --request DELETE '/api/v1/sandbox/sandbox-01' ``` **Python** ```python import requests url = "/api/v1/sandbox/sandbox-01" headers = { 'Content-Type': 'application/json' } response = requests.request("DELETE", url, headers=headers) print(response.text) ``` **Result:** ```json { "code": "0", "data": "Sandbox sandbox-01 deleted successfully" } ``` # License [Apache License](./LICENSE) ## Source & license This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [agent-sandbox](https://github.com/agent-sandbox) - **Source:** [agent-sandbox/agent-sandbox](https://github.com/agent-sandbox/agent-sandbox) - **License:** Apache-2.0 - **Homepage:** https://agent-sandbox.github.io Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** yes - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/mcp-agent-sandbox-agent-sandbox - Seller: https://agentstack.voostack.com/s/agent-sandbox - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.