jupyter_mcp
Provides tools for creating, editing, and executing Jupyter notebooks via an MCP interface, including cell management, dependency tracking, and output condensation.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@jupyter_mcprun stale cells in data_analysis.ipynb"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
jupyter-mcp
Kernel-attached MCP server for Jupyter EDA workflows. Built for coding agents that iterate on notebooks: named cells, a dependency DAG, minimal re-execution, condensed outputs, and cheap LLM summaries for navigation.
Why
Editing notebooks through generic file tools is painful for agents:
cells have no stable, human-meaningful addresses
every change means re-executing the whole notebook from scratch
raw outputs (box-drawn tables, base64 charts, ANSI noise) flood context
nothing tells you which cells a change invalidates
This server fixes each of those with an opinionated data model.
Related MCP server: Jupyter MCP Server
Concepts
Concept | What it means |
Cell names | Every cell has a unique kebab-case name stored in |
Revisions | Each cell has a short content hash ( |
Dependency DAG | A static AST pass (not runtime tracing) extracts per-cell defines/uses/mutations and builds last-writer-wins edges. Works on unexecuted cells, which is the whole point: edit first, then |
Staleness | A cell is fresh only if its current source ran on the currently live kernel (freshness is stamped with a per-kernel epoch). Source edits make a cell and its dependents stale; a new or restarted kernel makes everything stale — persisted metadata can never claim freshness against empty kernel state. |
Background execution | Every run goes through a per-notebook executor thread. |
Condensed outputs | Streams merged, ANSI stripped, long text truncated head+tail with explicit markers. Duplicate table reprs collapse to one: uniform → CSV, ragged → JSON. Charts return as real MCP images (downscaled), so the agent sees them. |
Summaries | Lazy, batched |
Snapshots / undo | Every mutation snapshots the file first (under |
Tools
Tool | Purpose |
| New empty notebook |
| Index: names, revs, staleness, tldrs, edges, lint |
| Full cells (code + condensed outputs + images), by names/slice |
| Mutations; all take |
| Default: all stale cells (minimal recompute). With |
| Stop the running cell (KeyboardInterrupt), cancel the queue |
| Fresh kernel; marks everything stale |
| Type/shape/schema of a live variable plus its richest repr: dataframes as CSV, figures as images, else pretty repr |
| Restore pre-mutation snapshot |
| Detailed LLM summaries incl. outputs |
| Search source + names + summaries |
Setup
uv syncRegister with Claude Code (.mcp.json in any project, or globally):
{
"mcpServers": {
"jupyter": {
"command": "uv",
"args": ["run", "--project", "/path/to/jupyter_mcp", "jupyter-mcp"]
}
}
}The server is multi-notebook: every tool takes a notebook path, one kernel
per notebook, started lazily in the notebook's directory (so relative data
paths behave like in your editor). Kernelspec comes from the notebook's
metadata, falling back to python3. Kernels idle longer than 30 minutes are
shut down lazily (JUPYTER_MCP_KERNEL_TTL_SECONDS overrides); the next
execution restarts them, and epoch-scoped staleness handles the rest. On
POSIX, kernels connect over IPC sockets (no open TCP ports).
Summaries & credentials
Summaries use the plain anthropic SDK: credentials resolve from
ANTHROPIC_API_KEY or an ant auth login profile automatically. Cost is
negligible (Haiku, batched, hash-cached). To disable entirely set
JUPYTER_MCP_DISABLE_SUMMARIES=1 — everything else works unchanged.
Development
uv run pytest # full suite
uv run pytest -m "not kernel" # skip real-kernel integration testsLayout: src/jupyter_mcp/ is a plain library (model, dag, condense, kernel,
summaries, session) with the MCP surface isolated in server.py; everything
below the server is unit-testable without MCP.
Known limitations (v1)
The DAG is static: dynamic patterns (
globals()[name] = ...,exec, attribute mutation through aliases) are invisible. Method calls only count as mutations for a known allowlist (append,fit, ...) — pure-functional chains (polars) intentionally create no false forward edges.%%bash/%%sqlstyle cells are treated as opaque (no dependencies).Concurrent edits from a live Jupyter editor are detected (the server reloads and rejects the mutation) but not merged.
See docs/ROADMAP.md for what's deliberately deferred — including the phase-2 OKF knowledge base.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Liu-Eroteme/jupyter_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server