MCP Server for Apache Airflow
Related Servers
Alternatives to MCP Server for Apache Airflow
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceAn 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

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- FlicenseNot gradedqualityDmaintenanceEnables DAG management, monitoring, debugging, and connection testing for Apache Airflow through the MCP protocol.-
- AlicenseNot gradedqualityDmaintenanceProvides integration with Apache Airflow's REST API, allowing AI assistants to programmatically interact with Airflow workflows, monitor DAG runs, and manage tasks.MIT
- 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
- AlicenseNot gradedqualityDmaintenanceProvides a standardized MCP interface for interacting with HTTP tools and services, enabling unified API access and management.MIT
TDQS
Scored across 68 tools
Most tools have distinct purposes targeting specific Airflow entities (DAGs, tasks, connections, variables, datasets), but there is some overlap between get_dag_details and get_dag, and between get_tasks and get_dag_tasks, which could cause minor confusion. The descriptions help differentiate, but the sheer number of tools increases cognitive load.
Tool names follow a highly consistent verb_noun pattern throughout (e.g., get_dag, create_connection, delete_variable, update_task_instance). There are no deviations in naming conventions, making the set predictable and easy to navigate.
With 68 tools, this server is overloaded for typical agent use. While Airflow is a complex system, this count far exceeds the 3-15 range for well-scoped servers, making it heavy and likely overwhelming for agents to handle efficiently.
The tool surface provides comprehensive CRUD/lifecycle coverage for all key Airflow domains (DAGs, tasks, connections, variables, datasets, pools, logs, XComs). There are no obvious gaps, and operations like create, get, update, delete, list, and state management are fully represented across entities.