Developer Tools

pilldrops.com

This MCP server manages cloud sandboxes for development and testing, allowing users to create, list, inspect, and run commands in isolated environments.

1 endpoint18 known toolsFirst detected August 5, 2026Last detected August 5, 2026

ENDPOINT 1

https://pilldrops.com/mcp

No auth detected

MCP server metadata

Name: pilldrops
Version: 1.8.1

Capabilities

tools

Server instructions

PillDrops gives agents disposable cloud sandboxes. Typical flow: create_sandbox (template python-3.11) → write_file / run_command → read output → destroy_sandbox. App servers: create_sandbox with start+ports (the app MUST bind the injected $PORT env var) → the returned url is a public preview. Debug with get_logs / get_metrics; past sandboxes (with cost) via the CLI `pilldrops history`.

Known tools 18

list_templates

List available sandbox templates (python-3.11, node, playwright, …) with their default resources.

Inferred read-only

create_sandbox

Create an isolated cloud sandbox.

Potential side effects

list_sandboxes

List active sandboxes: id, template, status.

Inferred read-only

get_sandbox

Inspect one sandbox: status, resources, preview url when it serves an app.

Inferred read-only

run_command

Run a shell command in the sandbox and get {stdout, stderr, exit_code}.

Potential side effects

start_server

Potential side effects

write_file

Write text content to a file in the sandbox workspace (path is relative to the workspace root; parent dirs are created).

Potential side effects

read_file

Read a file from the sandbox workspace and return its content as text.

Inferred read-only

get_logs

Fetch recent sandbox logs (start command + service output) — the first stop when an app misbehaves or a preview 502s.

Potential side effects

get_metrics

Live CPU/memory of a sandbox — spot OOMs and busy loops.

Inferred read-only

pause_sandbox

Pause a sandbox: billing stops, state is kept.

Inferred read-only

resume_sandbox

Resume a paused sandbox (also relaunches its registered start_server command).

Potential side effects

get_events

Recent lifecycle events for the org, newest first: created/paused/resumed/destroyed and `oom` (a process was out-of-memory-killed inside a sandbox).

Inferred read-only

wait_ready

Block until the sandbox's app answers on a port (or timeout), by probing 127.0.0.1:<port> from inside the sandbox.

Inferred read-only

destroy_sandbox

Destroy a sandbox and stop billing.

Potential side effects

get_usage

Account usage and charges — current consumption vs plan limits.

Inferred read-only

verify

Run an agentic browser verification: URL + plain-English goal (or a Playwright spec) → a sandbox that produces a pass/fail verdict with video.

Inferred read-only

verify_status

Poll a verify sandbox's status.json for its verdict: {state, verdict, exit, videos, trace, report}.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.pilldrops]
url = "https://pilldrops.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "pilldrops": {
      "type": "http",
      "url": "https://pilldrops.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: pilldrops
Remote MCP URL: https://pilldrops.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "pilldrops": {
      "url": "https://pilldrops.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "pilldrops": {
      "type": "http",
      "url": "https://pilldrops.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "pilldrops",
  "transport": "streamable-http",
  "url": "https://pilldrops.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for pilldrops.com was fetched 2026-08-24T05:54:29.418Z.

Trust status Trusted

pilldrops.com is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.