MCP-Airflow-API
Related Servers
Alternatives to MCP-Airflow-API
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server exposing Apache Airflow REST API operations as tools — list DAGs, inspect runs and task instances, trigger DAG runs, and check failed DAGs and scheduler health72MIT

astro-airflow-mcpofficial
AlicenseAqualityFmaintenanceAn 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.3113Apache 2.0- AlicenseAqualityBmaintenanceMCP 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.21Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server for controlling Apache Airflow 3 via its REST API, enabling operations like DAG management, task monitoring, and more through natural language.MIT
- AlicenseAqualityAmaintenanceAn 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.101MIT
- AlicenseNot gradedqualityDmaintenanceEnables natural language interaction with Apache Airflow for querying DAGs, monitoring execution, and troubleshooting failures.1MIT
TDQS
Scored across 54 tools
Each tool targets a distinct resource or action (e.g., list_dags, trigger_dag, get_config_section). Even closely related tools like running_dags and failed_dags have clear, non-overlapping purposes. No ambiguity in tool selection.
Most tools follow a consistent verb_noun pattern (list, get, create, trigger, pause), with minor deviations like running_dags and batch tools (get_dags_detailed_batch). Naming is readable and predictable overall, but not perfectly uniform.
With 54 tools, the set is far above the recommended 3-15 range and exceeds the 25+ threshold for 'too many'. While the Airflow domain is broad, the sheer number will likely overwhelm agents and reduce usability.
The server covers virtually all Airflow API resources: DAGs, runs, tasks, variables, connections, config, pools, datasets, users, permissions, logs, and more. It includes CRUD for connections and provides detailed views, summaries, and search, making it a comprehensive surface.