PillDrops ships a hosted, OAuth-secured MCP server with 70+ tools that spin up microVM sandboxes and run real code. Add one line — no repo to clone, no Docker to babysit — and your agent can create a sandbox, run commands, and read metrics.
Zero install · OAuth on first call · works with Claude, Cursor, any MCP client
$ claude mcp add --transport http pilldrops https://pilldrops.com/mcp Added HTTP MCP server 'pilldrops' — auth on first call # agent calls a tool → OAuth (PKCE) in the browser once → done > create_sandbox(template="python-3.11") { id: "sb_9f21", status: "ready" } # 180ms > run_command(id="sb_9f21", cmd="python -c 'print(2+2)'") { stdout: "4\n", exit_code: 0 } ✓ code executed in a real microVM · billed per second
Create a sandbox, move files in and out, run commands, start a server, read logs and metrics, then pause or destroy it. The full lifecycle — no glue code, no DIY Docker wrapper to maintain.
create_sandbox boots an isolated sandbox from a template; run_command executes a shell command and returns stdout, stderr, and exit_code.
write_file and read_file put data in and pull results out — datasets, scripts, artifacts — without leaving the tool call.
start_server exposes a public preview URL; get_logs and get_metrics stream output and CPU/memory back to the agent.
pause freezes state (storage-only billing), resume picks it back up, and destroy_sandbox tears it down.
list_sandboxes shows what's running and list_templates shows what you can boot — python-3.11, node-20, code-interpreter, and more.
get_usage reports vCPU-seconds, GB-seconds, and cost so the agent — and you — can attribute spend per run. Metering guide →
The hosted transport is the zero-setup path: one line, OAuth on first call, nothing to install. Run it locally against your own binary, or wire it into CI with a bearer token.
Point any MCP client at the hosted endpoint. The first tool call opens a browser for OAuth (PKCE); after that it just works.
$ claude mcp add --transport http pilldrops https://pilldrops.com/mcp
Run the MCP server on your machine over stdio via the PillDrops CLI — handy for air-gapped or self-hosted setups.
$ claude mcp add pilldrops -- pilldrops mcp
In non-interactive environments, skip the browser flow and pass an API key as a header so pipelines can run code in sandboxes.
$ claude mcp add --transport http pilldrops https://pilldrops.com/mcp \ --header "Authorization: Bearer <api-key>"
The server speaks the Model Context Protocol, so the same 70+ tools show up in Claude, Cursor, or any client that speaks MCP over HTTP or stdio. Machine-readable capabilities live at /llms.txt.
Add over HTTP with claude mcp add --transport http, authorize once, and the tools appear inline for the model to call.
Register the same hosted endpoint in Cursor's MCP config — no separate build, same OAuth flow, same toolset.
Standard MCP over HTTP or stdio means custom agents and other clients connect the same way. MCP reference → · /llms.txt →
One command adds a hosted, OAuth-secured MCP server with 70+ tools for running real code in isolated microVMs. No repo to clone, no Docker to maintain. Try it on $5 of free credits — no card.