Connects MCP clients to Airflow 3.x for DAG inspection, health analysis, log tails, and gated run management.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent โ or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag โ we're steadily working through the catalog.
๐ก Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Airflow MCP Server.
airflow-list-dagsList active DAGs with tag/search filters
airflow-list-runsRecent runs of one DAG (state filter, ordered newest first)
airflow-get-task-instancesTask instances for a specific DAG run
airflow-get-task-logsTail (last N kB) of one task instance log
airflow-trigger-dagTrigger a new run (write-gated)
airflow-clear-taskClear specific task instances โ re-run (write-gated)
The us-all/airflow-mcp-server MCP server connects an MCP client to the Airflow 3.x REST API at /api/v2. It provides tools for finding active DAGs, reviewing recent runs, inspecting task instances, and retrieving the end of a task log. A health rollup combines operational signals into a DAG-level view with success rate, average duration, the most recent failed run, and failing tasks.
The server also includes two workflow prompts. dag-failure-triage gathers run and task information, retrieves relevant logs, and proposes remediation for a failed DAG. dag-schedule-audit checks DAGs for low success rates and stuck runs. The search-tools meta tool supports natural-language discovery of available tools.
At startup, the server receives an Airflow host base URL and adds /api/v2 internally. If the supplied URL ends in /api/v1 or /api/v2, that suffix is removed first. Authentication uses Airflow SimpleAuthManager: the server sends the configured credentials to /auth/token, caches the resulting JWT for the session, and refreshes it one minute before expiration.
The us-all/airflow-mcp-server MCP server uses MCP stdio by default, so it can be configured in local clients such as Claude Desktop and Cursor. Setting MCP_TRANSPORT=http switches to Streamable HTTP transport, which provides Bearer authentication and a /health endpoint.
Install the npm package as a development dependency with pnpm, or run the published package directly with npx. The server requires AIRFLOW_API_URL, AIRFLOW_USERNAME, and AIRFLOW_PASSWORD. The URL should identify the Airflow host rather than include an API path.
Set AIRFLOW_ALLOW_WRITE=true only when the client should be able to use airflow-trigger-dag and airflow-clear-task. Without that setting, the server remains read-only for those operations. AIRFLOW_TOOLS and AIRFLOW_DISABLE are available for category-level tool toggles.
The us-all/airflow-mcp-server MCP server targets Airflow 3.0โ3.2 and the /api/v2 API; the README reports verification against Airflow 3.2.1. Version 0.2 and later do not support Airflow 2.x deployments because the required basic-auth and /api/v1 behavior was removed. Airflow 2.x users should use @us-all/airflow-mcp@0.1.0 instead.
This package does not provide the deeper dbt artifact, lineage, source-freshness, or data-quality capabilities described for the companion @us-all/dbt-mcp server. The HTTP transport is opt-in; stdio is the default transport.
Always refer to the official documentation for the most accurate and up-to-date information.
Factual signals from GitHub, npm, and our automated checks โ not a rating.
No reviews yet โ be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/us-all-airflow-mcp-server)<a href="https://allmcps.com/mcp/us-all-airflow-mcp-server"><img src="https://allmcps.com/api/badge/us-all-airflow-mcp-server?style=directory" alt="Airflow MCP Server on AllMCPs" /></a>