Skip to main content
Glama

Related Servers

Alternatives to ipynb-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      A
      quality
      D
      maintenance
      Enables AI assistants to read, edit, and execute Jupyter notebook files (.ipynb) with live kernel output, without requiring JupyterLab.
      17
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      Enables adding and editing cells in local Jupyter Notebooks, and executing individual cells on the notebook's specified kernel, with state persisted across cells.
      6
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to safely and structurally edit Jupyter Notebook (.ipynb) files by providing tools to read, edit, add, and delete cells without corrupting the JSON structure.
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to browse, create, edit, and execute Jupyter notebook cells against local .ipynb files or a running Jupyter Server, including kernel interrupt/restart and notebook export. Outputs (text, tables, PNG images) are written back to the notebook and returned to the conversation.
      150 npm
      1
      MIT

    TDQS

    A3.6/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools target clearly distinct operations (read, edit, kernel management, run, run status, run cancel). The only mild overlap is the run family, where notebook_run could plausibly be assumed to return status, but the descriptions explicitly clarify that status is polled separately via notebook_run_status.

    Naming Consistency4/5

    All tools share a consistent notebook_ prefix with a mostly verb_noun structure (notebook_read, notebook_edit, notebook_run_status, notebook_run_cancel). notebook_kernel deviates slightly by using a noun rather than a verb, but the overall pattern is predictable and readable.

    Tool Count5/5

    Six tools is well-scoped for notebook lifecycle operations. Each tool covers a distinct concern (read, edit, kernel, run, status, cancel) with no redundancy and no trivially thin surface.

    Completeness4/5

    The surface covers the core lifecycle: reading, editing, executing, monitoring, cancelling runs, and managing kernels. Minor gaps exist around notebook creation/deletion and cell-level structural operations, but agents can work around these via editing.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data