Apache Zeppelin MCP Server
Related Servers
Alternatives to Apache Zeppelin MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to create, read, edit, and execute Jupyter notebook cells, manage kernels, and connect to remote Jupyter servers.21MIT
- AlicenseAqualityCmaintenanceEnables AI agents to interact with Jupyter notebooks via MCP tools for querying, modifying, executing, and setting up notebooks, with state preservation and real-time collaboration.445Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables 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-
- FlicenseAqualityDmaintenanceEnables AI agents to query and interact with Google NotebookLM notebooks to retrieve citation-backed information. It provides tools for listing notebooks, accessing source data, and asking natural language questions.11-
- AlicenseBqualityCmaintenanceEnables AI agents to interact with Microsoft Fabric by exposing tools for managing workspaces, notebooks, SQL queries, pipelines, and Livy Spark sessions. It provides a comprehensive set of operations for data engineering and analytics tasks using standard Azure authentication.374MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to execute Jupyter notebook cells with persistent kernel state, output persistence, and structured JSON control surface.2-
TDQS
Scored across 33 tools
Tools have mostly distinct resource+action targets, and descriptions actively steer the agent (e.g., get_paragraph_code vs get_paragraph, edit_paragraph vs update_paragraph, run_paragraph vs run_paragraph_async vs batch_run_paragraph). A few overlaps remain between the get/list variants and the many run flavors, but the guidance is strong enough that an agent can pick correctly.
Consistent verb_noun snake_case throughout: list_paragraphs, get_paragraph, update_paragraph, run_paragraph, delete_paragraph, move_paragraph, plus a uniformly prefixed batch_ family (batch_add/edit/delete/run/update). No style mixing.
At 33 tools it sits firmly in heavy territory, with a full parallel batch_ variant for nearly every per-paragraph operation (add, edit, update, delete, run, config). Each earns a rationale (collapsing round-trips), but the surface is larger than the domain strictly requires.
Paragraph and run lifecycles are exhaustive (list/get/get_code/forms/config, add/edit/update/move/clone/delete, run/stop/status) and notebooks cover create/list/search/get/export/import/clone plus permissions. However there is no delete_notebook or notebook rename/update, leaving the notebook lifecycle incomplete.