Airflow MCP
Provides tools for managing Apache Airflow DAGs, DAG runs, task instances, and logs via the Airflow REST API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Airflow MCP list the last 5 runs of DAG 'etl_pipeline'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Airflow MCP
A Model Context Protocol server that exposes Apache Airflow's REST API to AI agents (Claude Code, Claude Desktop, etc.), so they can inspect and operate on DAGs, DAG runs, task instances and logs.
The server is general-purpose: point it at any Airflow 2.x/3.x instance via AIRFLOW_BASE_URL. It has no knowledge of any specific project's DAGs, and does not edit DAG files or manage Airflow users/roles/pools/connections.
Tools
Read-only
Tool | Description | Parameters |
| List DAGs, optionally filtered by tag or active state |
|
| Get metadata for a single DAG |
|
| List DAG run history |
|
| Get details for a single DAG run, including trigger conf |
|
| List task instances and their state for a DAG run |
|
| Get logs for a task instance, truncated to |
|
Write (sensitive — annotated so MCP clients require confirmation)
Tool | Description | Parameters |
| Trigger a new DAG run (destructive, non-idempotent) |
|
| Pause a DAG (idempotent) |
|
| Resume a paused DAG (idempotent) |
|
Related MCP server: MCP Server Airflow Token
Requirements
Python >= 3.12
An Apache Airflow instance reachable over HTTP, with a user that has at least
Viewerrole (Opif you need the write tools)
Least privilege
Use a dedicated Airflow user for this server, scoped to the minimum role it needs:
Vieweris enough if you only register the read-only tools.Opis required if you also registertrigger_dag_run,pause_dagorunpause_dag.Never point this server at an
Adminaccount unless you have a specific reason to.
Quickstart
./install.shDetects whether you have Docker or uv installed, sets up .env (from .env.example, if missing), builds the image or syncs dependencies accordingly, and prints the .mcp.json snippet to register the server.
Setup
uv sync --group dev
cp .env.example .envFill in .env with your Airflow instance's URL and credentials.
Docker
No local Python/uv needed — build once, run anywhere Docker runs:
docker build -t mcp-airflow .
cp .env.example .env # fill in your Airflow credentialsRun in stdio mode (default, for MCP clients that spawn the process):
docker run -i --rm --env-file .env mcp-airflowRun in streamable-http mode (standalone service, listens on :8000):
docker run --rm -p 8000:8000 --env-file .env -e MCP_TRANSPORT=streamable-http mcp-airflowRegistering with an MCP client
stdio (recommended for local development)
{
"mcpServers": {
"airflow": {
"command": "uv",
"args": ["run", "mcp-airflow"],
"env": {
"AIRFLOW_BASE_URL": "http://localhost:8080",
"AIRFLOW_AUTH_MODE": "basic",
"AIRFLOW_USERNAME": "airflow",
"AIRFLOW_PASSWORD": "airflow"
}
}
}
}stdio via Docker
{
"mcpServers": {
"airflow": {
"command": "docker",
"args": ["run", "-i", "--rm", "--env-file", ".env", "mcp-airflow"]
}
}
}streamable-http (server running as a standalone process)
Start the server with MCP_TRANSPORT=streamable-http uv run mcp-airflow (or the Docker command above), then register:
{
"mcpServers": {
"airflow": {
"url": "http://localhost:8000/mcp"
}
}
}Development
uv run pytest
uv run ruff check .
uv run mypy srcAvailable Tools
9 toolsget_dagC
Get metadata for a single Airflow DAG.
Inputs: dag_id (required). Returns: object
get_dag_runC
Get details for a single DAG run, including its trigger conf.
Inputs: dag_id (required), dag_run_id (required). Returns: object
get_task_logsB
Get logs for a task instance, truncated to AIRFLOW_LOG_MAX_LINES.
Inputs: dag_id (required), task_id (required), dag_run_id (required), try_number. Returns: result
list_dag_runsC
List DAG run history for a given DAG.
Inputs: dag_id (required), limit, state. Returns: result
list_dagsA
List Airflow DAGs, optionally filtered by tag or active state.
Inputs: tags, limit, offset, only_active. Returns: result
list_task_instancesB
List task instances and their state for a given DAG run.
Inputs: dag_id (required), dag_run_id (required). Returns: result
pause_dagAIdempotent
Pause a DAG. Reversible, but affects the shared scheduler.
Inputs: dag_id (required). Returns: object
trigger_dag_runBDestructive
Trigger a new DAG run. Sensitive: creates a new, irreversible execution.
Inputs: dag_id (required), conf, logical_date. Returns: object
unpause_dagBIdempotent
Resume a paused DAG.
Inputs: dag_id (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool targets a distinct entity or action: DAG metadata, DAG run details, task logs, listing operations, and state changes (pause, unpause, trigger). No overlapping purposes.
All names follow a consistent verb_noun pattern with underscores (e.g., get_dag, list_dags, trigger_dag_run). Verbs are clear and nouns precisely identify the resource.
9 tools is appropriate for an Airflow MCP server, covering core operations without redundancy. The count is well-scoped for the domain.
Covers essential DAG, DAG run, and task instance operations. Minor gaps like clearing task instances or updating DAG configuration are missing but not critical for typical monitoring and triggering workflows.
Maintenance
Related MCP Connectors
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
The Mercado Pago MCP Server implements the Model Context Protocol to provide AI agents and LLMs with access to Mercado Pago's APIs and tools within compatible development environments. It acts as an intermediary that translates Mercado Pago resources into executable functions (tools) that AI applications can invoke to perform actions and automate flows. The server simplifies integration, enables using documentation to implement or improve code, and optimizes operations through natural language interactions without manual implementations.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol Server that enables LLMs to interact with and execute REST API calls through natural language prompts, supporting GET/PUT/POST/PATCH operations on configured APIs.6Apache 2.0
- AlicenseCqualityDmaintenanceA Model Context Protocol server that wraps Apache Airflow's REST API with Bearer token authentication support, enabling AI assistants to interact with Airflow deployments including Astronomer Cloud.66MIT

astro-airflow-mcpofficial
AlicenseAqualityFmaintenanceAn MCP server that enables AI assistants to interact with Apache Airflow's REST API for DAG management, task monitoring, and system diagnostics. It provides comprehensive tools for triggering workflows, retrieving logs, and inspecting system health across Airflow 2.x and 3.x versions.3113Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables interaction with Apache Airflow through the Model Context Protocol, allowing users to manage DAGs, task instances, variables, connections, pools, XComs, and datasets.MIT