@mhdd_24/airflow-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIRFLOW_BASE_URL | Yes | Airflow URL | |
| AIRFLOW_PASSWORD | Yes | Password | |
| AIRFLOW_USERNAME | Yes | User |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| airflow_statusB | Show dags configuration / health. |
| airflow_listC | List dags resources/items. |
| airflow_getA | Get a dags resource by id/name. |
| airflow_diagnoseC | Diagnostics / checklist for dags. |
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 4 tools
Most tools are clearly distinct (list vs get vs status), but 'airflow_status' and 'airflow_diagnose' overlap in intent—both appear to inspect health or state, making it ambiguous which to choose for a given diagnostic question.
All tools share the 'airflow_' prefix with snake_case, but 'airflow_status' uses a noun while the others use verbs (list, get, diagnose), creating a minor inconsistency in the naming pattern.
Four tools is a tight, focused set for an Airflow-oriented server. Each tool addresses a distinct need and none feel redundant or superfluous.
The set covers read-only inspection and diagnostics well, but lacks common Airflow DAG operations like pause/unpause, trigger, or delete. If the intended scope is monitoring only, this is fine; for management tasks, there are notable gaps.