Skip to main content
Glama
fastmcp-me

MCP-Airflow-API

by fastmcp-me

Related Servers

Alternatives to MCP-Airflow-API

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Apache Airflow through the Model Context Protocol, allowing users to manage DAGs, task instances, variables, connections, pools, XComs, and datasets.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with Apache Airflow for querying DAGs, monitoring execution, and troubleshooting failures.
      1
      MIT
    • 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
    • A
      license
      B
      quality
      A
      maintenance
      A Model Context Protocol server that exposes Apache Airflow's REST API to AI agents, enabling them to inspect and operate on DAGs, DAG runs, task instances, and logs.
      9
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables natural language interaction with Home Assistant for managing entities, automations, services, and dashboards via the Model Context Protocol.
      189 npm
      MIT
    • A
      license
      B
      quality
      F
      maintenance
      A Model Context Protocol server that allows AI assistants to interact with Prefect's workflow automation platform through natural language, enabling users to manage flows, deployments, tasks, and other Prefect resources via conversational commands.
      46
      15
      Apache 2.0

    TDQS

    C2.9/5.0

    Scored across 54 tools

    Disambiguation4/5

    Most tools clearly target distinct resources and actions, such as list_dags, get_dag, and trigger_dag. However, a few pairs like list_task_instances_all vs list_task_instances_batch and list_dataset_events vs get_dataset_events have overlapping purposes that could confuse an agent.

    Naming Consistency5/5

    All 54 tools follow a consistent snake_case verb_noun pattern, such as get_user, list_plugins, trigger_dag, and pause_dag. Even longer names like get_dags_detailed_batch and list_task_instances_all maintain the same pattern, with no mixed naming conventions.

    Tool Count1/5

    With 54 tools, this is an extremely large tool set for a single server. The number far exceeds the typical well-scoped range of 3-15 tools, and while Airflow is complex, many tools are redundant or could be consolidated, making the surface overwhelming for an agent.

    Completeness3/5

    The tool set provides broad read coverage for most Airflow resources, including DAGs, task instances, connections, variables, and pools, plus core actions like triggering, pausing, and unpausing DAGs. However, there are significant gaps in mutation operations, such as creating or updating variables, pools, and users, and missing common task management like clearing or retrying task instances.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues