Jupyter Notebook Editor MCP Server
A Model Context Protocol (MCP) server for programmatically editing Jupyter notebooks while preserving their format and structure.
Features
- 29 specialized tools for notebook manipulation
- File-based operations - no Jupyter server required
- Format preservation - automatic validation after modifications
- Batch operations - modify multiple cells or notebooks at once
- Type-safe - full type hints for all operations
Installation
One-Click Install
From PyPI
uv tool install jupyter-editor-mcp
jupyter-editor-mcp
From Source
git clone https://github.com/jsamuel1/jupyter-editor-mcp.git
cd jupyter-editor-mcp
uv venv
uv pip install -e ".[dev]"
See INSTALL.md for detailed configuration options.
Usage
With Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"jupyter-editor": {
"command": "jupyter-editor-mcp"
}
}
}
Example Interactions
Read a notebook:
"Show me the structure of my notebook.ipynb"
Insert a cell:
"Add a markdown cell at the beginning explaining what this notebook does"
Batch operations:
"Replace all occurrences of 'old_function' with 'new_function' in all code cells"
Multi-notebook:
"Merge analysis.ipynb and visualization.ipynb into combined.ipynb"
Tool Categories
- Read Operations (4 tools): read_notebook, list_cells, get_cell, search_cells
- Cell Modification (5 tools): replace_cell, insert_cell, append_cell, delete_cell, str_replace_in_cell
- Metadata Operations (4 tools): get_metadata, update_metadata, set_kernel, list_available_kernels
- Batch Operations - Multi-Cell (6 tools): replace_cells_batch, delete_cells_batch, insert_cells_batch, search_replace_all, reorder_cells, filter_cells
- Batch Operations - Multi-Notebook (7 tools): merge_notebooks, split_notebook, apply_to_notebooks, search_notebooks, sync_metadata, extract_cells, clear_outputs
- Validation (3 tools): validate_notebook, get_notebook_info, validate_notebooks_batch
Development
# Run tests
pytest
# Run tests with coverage
pytest --cov
# Install in development mode
uv pip install -e ".[dev]"
Documentation
- docs/RESEARCH.md - Technical research and tool specifications
- docs/REQUIREMENTS.md - User stories and acceptance criteria
- docs/DESIGN.md - Architecture and API design
- CONTRIBUTING.md - Contribution guidelines
License
MIT
Metadata
Release files for jupyter-editor-mcp 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| jupyter_editor_mcp-0.2.2.tar.gz | 152.1 kB | With provenance | Details for jupyter_editor_mcp-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jupyter_editor_mcp-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for jupyter_editor_mcp-0.2.2-py3-none-any.whl |
Total release size: 166.9 kB
Release files / jupyter_editor_mcp-0.2.2.tar.gz
| Download URL | jupyter_editor_mcp-0.2.2.tar.gz |
|---|---|
| Size | 152.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
68d85f4f9df652293fdaa702b3b3fb8de9e01ca6e0d0adf9c53ba853064bbc05
|
|
BLAKE2b-256 checksum How to use checksums |
aea2ee13af7fbcc51c27e8113ad33746b9fea28ac6969de19f2a5a3c90336373
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 15, 2026.
Transparency logRelease files / jupyter_editor_mcp-0.2.2-py3-none-any.whl
| Download URL | jupyter_editor_mcp-0.2.2-py3-none-any.whl |
|---|---|
| Size | 14.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2242880050b941c902a07895c0772d41c02682bf9e93386cf0294a860fdba9e0
|
|
BLAKE2b-256 checksum How to use checksums |
a829548f8fac5f6e7e136e3298ee2afa13effe2e7bddca05810c513f6adbab4f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 15, 2026.
Transparency logSecurity for jupyter-editor-mcp 0.2.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for jupyter_editor_mcp-0.2.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 15, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.