| FMRS | 65 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 10 / 20 | 12 / 20 |
|---|
| Security and permissions | 12 / 20 | 16 / 20 |
|---|
| Maintenance | 13 / 20 | 18 / 20 |
|---|
| Documentation | 15 / 20 | 18 / 20 |
|---|
| Setup experience | 15 / 20 | 15 / 20 |
|---|
| Best for | - Users already running a local JupyterLab or JupyterHub who want to attach an AI agent
- Data science and machine learning workflows needing multimodal output (images, plots, text)
- Teams wanting to extend code execution from local to cloud sandboxes such as Datalayer, Kaggle or Google Colab
- Users who want notebook sessions to keep running after the agent disconnects
| - Developers auditing NPM dependencies within AI workflows
- Teams performing supply chain security assessments
- Users of Claude Desktop, Cursor, or VS Code
|
|---|
| Not for | - Users who do not run any Jupyter Server and do not need Jupyter Notebooks
- Users whose LLM or client cannot handle multimodal image output and who do not want to disable ALLOW_IMG_OUTPUT
- Users who need cloud sandbox variants without network access or the required credentials
| - Projects outside the NPM ecosystem (e.g., pure Python/Go)
- Environments without network access to deps.dev, OSV.dev, and the npm registry
- Scenarios requiring maintenance by an official upstream vendor
|
|---|
| Required permissions | - Access to the Jupyter Server URL (JUPYTER_URL / DOCUMENT_URL / CODE_SANDBOX_URL)
- The Jupyter access token (JUPYTER_TOKEN, or DOCUMENT_TOKEN and CODE_SANDBOX_TOKEN separately)
- Permission to read and write notebook documents and execute code
- Vendor credentials when using cloud sandboxes (e.g. DAYTONA_API_KEY, E2B_API_KEY, CWSANDBOX_API_KEY, CLOUDFLARE_SANDBOX_API_URL / CLOUDFLARE_SANDBOX_API_KEY, Kaggle credentials, Modal credentials)
- Optional OAuth 2.1 scopes with Datalayer hosting: notebooks:read, notebooks:write, code:execute, data:read
| - Network access to the NPM registry and external services (deps.dev, OSV.dev, OpenSSF, npms.io, GitHub)
- Read access to workspace lockfiles (pnpm-lock.yaml, package-lock., yarn.lock) for cache invalidation
|
|---|
| Risks and side effects | - The AI agent can execute arbitrary code in notebooks, which may lead to data leakage, data corruption or resource abuse
- A leaked token grants the same Jupyter access as the token itself
- Starting JupyterLab with --ip 0.0.0.0 by default widens the network exposure surface
- Cloud sandboxes incur vendor-side costs and may run beyond local resource limits
- A version mismatch between jupyter-mcp-server and code-sandboxes fails on first execution with Unknown sandbox variant: jupyter
| - Third-party READMEs and changelogs are untrusted external content; they are wrapped in tags with _meta flags but should still be handled cautiously
- Depends on availability and accuracy of external services
- Batch requests are capped at 25 packages to prevent registry enumeration; larger sets require batching
- Third-party open source project, not officially maintained by NPM or Anthropic
|
|---|
| Supported clients | Claude Desktop, Cursor, Windsurf, VS Code, Cline, Claude Code | Claude Desktop, VS Code, Cursor |
|---|
| Tools | 6 | 19 |
|---|