Sandbox as a Service
Give an AI agent an isolated Linux VM: create a sandbox, run commands, transfer files, expose an HTTPS preview, and destroy it when finished.
Community: Submitted by a user or imported; check the owner before granting accessOnlineAPI key requiredGlobalFreeCan modify data
What it can do
- Create Sandbox: Create an isolated cloud sandbox — a dedicated virtual machine you can run commands in. Returns once the sandbox is ready. Python 3, Node.js 22, git and a build toolchain are pre-insta
- Run Command: Run a shell command inside a sandbox and wait for it to finish. Returns stdout, stderr and the exit code. The command runs as an unprivileged user in /workspace. A non-zero exit code is r
- Write File: Write a file inside a sandbox. Use this to place a script or input data before running it. Paths are relative to /workspace unless absolute. Content of any kind is safe — it is transferred
What data it sees
Do you need an account
An API key from the service settings is required
Give an AI agent an isolated Linux VM: create a sandbox, run commands, transfer files, expose an HTTPS preview, and destroy it when finished. Connect remotely over Streamable HTTP using your own Sandbox as a Service API key; no local MCP installation required. Public service information is available without a key. Account and execution tools require authentication. VM runtime uses your account credit; startup time depends on capacity. See the homepage for current pricing and limits.
Server tool list (12)
Raw names from tools/list. Only developers need these.
| create_sandbox | Create an isolated cloud sandbox — a dedicated virtual machine you can run commands in. Returns once the sandbox is ready. Python 3, Node.js 22, git and a build toolchain are pre-installed. The sandbox is destroyed automatically after timeout_minutes; nothing inside it survives that. Use this before running any code you would not want to run on the local machine. |
| run_command | Run a shell command inside a sandbox and wait for it to finish. Returns stdout, stderr and the exit code. The command runs as an unprivileged user in /workspace. A non-zero exit code is returned normally, not as an error. Use this to execute code, install packages, clone repositories or inspect the filesystem. To start something that keeps running (a web server), background it with `&` AND pass `cwd` instead of writing `cd ... &&` — a `&` after a `&&` list backgrounds a subshell that holds the output stream open, so the call waits out the whole timeout and returns exit_code 124. The process survives either way; only the waiting is wasted. |
| write_file | Write a file inside a sandbox. Use this to place a script or input data before running it. Paths are relative to /workspace unless absolute. Content of any kind is safe — it is transferred verbatim, not interpreted by a shell. |
| read_file | Read a file back out of a sandbox — an artifact your code produced, a log, a generated report. Use encoding "base64" for binary files such as images. |
| list_files | List the contents of a directory in a sandbox, with the type and size of each entry. Defaults to /workspace. Use this to find what your code produced before reading it. |
| expose_port | Give a server running inside the sandbox a public https URL, so a person can open it in a browser. Use this after starting a web server or dev server in the background with run_command (background it with `&` and pass `cwd` rather than `cd ... &&`). The server only needs to listen on localhost. Returns a URL that works until the sandbox is destroyed. |
| get_sandbox | Get the current status and details of one sandbox, including when it expires. |
| list_sandboxes | List the sandboxes on this account, newest first. Use it to find sandboxes you created earlier. |
| extend_sandbox | Push a sandbox’s expiry further out so long-running work is not cut off. Total lifetime is still capped at 24 hours from creation. |
| destroy_sandbox | Destroy a sandbox and stop billing for it. Everything inside is lost. Call this as soon as you are finished — do not leave sandboxes running. |
| get_usage | Show the account’s remaining credit balance and recent sandbox usage. |
| get_service_info | Describe this service: what a sandbox costs, which machine sizes exist, the account limits, and where to get an API key. Free — it never provisions anything and is not charged for. Every other tool here needs an API key and acts on the account that key belongs to. |