Skip to main content
Glama
husams

ipython-mcp

by husams
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ipython-mcp

No user-submitted related servers found.

    Related Servers

    • loommux

      MichengLiang
      A
      license
      A
      quality
      A
      maintenance
      Enables interactive Python execution with a persistent IPython kernel through MCP, retaining namespace state and providing structured output logs for agent and tool integrations.
      8
      Apache 2.0

    • repl-mcp

      iota-uz
      F
      license
      A
      quality
      C
      maintenance
      A persistent Python REPL MCP server for AI agents with stateful execution, real timeouts, crash isolation, and an MCP bridge to call other tools in the project.
      1
      2
      -

    • mypr-mcp

      prepaser
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLM agents to run persistent Python code in a workspace-scoped shared kernel, with tools for execution, background tasks, file operations, and external MCP integrations.
      AGPL 3.0

    • Sherlog MCP

      GetSherlog
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent IPython shell sessions per conversation with DataFrame-centric architecture, enabling stateful data analysis, CLI tool execution, and integration of external MCP servers within the same workspace context.
      23
      Apache 2.0

    • python-session-mcp

      merwanroudane
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLM clients to run Python code in a persistent, user-selected interpreter via MCP, with tools for data loading, summaries, regressions, diagnostics, and plotting, while keeping sessions alive between calls and isolating crashes.
      MIT

    • kernel-mcp

      Luckylobster8868
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides a persistent Jupyter kernel for executing code, inspecting variables and dataframes, and checking SQL query plans, enabling agents to work with stateful Python sessions.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 11 tools

    Disambiguation4/5

    Tools are mostly distinct, but `list`, `search`, and `inspect` all deal with namespace introspection and could be confused at a glance. `remove` vs `reset` also have overlapping deletion semantics, though descriptions clarify boundaries.

    Naming Consistency4/5

    Naming uses a consistent snake_case imperative style (e.g., `execute`, `inspect`, `register_tool`). A few names like `runtime_status` are noun-like rather than verb_noun, but overall the pattern is predictable and readable.

    Tool Count5/5

    11 tools is well within the ideal 3-15 range and each tool serves a clear purpose for managing a live IPython namespace. The count feels appropriate for the server's stated scope.

    Completeness4/5

    The toolset covers core operations: executing code, inspecting objects, managing namespace bindings, and runtime status. Minor gaps like fetching full history or handling asynchronous execution exist, but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources