MCP Jupyter Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_cellsA | List all cells in a Jupyter notebook with their indices and types |
| get_cell_sourceC | Get the source code of a specific cell by index |
| edit_cell_sourceC | Edit the source code of a specific cell by index |
| insert_cellC | Insert a new cell at a specific position |
| delete_cellC | Delete a cell by index |
| move_cellC | Move a cell from one position to another |
| convert_cell_typeC | Convert a cell from one type to another |
| bulk_edit_cellsC | Perform bulk operations on multiple cells |
| read_notebook_with_outputsC | Read a Jupyter notebook including cell outputs |
| execute_cellC | Execute a specific cell in the notebook using a Jupyter kernel |
| add_cellC | Add a new cell to the notebook |
| edit_cellC | Edit the source code of a specific cell by ID or index |
| trigger_vscode_reloadC | Trigger VS Code to reload the notebook file |
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 13 tools
Most tools have distinct purposes for cell operations, but there is notable overlap between 'edit_cell' and 'edit_cell_source' which both edit cell source code, and between 'add_cell' and 'insert_cell' which both add cells. This could cause confusion for an agent trying to select the right tool.
Tool names follow a consistent verb_noun pattern (e.g., add_cell, delete_cell, execute_cell) with clear actions and targets. The only deviation is 'read_notebook_with_outputs' which is longer but still follows the pattern, and 'trigger_vscode_reload' which uses a verb_noun_noun structure but remains readable.
With 13 tools, this server is well-scoped for managing Jupyter notebooks, covering a comprehensive set of operations like adding, editing, executing, and listing cells. Each tool appears to serve a specific function without unnecessary bloat.
The toolset provides strong coverage for cell-level operations (CRUD, execution, type conversion) and notebook reading, but lacks tools for higher-level notebook management such as saving, creating new notebooks, or kernel control. Minor gaps exist, but agents can likely work around them.