jupyter_mcp_sandboxes is an optional extension for
jupyter-mcp-server that adds
sandbox-backed code execution. It is discovered automatically through the
reactor.mcp.extensions entry point (powered by
reactor and
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 byexecute_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
pip install jupyter_mcp_sandboxes
Backend-specific extras are provided by the underlying
code-sandboxes package, e.g.:
pip install "code-sandboxes[modal]" # Modal
pip install "code-sandboxes" # Google Colab (included in base)
pip install "code-sandboxes[kaggle]" # Kaggle
pip install "code-sandboxes[daytona]" # Daytona
pip install "code-sandboxes[e2b]" # E2B
pip install "code-sandboxes[coreweave]" # CoreWeave
pip install "code-sandboxes[cloudflare]" # Cloudflare
Usage
Once installed, start jupyter-mcp-server as usual — no flag is required. The
sandbox tools appear automatically. To route execute_code through a specific
backend by default, set SANDBOX_VARIANT:
SANDBOX_VARIANT=monty jupyter-mcp-server start --transport streamable-http
License
BSD 3-Clause License. Copyright (c) 2024- Datalayer, Inc.
Metadata
Release files for jupyter-mcp-sandboxes 0.2.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| jupyter_mcp_sandboxes-0.2.7.tar.gz | 23.9 kB | Without provenance | Details for jupyter_mcp_sandboxes-0.2.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jupyter_mcp_sandboxes-0.2.7-py3-none-any.whl | Python 3 | none | any | Details for jupyter_mcp_sandboxes-0.2.7-py3-none-any.whl |
Total release size: 40.5 kB
Release files / jupyter_mcp_sandboxes-0.2.7.tar.gz
| Download URL | jupyter_mcp_sandboxes-0.2.7.tar.gz |
|---|---|
| Size | 23.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7b73d61bd36c832a13b912737ce71f3656dec5af084d8239d8b6c673f1246cc5
|
|
BLAKE2b-256 checksum How to use checksums |
25185e39f49738970198722f11813429d4fbd1a24c48c471ce15c7df118f7992
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.11
|
Release files / jupyter_mcp_sandboxes-0.2.7-py3-none-any.whl
| Download URL | jupyter_mcp_sandboxes-0.2.7-py3-none-any.whl |
|---|---|
| Size | 16.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6fa400221e2c332b3ce1771daf645038ea0ffa8fa8cf82228dfcb6e8cc855880
|
|
BLAKE2b-256 checksum How to use checksums |
37b71dd50fcf04fe63f59b25ae2b20bf63704162bdb022a91d57af7d706fe261
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.11
|
Security for jupyter-mcp-sandboxes 0.2.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.