A **Model Context Protocol (MCP) server** for Apache Airflow 3 that provides essential tools for DAG management, monitoring, debugging, and
MCP Airflow Simple MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. A Model Context Protocol (MCP) server for Apache Airflow 3 that provides essential tools for DAG management, monitoring, debugging, and connection testing through the Airflow REST API v2.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
Once MCP Airflow Simple is connected, these are the calls the assistant has available:
get_dags — List all DAGs in Airflow. json { "only_active": false, "limit": 100 }get_dag_tasks — Get all tasks in a specific DAG. json { "dag_id": "example_dag" }trigger_dag_run — Trigger a new DAG run. json { "dag_id": "example_dag", "conf": {"key": "value"}, "logical_date": "2026-01-05T00:00:00Z" }clear_dag_run — Clear/retry a DAG run (resets failed tasks). json { "dag_id": "example_dag", "dag_run_id": "manual__2026-01-05T00:00:00+00:00", "dry_run": false }set_dag_state — The set_dag_state tool exposed by this serverget_dag_runs — Get DAG run history with optional state filtering. json { "dag_id": "example_dag", "state": "failed", "limit": 25 }get_task_instances — Get task instances for a specific DAG run. json { "dag_id": "example_dag", "dag_run_id": "manual__2026-01-05T00:00:00+00:00" }get_dag_stats — The get_dag_stats tool exposed by this serverget_task_logs — Get execution logs for a specific task instance. json { "dag_id": "example_dag", "dag_run_id": "manual__2026-01-05T00:00:00+00:00", "task_id"get_import_errors — The get_import_errors tool exposed by this serverget_connections — List all Airflow connections. json { "limit": 100 }get_connection — Get details of a specific connection. json { "connection_id": "postgres_default" }You will need one environment variable: GIT_AUTO_UPDATE. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the monitoring and observability options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. MCP Airflow Simple's toolset — get_dags, get_dag_tasks, trigger_dag_run and 11 more — is a fair guide to whether it matches your workflow. It is maintained by chayasin; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| get_dags | List all DAGs in Airflow. json { "only_active": false, "limit": 100 } |
| get_dag_tasks | Get all tasks in a specific DAG. json { "dag_id": "example_dag" } |
| trigger_dag_run | Trigger a new DAG run. json { "dag_id": "example_dag", "conf": {"key": "value"}, "logical_date": "2026-01-05T00:00:00Z" } |
| clear_dag_run | Clear/retry a DAG run (resets failed tasks). json { "dag_id": "example_dag", "dag_run_id": "manual__2026-01-05T00:00:00+00:00", "dry_run": false } |
| set_dag_state | The set_dag_state tool exposed by this server. |
| get_dag_runs | Get DAG run history with optional state filtering. json { "dag_id": "example_dag", "state": "failed", "limit": 25 } |
| get_task_instances | Get task instances for a specific DAG run. json { "dag_id": "example_dag", "dag_run_id": "manual__2026-01-05T00:00:00+00:00" } |
| get_dag_stats | The get_dag_stats tool exposed by this server. |
| get_task_logs | Get execution logs for a specific task instance. json { "dag_id": "example_dag", "dag_run_id": "manual__2026-01-05T00:00:00+00:00", "task_id": "example_task", "try_number": 1 } |
| get_import_errors | The get_import_errors tool exposed by this server. |
| get_connections | List all Airflow connections. json { "limit": 100 } |
| get_connection | Get details of a specific connection. json { "connection_id": "postgres_default" } |
| test_connection | Test connection accessibility. json { "connection_id": "postgres_default" } |
| check_health | Check Airflow system health (includes Metadatabase, Scheduler, Triggerer, and DagProcessor). json {} |
{
"mcpServers": {
"airflow": {
"command": "python",
"args": ["c:\\{path_to_your_folder}\\mcp-airflow-simple\\server.py"],
"env": {
"GIT_AUTO_UPDATE": "true"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GIT_AUTO_UPDATE | Configuration value read at startup. | Optional |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.