Skip to main content
Glama

Related Servers

Alternatives to flink-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that lets AI assistants and LLMs interact with Apache Flink clusters through natural language: cluster/job monitoring, metrics, exception tracking, TaskManager resources, and multi-cluster support via the Flink REST API.
      13
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to read and analyze Spark History Server data, including jobs, stages, executors, and SQL executions, to diagnose failures and optimize performance.
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides a read-only interface to Kubernetes clusters, enabling LLMs to list pods, get pod status and logs, fetch deployment manifests, and perform pod health analysis with resource trend tracking.
      -
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Exposes Spark History Server metrics and metadata as tools for LLM-based analysis of Spark applications. It enables deep optimization of Spark jobs by providing access to job summaries, stage details, SQL execution plans, and executor performance.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides read-only monitoring of Apache Airflow DAGs, including listing active DAGs, fetching recent runs, and analyzing execution history and performance metrics.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Apache Flink clusters via the SQL Gateway, allowing query execution, session management, and job control through MCP tools.
      8
      Apache 2.0

    TDQS

    B3.1/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools target a distinct resource+granularity: job_metrics vs vertex_metrics, get_logs vs list_log_files, diagnose_job (in-job health) vs diagnose_deployment (Kubernetes/operator health) are explicitly delineated in their descriptions. The main overlap cluster is job_details / job_timeline / diagnose_job / cluster_overview, where a newcomer might hesitate, but descriptions steer toward diagnose_job as the entry point.

    Naming Consistency3/5

    A dominant noun-based convention exists (cluster_config, job_config, checkpoint_stats, backpressure, taskmanagers) with `list_` used for enumerations (list_jobs, list_jars, list_clusters). But it is inconsistently applied: `get_logs` is the sole `get_` verb, `taskmanagers` is a bare plural where siblings use `list_`, and `list_flink_deployments` mixes a vendor-specific noun into the pattern.

    Tool Count3/5

    21 tools is on the heavy side for a monitoring server and pushes toward the borderline band. The facets (cluster, job, metrics, logs, config, savepoints, Kubernetes operator) each justify tools, but a few (list_jars, cluster_config, job_config) are narrow and could be consolidated into a generic cluster/job inspection call.

    Completeness4/5

    The read-only diagnostics surface is thorough: state, exceptions, timeline, checkpoints, savepoints/restore origins, backpressure, metrics at both job and vertex level, logs, config, and Kubernetes/operator health. Gaps are around lifecycle actions a user might expect next (trigger savepoint, cancel/restart job, thread dump), so an agent can diagnose but never act.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data