ipython-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IPYTHON_MCP_MAX_RESULTS | No | Maximum retained items in lists, mappings, and result discovery; default 100. | 100 |
| IPYTHON_MCP_LIBRARY_PATHS | No | Trusted library directories separated by the platform path separator. | |
| IPYTHON_MCP_MAX_JSON_DEPTH | No | Maximum nested JSON translation depth; default 6. | 6 |
| IPYTHON_MCP_MAX_REPR_CHARS | No | Maximum search representation size; default 1024. | 1024 |
| IPYTHON_MCP_MAX_TEXT_CHARS | No | Maximum returned text size; default 8192. | 8192 |
| IPYTHON_MCP_MODULE_ALIASES | No | JSON object mapping module names to namespace aliases. | |
| IPYTHON_MCP_PRELOAD_MODULES | No | Comma-separated modules imported at startup. | |
| IPYTHON_MCP_MAX_DISPLAY_ITEMS | No | Maximum display payloads retained per execution; default 20. | 20 |
| IPYTHON_MCP_MAX_DYNAMIC_TOOLS | No | Maximum retained dynamic registrations; default 100. | 100 |
| IPYTHON_MCP_MAX_TOOL_NAME_CHARS | No | Maximum dynamic MCP tool-name size; default 64. | 64 |
| IPYTHON_MCP_MAX_TRACEBACK_CHARS | No | Maximum returned traceback size; default 4096. | 4096 |
| IPYTHON_MCP_MAX_IPC_MESSAGE_BYTES | No | Positive bounded JSON IPC message size; default 4194304. | 4194304 |
| IPYTHON_MCP_MAX_PENDING_OPERATIONS | No | Positive pending FIFO capacity, excluding the active operation; default 32. | 32 |
| IPYTHON_MCP_OPERATION_TIMEOUT_SECONDS | No | Positive finite dispatch-to-result deadline; default 30. | 30 |
| IPYTHON_MCP_INTERRUPTION_GRACE_SECONDS | No | Positive finite cooperative interruption grace; default 2. | 2 |
| IPYTHON_MCP_MAX_TOOL_DESCRIPTION_CHARS | No | Maximum registration description snapshot; default 1024. | 1024 |
| IPYTHON_MCP_QUEUE_WAIT_TIMEOUT_SECONDS | No | Positive finite admission wait bound; default 30. | 30 |
| IPYTHON_MCP_WORKER_STARTUP_TIMEOUT_SECONDS | No | Positive finite initial/replacement startup bound; default 10. | 10 |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| listA | List callable functions currently available in the live namespace. |
| executeA | Execute Python source in the persistent IPython namespace. |
| call_functionC | Call a live callable by name with a JSON object of keyword arguments. |
| searchA | Search visible live namespace objects by exact or partial name. |
| reloadB | Reload explicitly named imported modules and refresh their bindings. |
| inspectB | Inspect one live name with bounded metadata and explicit truncation flags. |
| removeC | Remove unprotected top-level names and report every requested partition. |
| resetA | Remove user-created names while preserving runtime and configured bindings. |
| register_toolC | Explicitly publish one supported top-level synchronous live callable. |
| unregister_toolA | Remove requested dynamic tool registrations without affecting stable tools. |
| runtime_statusB | Report bounded out-of-band worker, queue, epoch, and recovery metadata. |
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/husams/ipython-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server