Claude Code Notebook MCP
Related Servers
Alternatives to Claude Code Notebook MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA Model Control Protocol (MCP) server that enables remote programmatic control of Jupyter notebooks, allowing AI assistants and applications to create, edit, and execute notebook cells via SSE protocol.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that connects to existing IPython kernels, allowing Claude to execute code in a shared persistent environment with your IDE.2MIT
- AlicenseNot gradedqualityBmaintenanceA self-hosted MCP server providing Claude with an interactive Jupyter environment, including real kernels, persistent notebooks, and optional GPU offload to Google Colab.MIT
- AlicenseNot gradedqualityDmaintenanceAn agent-agnostic MCP server that lets any AI agent drive a local JupyterLab session via the Model Context Protocol.CC BY-4.0
- AlicenseAqualityDmaintenanceAI-powered MCP server for connecting and managing Jupyter Notebooks. Enables interactive code execution, multi-notebook management, and multimodal output for data analysis, visualization, and machine learning.129MIT
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that enables AI assistants like Claude to perform Python development tasks through file operations, code analysis, project management, and safe code execution.9MIT
TDQS
Scored across 29 tools
Every tool targets a distinct aspect of notebook manipulation: whole notebook, individual cells, metadata, outputs, or file operations. There is no overlap; even similar-sounding tools like notebook_read and notebook_read_cell are clearly differentiated by scope.
All tools follow the consistent pattern 'notebook_verb_noun', with verbs like create, delete, read, edit, and nouns like cell, metadata, output. The few plural nouns (cells, outputs) are grammatically correct and do not break the pattern.
With 29 tools, the set is beyond the typical 3-15 well-scoped range and exceeds the 25+ threshold for 'too many'. While each tool is justified, the count feels heavy for a notebook manipulation server, and some tools (e.g., notebook_edit_cell_output vs notebook_edit_cell) could be consolidated.
The tool set covers all major notebook lifecycle operations: CRUD for notebooks and cells, metadata editing, output management, validation, export, search, and outline generation. There are no obvious gaps for the intended domain of notebook file manipulation.