Jupyter MCP Server for Claude Desktop

Created By
harshitha-8a year ago
Jupyter MCP Server Jupyter MCP Server is an implementation of the Model Context Protocol (MCP) server that enables interaction with Jupyter notebooks running in any JupyterLab environment, including your local JupyterLab instance
Overview

What is Jupyter MCP Server for Claude Desktop?

Jupyter MCP Server is an implementation of the Model Context Protocol (MCP) server that enables interaction with Jupyter notebooks running in any JupyterLab environment, including local instances. It is designed for seamless integration with Claude Desktop across macOS, Windows, and Linux.

How to use Jupyter MCP Server?

To use the Jupyter MCP Server, ensure you have JupyterLab and the required dependencies installed. Start JupyterLab with the appropriate command and configure the MCP server settings in your environment.

Key features of Jupyter MCP Server?

  • Provides an MCP server interface for Jupyter notebooks.
  • Supports real-time collaboration via JupyterLab.
  • Integrates smoothly with Claude Desktop (macOS, Windows, Linux).
  • Programmatically add and execute code or markdown cells in notebooks.

Use cases of Jupyter MCP Server?

  1. Collaborating on Jupyter notebooks in real-time.
  2. Executing code and markdown cells programmatically.
  3. Integrating Jupyter notebooks with Claude Desktop for enhanced functionality.

FAQ from Jupyter MCP Server?

  • What platforms does Jupyter MCP Server support?

Jupyter MCP Server supports macOS, Windows, and Linux.

  • How do I install Jupyter MCP Server?

You can install it using pip with the specified versions of JupyterLab and other dependencies.

  • Can I use Jupyter MCP Server without Docker?

Yes, but using Docker simplifies the setup and integration process.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
harshitha-8
Star
0
Language
Jupyter Notebook
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago