🚀 Jupyter MCP Server

Created By
JosephLin11a year ago
Jupyter MCP (Model Context Protocol) Server - Connect Jupyter notebooks with MCP-enabled applications
Overview

What is Jupyter MCP Server?

Jupyter MCP Server is a comprehensive Model Context Protocol (MCP) server that connects Jupyter notebooks with MCP-enabled applications, allowing for real-time code execution, visualization generation, and advanced image extraction capabilities.

How to use Jupyter MCP Server?

To use the Jupyter MCP Server, clone the repository, install the dependencies, and start the Jupyter server. Configure your MCP client to connect to the server for executing code and managing notebooks.

Key features of Jupyter MCP Server?

  • Real-time code execution through WebSocket connections.
  • Automatic kernel management and session persistence.
  • Advanced image extraction capabilities supporting multiple formats.
  • Comprehensive notebook management including cell manipulation and file operations.
  • Enterprise-ready security features including smart XSRF handling and authentication support.

Use cases of Jupyter MCP Server?

  1. Data visualization pipelines for generating and extracting visual outputs.
  2. Scientific computing with real-time execution of complex algorithms.
  3. Educational tools for interactive learning and coding.

FAQ from Jupyter MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol designed to facilitate communication between AI agents and applications, enabling seamless integration and execution of tasks.

  • Is Jupyter MCP Server free to use?

Yes! Jupyter MCP Server is open-source and free to use under the BSD 3-Clause License.

  • What are the prerequisites for using Jupyter MCP Server?

You need Python 3.11+, Jupyter Notebook, and a compatible MCP client like Claude Desktop.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JosephLin11
Star
0
Language
Python
License
BSD-3-Clause 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
Crevio

2 days ago