airflow-mcp
Related Servers
Alternatives to airflow-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables inspection and management of Apache Airflow DAGs, runs, and logs across multiple instances. It provides tools for monitoring workflows and performing gated write operations like triggering DAGs or clearing task instances.1673 PyPI2Apache 2.0
- AlicenseNot gradedqualityDmaintenanceProvides read-only monitoring of Apache Airflow DAGs, including listing active DAGs, fetching recent runs, and analyzing execution history and performance metrics.1MIT
- AlicenseAqualityBmaintenanceEnables Claude to inspect and operate Apache Airflow over its REST API, providing read tools and safe write operations (gated by read-only mode) for managing DAGs, runs, tasks, and pools.14MIT
- FlicenseNot gradedqualityDmaintenanceEnables DAG management, monitoring, debugging, and connection testing for Apache Airflow through the MCP protocol.-
- AlicenseAqualityDmaintenanceEnables management of Amazon Managed Workflows for Apache Airflow (MWAA) environments and operations including DAG management, workflow execution monitoring, and access to Airflow connections and variables through a unified interface.213Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables users to inspect databases through read-only tools that explain queries, sample rows, and list indexes, while refusing apply or delete operations.MIT
TDQS
Scored across 5 tools
The five tools mostly target distinct resources: DAGs, tasks, runs, a run snapshot, and task instances. The only mild overlap is between inspect_run's task attempts and list_task_instances, but the descriptions make the run-level vs execution-level distinction reasonably clear.
All tool names use snake_case with a clear verb_noun pattern: list_runs, inspect_run, list_dags, list_tasks, and list_task_instances. The single inspect_ prefix variation is natural and does not break consistency.
Five tools is a well-scoped set for a read-oriented Airflow inspection server. Each tool covers a distinct listing or inspection need without redundant operations.
The server covers broad listing and run snapshot inspection, but it lacks key follow-up operations such as getting a single DAG or task instance, retrieving logs, or accessing XCom values. These gaps will limit agents trying to debug task failures beyond enumeration.