Skip to content
Jupyter MCP Server

Jupyter MCP Server

Released
44 views
v1.3.4
BSD-3-Clause

Summary

Drive live Jupyter notebooks from an agent — read and edit cells, execute code, see rich outputs, and run against local JupyterLab or a cloud sandbox.

Features

  • Read, insert, edit and execute cells in a live notebook
  • Multimodal outputs — return plots and images back to the agent
  • Manage multiple notebooks in a single session
  • Code-sandbox variants for Datalayer, Kaggle, Google Colab and Modal
  • STDIO, Streamable HTTP and Jupyter Server extension transports
  • Claude Code plugin and a hosted deployment option

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

  1. Open your agent's MCP configuration file.
  2. Merge the snippet below into it, filling in the environment variables with your own values.
  3. Restart the agent — the "Jupyter MCP Server" tools will be available.
{
  "mcpServers": {
    "jupyter-mcp-server": {
      "command": "uvx",
      "args": [
        "jupyter-mcp-server@latest"
      ],
      "env": {
        "JUPYTER_URL": "http://localhost:8888",
        "JUPYTER_TOKEN": "<YOUR_TOKEN>",
        "ALLOW_IMG_OUTPUT": "true"
      }
    }
  }
}

Description

Datalayer's Jupyter MCP Server connects an agent to a running Jupyter kernel rather than to notebook files on disk. That distinction is the whole point: the agent can insert and edit cells, execute them, read the outputs — including images, when ALLOW_IMG_OUTPUT is enabled — and iterate the way a person would, with state carried between cells instead of re-running a script from scratch each time.

It handles multiple notebooks in one session, exposes server and sandbox management tools alongside cell operations, and ships MCP prompts as well as tools. A JupyterLab integration adds further tools that can be switched on at the command line.

Where the kernel lives is configurable. Beyond a local JupyterLab, sandbox variants run the code on Datalayer, Kaggle (batch or interactive, with optional GPU), Google Colab or Modal, so the same agent workflow scales from a laptop to accelerated cloud compute. A hosted version of the server is also available, and there is a Claude Code plugin (/plugin marketplace add datalayer/jupyter-mcp-server).

Setup is a short list: pip install jupyterlab jupyter-collaboration jupyter-mcp-tools ipykernel, start JupyterLab with a token, then point the client at it. Distributed under the BSD 3-Clause licence.

Covered in the Weekly

Related MCP Servers

New

Official MCP server for the Mux video API, built on a code-execution scheme: the agent writes TypeScript against the SDK and runs it in a Deno sandbox.

MCP: ripwire

by Red Hat

New

Red Hat's zero-dependency C++23 code-context engine — ranked call graphs and blast-radius analysis, indexing a repo in under half a second with no server and no database.

MCP: Graft

by Trail

New

Builds a searchable markdown graph of your repo so coding agents stop re-exploring it on every task — reported 42% fewer tokens and 46% fewer tool calls.

New

Expo's official remote MCP server — searches Expo docs, installs compatible SDK packages, triggers and monitors EAS builds, and drives iOS/Android simulators.

Browse all MCP servers →