Skip to main content
@stateset/sandbox-mcp is the Sandbox control surface for MCP clients. It uses the TypeScript SDK. The commerce-provider servers in the repository’s separate mcp-servers/ directory operate their own external systems; they are not the Sandbox runtime server.

​
Build and connect

The reviewed Sandbox MCP source is 0.3.0. Its guide records npm publication as pending; use the checkout build until the intended package release is confirmed:
Use supported Node 20.19+ or 22.12+ and configure the client with an actual absolute path:
Keep the key in the host’s secret configuration. The API origin omits /api/v1. STATESET_ORG_ID supports configured multi-org JWT selection; it cannot grant authorization. The server uses stdio, so a web URL is not its executable command.

​
Discover capabilities

Discover tools/list and inspect input schemas on the actual server; catalog counts and client versions do not establish deployed feature support. Registry needs migration 067 and independent sandbox access. Embedded server callers must explicitly enable supported registry mutations; stdio entry point behavior is documented in its source guide.

​
Preserve identities and outcomes

Prepared tasks retain private launch receipts; configure absolute private journal/input/result roots when sharing a parent workspace between MCP, CLI and TUI. A fresh registry observer can discover permitted workers without those files, but cannot recover every private control or artifact receipt. Registration launches no worker. Read status/process evidence and validate task artifacts independently of a zero exit. code_run preserves Python state through its supported Jupyter kernel; script/fallback mode uses a fresh process and reports that boundary. Stop/pause/recovery can destroy kernel memory. Process streams retain bounded output and uncertain outcomes; a reconnect does not justify submitting the command again. STATESET_MCP_STOP_ON_EXIT defaults to false because hosts reconnect/restart servers. When enabled, cleanup is bounded and applies only to sandboxes this process created; it is not a guarantee of completed teardown. Runtime lifetime and external provider charges remain separate. Verify cleanup against the same identities. Source: mcp-sandbox/README.md, docs/guides/MCP_SANDBOX_SERVER.md, and server/tool modules, checked at 67bc2370 on October 20, 2026. Continue with prepared tasks, workbench, or execution recovery.
Last modified on October 20, 2026