Schema | mcp-server-jupyter

mcp-server-jupyter

Describes the environment variables required to run the server.

Name	Required	Description	Default
`UV_PROJECT_ENVIRONMENT`	Yes	Path to the virtual environment used for Jupyter notebooks (e.g., /path/to/venv_for_jupyter/.venv)

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
read_notebook_with_outputsA	Read the current version of the notebook at notebook_path, including cell outputs. Use this before modifying a notebook to understand its existing content and determine if changes are needed.
read_notebook_source_onlyA	Read the current version of the notebook at notebook_path without outputs. Use this when size limitations prevent reading the full notebook with outputs. Individual cell outputs can be retrieved using the read_output_of_cell tool.
read_output_of_cellB	Read the output of a specific cell in a notebook, by cell_id.
execute_cellA	Executes a specific cell in a notebook and returns its output. Useful to check that the cell runs without errors as well as produces the desired output.
add_cellB	Add a new cell to the notebook at the specified position.
edit_cellC	Edit the source code of an existing cell in the notebook.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ihrpr/mcp-server-jupyter'

If you have feedback or need assistance with the MCP directory API, please join our Discord server