jupyter-kernel-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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_kernelA | Start a new Jupyter kernel with persistent state for code execution. |
| stop_kernelA | Stop and permanently remove a Jupyter kernel and all its state. |
| list_kernelsA | List all currently active Jupyter kernels with their status information. |
| execute_codeA | Execute Python code in a persistent Jupyter kernel with maintained state. |
| list_variablesA | List all variables currently defined in the specified kernel's namespace. |
| reset_kernelA | Reset a Jupyter kernel by clearing all variables and state while keeping the same ID. |
| get_kernel_statusA | Get detailed status information about a specific Jupyter kernel. |
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 7 tools
Each tool targets a distinct operation: execution, kernel lifecycle, variable listing, and status. No overlapping functionality.
All tool names follow a consistent verb_noun pattern in lowercase snake_case, e.g., execute_code, reset_kernel.
7 tools is appropriate for managing Jupyter kernels: start, stop, reset, list, status, variable listing, and code execution. Not excessive or sparse.
Covers core kernel lifecycle and code execution. Missing features like interrupting a kernel or retrieving execution history, but essential operations are present.