airflow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIRFLOW_URL | Yes | Base URL of the Airflow API, for example https://airflow.example.com. | |
| AIRFLOW_TOKEN | No | Airflow API token. | |
| --allow-writes | No | Startup flag enabling write tools: set_dag_paused, restart_run, fail_run, edit_connection, and test_connection. | |
| AIRFLOW_AUTH_FILE | No | Absolute path to a mode 0600, gitignored, untracked *.secrets.json file containing either a token or username and password. | |
| --allow-connection-export | No | Startup flag enabling export_connection through an operator-configured privileged helper. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_dagsA | List DAGs using Airflow 3.3.1 API filters, pagination and sorting. *_pattern is case-insensitive substring matching; *_prefix_pattern is case-sensitive. Dates use ISO 8601 with timezone. Lists become repeated query parameters. Prefix order_by fields with '-' for descending order. Unset filters use API defaults. dag_id_regex adds Python regex search (inline flags supported), applied before offset/limit. Regex scans at most 1000 native-filtered candidates; limit=0 returns all matches. |
| list_tasksA | List task definitions in a DAG. This API supports order_by only (default task_id). For state, duration, queue, pool or attempt filters, use list_task_instances. task_id_regex adds Python regex search over actual IDs, with a 1000-candidate cap. |
| list_task_instancesA | List task executions with all Airflow 3.3.1 API query filters. Use '~' for all DAGs or runs. Date filters are timezone-aware ISO 8601 strings. Lists use repeated query parameters; order_by accepts '-' for descending order. cursor='' starts cursor pagination; pass returned next_cursor for the next page. When cursor is supplied, Airflow ignores offset. Patterns match substrings; prefix patterns are case-sensitive. No rendered fields or XCom values are returned. ID regexes use Python search with inline flags and combine with native filters using AND. Regex scans at most 1000 candidates before offset/limit pagination, forbids cursor, and returns a filtered total. With regex, limit=0 returns all matches. |
| list_runsC | List existing runs; never creates runs. |
| inspect_runA | Snapshot an existing run, its task attempts and elapsed wall-clock time (not summed task time). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
The five tools mostly target distinct resources: DAGs, tasks, runs, a run snapshot, and task instances. The only mild overlap is between inspect_run's task attempts and list_task_instances, but the descriptions make the run-level vs execution-level distinction reasonably clear.
All tool names use snake_case with a clear verb_noun pattern: list_runs, inspect_run, list_dags, list_tasks, and list_task_instances. The single inspect_ prefix variation is natural and does not break consistency.
Five tools is a well-scoped set for a read-oriented Airflow inspection server. Each tool covers a distinct listing or inspection need without redundant operations.
The server covers broad listing and run snapshot inspection, but it lacks key follow-up operations such as getting a single DAG or task instance, retrieving logs, or accessing XCom values. These gaps will limit agents trying to debug task failures beyond enumeration.