MCP for agents, a CLI and an API for you

The console, MCP, the CLI and the API, with the same isolated boxes and the same audit log behind them.

Sandboxes › sbx_9a14 › MCP sessionRevoke tool

Claude Code over MCP

Claude Code signed in through your SSO as maya and is driving its own sandbox with the Sandscale MCP tools.

Tool calls
maya signed Claude Code in through Okta14:01
create_sandbox template: python-3.12sbx_9a14
write_file /workspace/repo.tar, 4.2 MBallowed
exec pytest -q2 failed
exec pytest -q42 passed
read_file /workspace/report.xmlallowed
terminate_sandbox sbx_9a14in the audit log
Client
Claude Code
Signed in as
maya@acme.dev
Through
Okta, SAML
Token
for this MCP server only
Tools
create, exec, read, write, terminate
Sandbox
sbx_9a14
Calls
6, all audited

Four ways in, one set of boxes. Use the console at cloud.sandscale.dev, connect a coding agent over MCP, script runs with the CLI, or call the API from your own code. The same isolated machines and the same audit log sit behind all of them. SDKs for TypeScript and Python are coming soon.

FIG 0.1MCP for agents

Claude Code, Codex, Gemini CLI or your own framework.

FIG 0.2CLI for people

The same lifecycle as commands you type or script.

FIG 0.3API for your code

Plain HTTP requests, with output streamed back.

Agents connect
over MCP

Run sandscale mcp and add it to Claude Code, Codex, Cursor or any MCP tool. Claude Code signs in through your SSO as the person running it, and its token works for Sandscale only. Every call acts on the agent’s own sandbox and lands in the audit log.

Gemini CLIsbx_9a17
Summarise last week’s failed builds
sbx_9a17 added to context
create_sandbox
exec · 31 logs read
Claude Codesbx_9a14
Fix the failing payment tests
sbx_9a14 added to context
create_sandbox
exec pytest · 42 passed
waiting for lee@
Codexsbx_9a15
Lint the web app
sbx_9a15 added to context
create_sandbox
exec npm run lint
terminate_sandbox
Your agentsbx_9a19
Run the nightly data check
sbx_9a19 added to context
create_sandbox
exec python check.py

The whole lifecycle
from your terminal

The same things your agent can do, as commands you can type or put in a script: start, copy files, run, pause, resume, open a shell with a short-lived certificate, and reach a port through an authenticated tunnel.

See the CLI →
Terminal
01$ sandscale up --template python-3.12
02sbx_9a14 running python-3.12 2 vCPU us-east
03$ sandscale cp ./repo sbx_9a14:/workspace
04$ sandscale exec sbx_9a14 -- pytest -q
0542 passed in 3.1s
06$ sandscale pause sbx_9a14
07paused, memory and files kept
08$ sandscale ssh sbx_9a14
09certificate valid for 15:00

Plain HTTP
from your own code

Call api.sandscale.dev with an API key or your own sign-in: create a sandbox, run a command and read its output as it streams. Anything you can do in the console, you can do with a request. SDKs for TypeScript and Python are coming soon.

Read the docs →
Request
01POST /v1/sandboxes
02Authorization: Bearer $SANDSCALE_TOKEN
03{ "template": "python-3.12" }
04
05POST /v1/sandboxes/sbx_9a14/exec
06{ "cmd": ["pytest", "-q"] }
Response
01201 Created
02{ "id": "sbx_9a14", "state": "running" }
03
04200 OK · streamed
05{"stream":"stdout","data":"42 passed"}
06{"exit_code":0}

Identity and
your own cloud

Sign in with SAML or OpenID Connect on Team. On Enterprise, keep members in step with your directory over SCIM and run Sandscale workers in your own AWS account; Azure and Google Cloud are coming soon.

See security →
Identity and your own cloud
What it doesPlan
SAML and OpenID ConnectEntra ID, Okta, Google Workspace or any standard providerTeam
Roles and groupsWho can start, see and stop whatTeam
SCIMMembers follow your directoryEnterprise
Your own AWSSandscale workers in your accountEnterprise
Azure, Google CloudComing soonEnterprise
Lab hostsYour Linux and macOS machines and devicesTeam

Connect your agent
in a minute

Start free with 100 vCPU-hours a month. Upgrade when your agents need more.

A Firecracker microVM for every runNo network by defaultPause and resume with state keptVault keeps secrets out of promptsSSO, roles and audit logBring your own cloudWorks over MCP and the CLI