Notebook MCP Bridge

An MCP (Model Context Protocol) server that lets Codex and Claude Code read, edit and run Jupyter notebooks in VS Code. Your assistant works with the notebook you see, including changes you haven't saved. Each connection stays within the assistant's own VS Code window.

What you can do

• Read and search code and Markdown; view text output and charts.
• Edit, insert, move and delete cells, change cell types, and clear outputs.
• Run selected cells, follow their progress and interrupt the whole kernel.
• Inspect variables in a Python kernel you've started; Jupyter may request your permission.
• Create notebooks and save changes when requested.

For example, ask your assistant:

Summarize this notebook, fix the data-cleaning cell, then run it and explain the output.

Requirements

• VS Code 1.100 or later on Windows x64 or Linux x64, including Remote-WSL.
• A Codex or Claude Code panel in the same VS Code window as your notebooks. With Remote-WSL, install and run both the assistant and Notebook MCP Bridge in WSL.
• To run cells, the Jupyter extension, a working kernel and a trusted workspace. Python cells need Python and ipykernel in that kernel's environment. Automatic Python kernel selection also needs the Python extension.

Reading and editing need no Python or Jupyter installation. No separate Node.js installation is needed. macOS, browser-only VS Code and assistants running in a terminal or separate application are unsupported.

Get started

1. Install Notebook MCP Bridge from the Extensions view.
2. It automatically configures Codex and Claude Code panels already installed and enabled in this window. Follow the setup notification to restart the assistant or start a new conversation.
3. Ask your assistant to list the notebooks in this window, then tell it what to work on.

For assistants installed later or an existing connection that needs replacing, run Notebook MCP Bridge: Set up assistant connection from the Command Palette. Its Connect buttons ask before replacing an existing connection.

Working with your notebook

• You control saving. Edits stay unsaved until you or the assistant save. First access may add missing cell identifiers and mark the notebook as changed.
• Conflicting edits are refused. Changed cells must be read again before editing. Cells in a tracked run are protected from assistant edits.
• Keep running notebook tabs open. Closing or moving one during command hand-over can send execution or interruption to another notebook.
• Check before repeating interrupted work. Code may still run after a lost connection. Reloading VS Code clears protection against editing those running cells. Inspect the notebook and kernel before asking to run again.
• Markdown edits refresh the preview and move keyboard focus.

Help

Run Notebook MCP Bridge: Troubleshooting for the included setup, tool and compatibility guides, available offline. Notebook MCP Bridge: Show compatibility report checks the current window's platform, connection setup and installed integrations.

License

MIT. Notebook MCP Bridge began as a fork of Olavo Carvalho's Jupyter Notebook MCP Server. The original copyright notice is preserved in the included license and attribution notices.