ipython-kernel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IPYTHON_MCP_CONNECTION | No | Path to the Jupyter connection file for a running IPython kernel. The server connects to this existing kernel; the path is resolved from this environment variable unless overridden by the connect_to_kernel tool. |
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 |
|---|---|
| connect_to_kernelA | Connect to an existing IPython kernel using its connection file. Args: connection_file: Path to the kernel connection JSON file. If not provided, uses the IPYTHON_MCP_CONNECTION environment variable. Returns: Connection status message. |
| execute_codeA | Execute Python code on the connected IPython kernel. Variables persist between calls. Output (stdout, results, errors) is collected and returned as a single string when execution completes. Args: code: Python code to execute. Returns: Execution output (stdout, expression results, or error messages). |
| kernel_statusA | Check the current kernel connection status. Returns: Status message indicating whether a kernel is connected. |
| interrupt_kernelA | Interrupt the current kernel execution by sending SIGINT. Useful for stopping long-running code or infinite loops. Returns: Interrupt status message. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/asanchezleache/ipython-kernel-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server