Skip to main content
Glama
mihneamanolache

zeppelin-mcp

by mihneamanolache
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to zeppelin-mcp

No user-submitted related servers found.

    Related Servers

    • astro-airflow-mcp by astronomer

      astro-airflow-mcpofficial

      astronomer
      A
      license
      A
      quality
      F
      maintenance
      An MCP server that enables AI assistants to interact with Apache Airflow's REST API for DAG management, task monitoring, and system diagnostics. It provides comprehensive tools for triggering workflows, retrieving logs, and inspecting system health across Airflow 2.x and 3.x versions.
      31
      13
      Apache 2.0

    • Apache Airflow MCP Server

      swesmith-repos
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      An MCP server that wraps the Apache Airflow REST API, enabling clients to manage DAGs, monitor task instances, and handle workflows through a standardized interface. It provides comprehensive access to Airflow features including DAG runs, variables, connections, and XComs.
      MIT

    • airflow-dev-mcp

      BrianLondon
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables AI coding assistants to interact with a local Airflow cluster via its REST API for triggering DAG runs, monitoring status, reading logs, and diagnosing errors.
      10
      1
      MIT

    • superset-mcp

      thedeceptio
      F
      license
      B
      quality
      D
      maintenance
      An MCP server that provides AI assistants with full access to Apache Superset instances, enabling interaction with dashboards, charts, datasets, databases, and SQL execution capabilities.
      34
      -
    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

    A3.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: notebook lifecycle, paragraph lifecycle, execution control, interpreter restart, and authentication. Descriptions clarify boundaries (e.g., get_notebook vs get_paragraph). No overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with underscores (e.g., create_notebook, delete_paragraph, run_all_paragraphs). The only slight deviation is zeppelin_login, but it still fits the pattern of action_resource. Naming is uniform and predictable.

    Tool Count5/5

    14 tools provide a well-scoped surface for managing Zeppelin notebooks. It covers CRUD for notebooks and paragraphs, execution commands, interpreter restart, and authentication—neither too sparse nor excessive for the domain.

    Completeness4/5

    The toolset covers core notebook and paragraph operations, execution, and interpreter management. Minor gaps include no logout, no interpreter listing, and no notebook import/export, but the set is sufficient for typical agent interactions with Zeppelin.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources