Airflow MCP
Related Servers
Alternatives to Airflow MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceA Model Context Protocol server that wraps Apache Airflow's REST API with Bearer token authentication support, enabling AI assistants to interact with Airflow deployments including Astronomer Cloud.66MIT
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server for controlling Airflow 3 via Airflow APIs.MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Apache Airflow through the Model Context Protocol, allowing users to manage DAGs, task instances, variables, connections, pools, XComs, and datasets.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- 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 gradedqualityDmaintenanceA Model Context Protocol Server that enables LLMs to interact with and execute REST API calls through natural language prompts, supporting GET/PUT/POST/PATCH operations on configured APIs.321 PyPI6Apache 2.0
TDQS
Scored across 9 tools
Each tool targets a distinct entity or action: DAG metadata, DAG run details, task logs, listing operations, and state changes (pause, unpause, trigger). No overlapping purposes.
All names follow a consistent verb_noun pattern with underscores (e.g., get_dag, list_dags, trigger_dag_run). Verbs are clear and nouns precisely identify the resource.
9 tools is appropriate for an Airflow MCP server, covering core operations without redundancy. The count is well-scoped for the domain.
Covers essential DAG, DAG run, and task instance operations. Minor gaps like clearing task instances or updating DAG configuration are missing but not critical for typical monitoring and triggering workflows.