Sandboxes extension for Jupyter MCP Server (launch/use code-sandboxes code sandboxes as an alternative to Jupyter kernels)
Until 2026-09-26 this record combined several servers published from one repository. The others now have records of their own: jupyter-mcp-spaces, jupyter-mcp-server. Checks from before that date include them.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"jupyter-mcp-sandboxes","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
<!-- ~ Copyright (c) 2024- Datalayer, Inc. ~ ~ BSD 3-Clause License --> [](https://datalayer.io) [](https://github.com/sponsors/datalayer) <div align="center"> <!-- omit in toc --> # 🪐🔧 Jupyter MCP Server Sandboxes Extension </div> `jupyter_mcp_sandboxes` is an optional extension for [jupyter-mcp-server](https://github.com/datalayer/jupyter-mcp-server) that adds sandbox-backed code execution. It is discovered automatically through the `reactor.mcp.extensions` entry point (powered by [`reactor`](https://github.com/datalayer/reactor) and [`reactor_mcp_server`](https://pypi.org/project/reactor-mcp-server/)) once installed. Its four tools are in the `sandboxes` toolset, so a client that wants them and nothing else connects to `/mcp?only=sandboxes`. ## Features Installing this extension exposes four additional MCP tools: - `launch_sandbox` — launch a code sandbox (`eval`, `docker`, `jupyter-server`, `datalayer`, `daytona`, `e2b`, `coreweave`, `cloudflare`, `google-colab`, `kaggle`, `monty`, `modal`). - `list_sandboxes` — list launched sandboxes and their state. - `use_sandbox` — select (or clear) the active sandbox used by `execute_code`. - `terminate_sandbox` — stop and unregister a sandbox. It also lets `SANDBOX_VARIANT` route the standard notebook/cell execution tools through a non-`jupyter` backend via the sandbox's plain kernel client when the selected variant exposes one. ## Installation ```bash pip install jupyter_mcp_sandboxes ``` Backend-specific extras are provided by the underlying [`code-sandboxes`](https://github.com/datalayer/code-sandboxes) package, e.g.: ```bash pip install "code-sandboxes[modal]" # Modal pip install "code-sandboxes" # Google Colab (included in base) pip install "code-sandboxes[kaggle…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.