airflow

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: Run all af commands using uvx (no installation required): Throughout this document, af is shorthand for uvx --from astro-airflow-mcp af . 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: All commands output JSON (except instance commands which use human-readable tables): Use jq for filtering: Use af api for endpoints not covered by high-level commands (XCom, event-logs, backfills, etc). Field syntax : -F key=value auto-converts types, -f key=value keeps as string. Full reference : See api-reference.md for all options, common endpoints (XCom, event-logs, backfills), and examples. - New project? See the setting-up-astro-project skill - Local environment?