airflow

Query, manage, and troubleshoot Apache Airflow DAGs, runs, tasks, and system configuration. Use af commands to query, manage, and troubleshoot Airflow workflows. The Astro CLI is the recommended way to run Airflow locally and deploy to production. It provides a containerized Airflow environment that works out of the box: For more details: These commands assume af is on PATH. Run via astro otto to get it automatically, or install standalone with uv tool install astro-airflow-mcp . Manage multiple Airflow instances with persistent configuration: Config file: ~/.af/config.yaml (override with --config or AF_CONFIG env var) Tokens in config can reference environment variables using ${VAR} syntax: Or use environment variables directly (no config file needed): Or CLI flags: af --airflow-url --token "$TOKEN" If you're using the Astro CLI, you can validate DAGs without a running Airflow instance: Otherwise, validate against a running instance: The Airflow Registry at airflow.apache.org/registry is the authoritative source for provider classes and their current constructor signatures. Prefer it over memory or stale documentation when authoring DAGs — the registry reflects the live provider release. Results are cached locally: 1 hour for the latest version, 30 days for pinned versions (which are immutable).