Skip to main content
Glama
Mhdd-24

@mhdd_24/airflow-mcp

by Mhdd-24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @mhdd_24/airflow-mcp

No user-submitted related servers found.

    Related Servers

    • Airflow MCP

      ponderedw
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Apache Airflow for querying DAGs, monitoring execution, and troubleshooting failures.
      1
      MIT

    • Airflow MCP

      hipposys-ltd
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to interact with Apache Airflow orchestration platform through natural language to query pipeline statuses, troubleshoot DAG failures, trigger DAGs, and analyze configurations.
      10
      MIT

    • MCP-Airflow-API

      fastmcp-me
      A
      license
      C
      quality
      D
      maintenance
      Enables natural language management of Apache Airflow workflows, including DAG monitoring, task control, and configuration, via the Model Context Protocol.
      54
      MIT

    • MCP-Airflow-API

      call518
      A
      license
      B
      quality
      A
      maintenance
      Monitor and manage Apache Airflow clusters through natural language queries via MCP tools: DAG inspection, task monitoring, health checks, and cluster analytics without API complexity. * Guide: https://call518.medium.com/mcp-airflow-api-a-model-context-protocol-mcp-server-for-apache-airflow-5dfdfb2
      54
      53
      MIT

    • mwaa-mcp-server

      biswasbiplob
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Amazon MWAA that enables managing Airflow environments, DAGs, runs, task instances, and configurations through natural language, using secure AWS-native API access and read-only by default.
      21
      Apache 2.0
    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

    B3/5.0

    Scored across 4 tools

    Disambiguation3/5

    Most tools are clearly distinct (list vs get vs status), but 'airflow_status' and 'airflow_diagnose' overlap in intent—both appear to inspect health or state, making it ambiguous which to choose for a given diagnostic question.

    Naming Consistency4/5

    All tools share the 'airflow_' prefix with snake_case, but 'airflow_status' uses a noun while the others use verbs (list, get, diagnose), creating a minor inconsistency in the naming pattern.

    Tool Count5/5

    Four tools is a tight, focused set for an Airflow-oriented server. Each tool addresses a distinct need and none feel redundant or superfluous.

    Completeness3/5

    The set covers read-only inspection and diagnostics well, but lacks common Airflow DAG operations like pause/unpause, trigger, or delete. If the intended scope is monitoring only, this is fine; for management tasks, there are notable gaps.

    Resources