nbclassic frontend extension + relay server extension bridging the classic Notebook to an MCP server
Until 2026-09-24 this record combined several servers published from one repository. The others now have records of their own: nbclassic-mcp-bridge-mcp. 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":"nbclassic-mcp-bridge","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.
# nbclassic-mcp-bridge The Jupyter-side half of [nbclassic-mcp-bridge](https://github.com/jessegrabowski/nbclassic-mcp-bridge): an `nbclassic` frontend extension plus a relay server extension that give an MCP server a live handle on a notebook open in the classic Notebook UI. ```bash pip install nbclassic-mcp-bridge # in the Jupyter environment ``` Installing registers both the relay and the frontend extension automatically — nothing else to enable. Pair it with the [`nbclassic-mcp-bridge-mcp`](https://pypi.org/project/nbclassic-mcp-bridge-mcp/) package in your MCP client's environment. See the repository README for setup and usage.
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.