Claude Code Notebook MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notebook_createA | Creates a new, empty notebook file |
| notebook_deleteC | Deletes an existing notebook file |
| notebook_renameB | Renames/moves a notebook file from one path to another |
| notebook_readC | Reads an entire notebook and returns its structure as a dictionary |
| notebook_read_cellB | Reads the source content of a specific cell |
| notebook_add_cellA | Adds a new code or markdown cell after a specified index |
| notebook_edit_cellC | Replaces the source content of a specific cell |
| notebook_delete_cellC | Deletes a specific cell |
| notebook_change_cell_typeB | Changes a cell's type (code, markdown, or raw) |
| notebook_duplicate_cellB | Duplicates a cell multiple times (default: once) |
| notebook_get_cell_countB | Returns the total number of cells |
| notebook_read_metadataA | Reads the top-level notebook metadata |
| notebook_edit_metadataC | Updates the top-level notebook metadata |
| notebook_read_cell_metadataC | Reads the metadata of a specific cell |
| notebook_read_cell_outputB | Reads the output list of a specific code cell |
| notebook_edit_cell_metadataC | Updates the metadata of a specific cell |
| notebook_clear_cell_outputsA | Clears the outputs and execution count of a specific cell |
| notebook_clear_all_outputsB | Clears outputs and execution counts for all code cells |
| notebook_move_cellC | Moves a cell to a different position |
| notebook_split_cellB | Splits a cell into two at a specified line number |
| notebook_merge_cellsB | Merges a cell with the cell immediately following it |
| notebook_validateB | Validates the notebook structure against the nbformat schema |
| notebook_get_infoB | Retrieves general information (cell count, metadata, kernel, language info) |
| notebook_exportA | Exports the notebook to another format (e.g., python, html) using nbconvert |
| notebook_get_outlineB | Produces an outline showing cell numbers with major headings/functions and line counts |
| notebook_searchA | Searches cells for a keyword, showing which cell matches were found with contextual snippets |
| notebook_edit_cell_outputC | Allows direct manipulation and setting of cell outputs |
| notebook_bulk_add_cellsC | Adds multiple cells to a notebook in a single operation |
| notebook_get_server_path_contextB | Provides detailed server path configuration (allowed_roots, OS path style, project directory validation, and path construction guidance) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.