Airflow MCP Integration for Agentic AI

Airflow MCP lets AI clients that support the Model Context Protocol (MCP) view, run, troubleshoot and create Apache Airflow DAGs on your Data Fabric cluster, using your own identity.

As of Data Fabric 8.2.0 and DEP 10.2.0, Airflow MCP is supported. Airflow MCP is an endpoint on the Data Fabric MCP server. The MCP server run inside the Data Access Gateway. It gives AI clients such as Claude Desktop, Cursor, and MCP Inspector a set of tools that call the Airflow REST API for you.

An Apache Airflow DAG (Directed Acyclic Graph) is a worflow definition that describes tasks and the order in which they should run. This not to be confused with Data Access Gateway, which controls how applications securely access data. In this section, DAG refers to an Airflow DAG unless otherwise noted.

With Airflow MCP, you can ask an Ai assistant to:
  • List your DAGs and check their status, schedule and run history
  • Start a DAG run and watch it until it finishes
  • Find out why a run failed, using its task states and logs
  • Pause or unpause DAGs, and clear failed runs or tasks so they can run again
  • Look up Airflow settings such as connections, variables, pools and providers
  • Follow data lineage through Airflow assets and asset events
  • Write a new DAG and publish it to Airflow after you review it

How Airflow MCP works

  1. The AI client connects to the Data Fabric MCP server's Airflow endpoint at https://<host>:5679/airflow.
  2. The MCP server checks who you are and passes your JWT identity to Airflow as a Bearer token.
  3. The MCP server calls the Airflow REST API to run the tool the client asked for.
  4. Airflow sends back the result, and the MCP server passes it to the AI client.

By default, the MCP server finds the Airflow service on the cluster by itself. Administrators can also set the Airflow REST URL themselves.