astro-airflow-mcp

Official

An MCP server that enables AI assistants to interact with Apache Airflow's REST API for DAG manageme...

416 views

2 installs

Updated Jan 19, 2026

Not audited

An 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.

Click the "Install Now" button to open the FastMCP connection interface. Fill the environment variables below into the form fields in that interface (FastMCP will use these values when starting the MCP server).
AIRFLOW_API_URL — find your Airflow webserver URL:
- If you run Airflow locally (Astro CLI / default), use http://localhost:8080. (astronomer.io)
AIRFLOW_USERNAME and AIRFLOW_PASSWORD — create or obtain a user for API access:
- Option A (CLI): SSH/exec into the Airflow environment (or run inside the Airflow container) and run:
  airflow users create --username --firstname --lastname --email you@example.com --role Admin --password
  This creates a user you can use for API authentication. (airflow.apache.org)
- Option B (UI): Log into the Airflow web UI (Admin / Security / Users or equivalent) and create a user with an appropriate role (Admin/User with API access). (airflow.apache.org)
AIRFLOW_AUTH_TOKEN — (alternative to username/password) obtain a JWT bearer token:
- If your Airflow uses the FAB auth manager (or other token-capable auth manager), generate a JWT token by POSTing credentials to the Airflow token endpoint:
  curl -X POST "http:///auth/token" -H "Content-Type: application/json" -d '{"username":"","password":""}'
  The response contains a JWT you can use for API calls. Paste the JWT string into the AIRFLOW_AUTH_TOKEN field in the FastMCP interface (the MCP will send it in the Authorization: Bearer header). (airflow.apache.org)
Which auth method to pick:
- Use AIRFLOW_AUTH_TOKEN if you prefer a single bearer token for programmatic access (supported when your Airflow auth manager exposes /auth/token). Otherwise supply AIRFLOW_USERNAME and AIRFLOW_PASSWORD and let the MCP perform any necessary token exchange. (airflow.apache.org)
Save the environment values in the FastMCP connection interface and start the MCP ("Install"/"Connect" action). FastMCP will pass those env vars to the astro-airflow-mcp server.
Verify the connection:
- After the MCP starts, run a small MCP call (for example: get_airflow_version or list_dags) from your MCP client to confirm authentication and connectivity. If you get auth errors, re-check the URL, username/password, or the token and retry.

Notes / troubleshooting:

If Airflow is hosted (Astronomer/Astro, Kubernetes ingress, cloud deployment), get the webserver URL from your hosting control panel or ingress/LoadBalancer address and use that as AIRFLOW_API_URL. (astronomer.io)
If /auth/token returns 401 for certain backends (e.g., LDAP or custom auth), consult your Airflow auth-manager documentation and your deployment’s auth backend configuration — token behavior can differ by auth manager. (github.com)