Skip to main content
Glama

Related Servers

Alternatives to pyrepl-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      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.
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to execute Jupyter notebook cells with persistent kernel state, output persistence, and structured JSON control surface.
      2
      -
    • 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
    • A
      license
      A
      quality
      C
      maintenance
      Connects to an existing IPython kernel for persistent Python code execution, preserving variables and state across calls. It enables AI agents and clients to share a live kernel for interactive coding, execution, kernel status checks, and interrupts.
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables agents to run and manage SageMath computations through a persistent kernel over stdio, including executing code, polling long-running jobs, interrupting or resetting sessions, running files, and driving notebooks.
      7
      MIT

    TDQS

    A4.6/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of selecting the wrong one. The only ambiguity is internal (passing an empty string to collect output, or magic strings like %interrupt/%restart/%status), which is a mode overload inside a single tool rather than a boundary between tools.

    Naming Consistency4/5

    With a single tool named 'ipython', there is no inconsistency to speak of, and the name accurately signals a persistent IPython kernel. It does not follow a verb_noun pattern, but nothing else exists to pattern-match against, so the deviation is inconsequential.

    Tool Count4/5

    For a code-execution server, one entry point is the correct granularity: bash, env, save/load and kernel control are deliberately exposed as in-kernel helpers rather than separate tools, avoiding redundancy. It sits just below the typical 3-15 range, and those helpers are discoverable only via the description rather than as first-class tools.

    Completeness4/5

    Arbitrary Python execution plus background bash handles, snapshot save/load, and kernel lifecycle (%interrupt, %restart, %status) cover the realistic workflow with no dead ends. Minor gaps: no way to enumerate or delete saved snapshots, no named sessions or multiple kernels for parallel work, and no explicit per-call timeout parameter surfaced in the tool schema.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues