Model Context Protocol (MCP) implementation for Jupyter notebooks to overcome limitation with Cursor
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":"the-notebook-mcp","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.
[](https://pypi.org/project/the-notebook-mcp/) [](https://pypi.org/project/the-notebook-mcp/) [](https://pepy.tech/project/the-notebook-mcp) [](https://github.com/svallory/the-notebook-mcp/blob/main/LICENSE) [](https://pypi.org/project/the-notebook-mcp/) [](https://github.com/svallory/the-notebook-mcp/issues) [](https://github.com/svallory/the-notebook-mcp) [](https://coveralls.io/github/svallory/the-notebook-mcp?branch=main)   # The Notebook MCP A Model Context Protocol (MCP) server that enables AI agents to interact with Jupyter Notebook (`.ipynb`) files. Designed to overcome limitations with Cursor's AI agent mode, this tool allows AI assistants to directly manipulate notebook cells and structure through a secure, well-defined API. **Current Version:** `0.9.0` - See the [CHANGELOG.md](CHANGELOG.md) for details on recent changes. ## Why Use This? - **For Cursor Users:** Enables AI assistants to properly edit, create, and manipulate Jupyter notebooks. - **For Data Scientists:** No more copy-pasting AI output manually into your notebooks. - **For Developers:** Create complex notebook workflows with AI assistance while maintaining proper notebook structure. Although originally designed for Cursor, this MCP server can be used with any MCP-compatible …
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.