---
id: myst-nb
version: "1.4.0"
license: unclear
license_treatment: unclear
maintenance: active
---

# myst-nb — A Jupyter Notebook Sphinx reader built on top of the MyST markdown parser.

License: unclear · Maintenance: active · Downloads: 1.1M/mo

## What it is and what it does

MyST-NB is a Sphinx extension that lets you write and include Jupyter Notebooks directly in Sphinx documentation builds. Instead of converting notebooks to Markdown or reStructuredText by hand, you drop .ipynb files into your source tree and Sphinx reads them natively, rendering cells, outputs, and markdown content as part of your docs. It builds on the MyST parser, which understands Markdown syntax, so your notebooks can use MyST-flavored Markdown alongside standard Jupyter cell syntax.

The package sits at the intersection of Jupyter and Sphinx tooling. It depends on IPython, nbclient, jupyter-cache, and nbformat to handle notebook parsing and execution, plus Sphinx itself for documentation generation. It's actively maintained, supports Python 3.10 through 3.14, and is used in production documentation workflows. The main constraint is that you need a working Sphinx setup and familiarity with how Sphinx extensions are configured.

Use it for:

- Build technical documentation that includes executable Jupyter notebooks as chapters or sections.
- Publish data science or research notebooks as part of a larger Sphinx documentation site.
- Create tutorials or guides where notebook cells and their outputs are rendered inline in the final docs.
- Maintain a single source (the notebook) that serves both as an interactive tool and as documentation.
- Integrate notebooks into ReadTheDocs or similar CI/CD-driven documentation builds.

## Worth the install?

AI-flagged interpretation of the facts above — verify before relying.

Sphinx extension that parses and converts Jupyter Notebooks (.ipynb files) directly into Sphinx documentation, built on the MyST markdown parser.

Yes, if you use Sphinx for documentation and want to include Jupyter Notebooks without manual conversion. The install friction is low, maintenance is active, and the package is in the top 5000 by downloads. The only caveat is that the license status is unclear in the metadata—verify the actual license in the repository before using in proprietary contexts. No known security vulnerabilities.

## Install

pip install myst-nb
uv add myst-nb
poetry add myst-nb

## Installing myst-nb

Before you install: Low friction install with a pure Python wheel. Actively maintained as of August 2026 with recent commits. Depends on a substantial stack (Sphinx, IPython, nbclient, jupyter-cache, myst-parser) but all are standard ecosystem packages.

License in practice: License status is unclear from the package metadata—no SPDX identifier or raw license field is recorded. Verify the actual license in the repository before adopting in proprietary or restricted-license contexts.

Quickstart:

pip install myst-nb

# In conf.py:
extensions = ['myst_nb']

# Then add .ipynb files to your Sphinx source tree and build normally.

Requires Python 3.10 or later. Sphinx and IPython must be installed and configured.

Verify before relying:

- Actual license text and terms—metadata shows no SPDX or raw license field despite active development.
- Whether notebook execution is automatic or opt-in during documentation builds.
- Performance characteristics with large notebooks or many notebooks in a single build.

## Package facts

- License: not declared (unclear)
- Python support: supports_current
- Install friction: low
- Maintenance: active
- Downloads: 1.1M/month (top 5,000 on PyPI)
- Known vulnerabilities: none known

## Tags

jupyter notebook sphinx integration, convert ipynb to sphinx docs, myst notebook parser, jupyter documentation generation, sphinx notebook reader, ipynb to rst conversion, executable notebook documentation, jupyter-integration, sphinx-extension, notebook-publishing

[View on SkillFed](https://skillfed.io/packages/myst-nb) · [View on PyPI](https://pypi.org/project/myst-nb/)