ClickHouse's observability MCP server — investigate logs, traces and metrics with semantic tools rather than raw SQL, hosted or self-hosted.
8 views
Astro Airflow MCP Server
by Astronomer
Added to Onei
1 views
Apache-2.0
Summary
Astronomer's MCP server for Apache Airflow: 30+ tools over the Airflow REST API, with consolidated helpers that explore a DAG, diagnose a failed run or summarise system health in a single call. Works with Airflow 2.x and 3.x.
Features
- Consolidated explore_dag, diagnose_dag_run and get_system_health tools answer in one call what would otherwise take five
- 30+ fine-grained tools for DAGs, tasks, pools, Variables, Connections, assets, plugins and providers
- MCP resources for version, providers, plugins and config, plus troubleshooting and onboarding prompts
- Automatic Airflow version detection; supports both Airflow 2.x and 3.x
- Runs standalone via uvx, or as an Airflow 3.x plugin for a single shared deployment
- Basic-auth or bearer-token authentication; stdio or HTTP transport
Installation
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
Description
Debugging a failed Airflow run is a scavenger hunt through the UI — find the DAG, find the run, find the failed task, open the log, check the connection, check the pool. The Astro Airflow MCP Server is Astronomer's Model Context Protocol server for Apache Airflow, and its most useful design decision is that it does not stop at wrapping one endpoint per tool.
Consolidated tools, because agents pay per round trip
Alongside 30+ fine-grained tools it registers three agent-optimised ones:
- `explore_dag` — everything about a DAG in one response instead of five calls.
- `diagnose_dag_run` — the failed-run investigation, assembled: the run, its tasks, and the failure context.
- `get_system_health` — a system overview with health metrics.
That shape matters because each extra tool call is latency, tokens and another chance for the agent to lose the thread. A single diagnose_dag_run gets an assistant to a hypothesis in one hop.
Everything else it covers
The fine-grained tools span DAG operations (list, details, source code, statistics, trigger, pause and unpause), task management, pools, Variables and Connections, assets and datasets, plugin and provider inventories, and configuration. It also publishes MCP resources — airflow://version, airflow://providers, airflow://plugins, airflow://config — and MCP prompts for troubleshooting workflows, health checks and onboarding.
Deployment
It is a Python package (3.10+) on PyPI and runs with no install step:
{
"mcpServers": {
"airflow": { "command": "uvx", "args": ["astro-airflow-mcp", "--transport", "stdio"] }
}
}Point it at a webserver with AIRFLOW_API_URL plus either AIRFLOW_USERNAME/AIRFLOW_PASSWORD or AIRFLOW_AUTH_TOKEN. It detects the Airflow version automatically and supports both 2.x and 3.x, and on Airflow 3.x it can run as an Airflow plugin instead of a standalone process — one deployment for the whole team rather than credentials on every laptop. MCP_TRANSPORT, MCP_HOST and MCP_PORT switch it to HTTP.
Who it is for
Data engineers on call for a scheduler. The read paths (explore, diagnose, health) are where it earns its keep; triggering and pausing DAGs is available, so give the API user the grants you would give a junior on-call engineer and no more.
Apache 2.0, maintained by Astronomer.
Related MCP Servers
Vanta's official remote MCP server — query controls, tests, vendors, vulnerabilities and policies across SOC 2 and ISO 27001, and remediate failing tests from your agent.
Turso's hosted MCP server — manage Turso Cloud databases, branch them point-in-time and run SQL from a coding agent, authorised over OAuth with no API token to paste.
Google's official Firebase MCP server — 70+ tools across Firestore, Auth, Crashlytics, Cloud Functions, Storage, Messaging and Remote Config, shipped inside the Firebase CLI.