Skip to main content
Glama
block

Jupyter MCP Server

by block
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Jupyter MCP Server

No user-submitted related servers found.

    Related Servers

    • Cellar

      fbereilh
      A
      license
      Not graded
      quality
      A
      maintenance
      An interactive notebook server that enables humans and AI agents to collaboratively edit and run Jupyter notebooks on a shared kernel, with real-time streaming and automatic MCP integration for agent access.
      34 npm
      MIT

    • jupyter-vscode-mcp

      hadiproz
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes Jupyter notebook operations as MCP tools over plain HTTP, allowing AI agents to explore, edit, run, and debug notebooks in a live VS Code session using local or remote kernels.
      2
      MIT

    • notebook-agent-mcp

      KJH-Sun
      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
      -
    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

    A4.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: setup_notebook initializes and connects, execute_notebook_code runs code, modify_notebook_cells edits cells, and query_notebook retrieves information. No overlap in functionality.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with underscores (setup_notebook, execute_notebook_code, modify_notebook_cells, query_notebook). The naming is predictable and clear.

    Tool Count4/5

    With 4 tools, the count is appropriate for a Jupyter notebook server. Each tool is well-scoped, though some tools encapsulate multiple sub-operations, which could be split but is not problematic.

    Completeness4/5

    The tool surface covers the essential operations: setup, code execution, cell modification, and querying. Minor gaps like kernel management or file uploads are absent but not critical for basic notebook interaction.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources