Airflow Mcp Server

io.github.abhishekbhakat由 GitHub 帳號 abhishekbhakat 發布v0.9.0更新於 Oct 27, 2026

An MCP server for Apache Airflow

概覽

AI 產生的概覽

一個讓助理透過 REST API 控制 Apache Airflow 3 執行個體的 MCP 伺服器,可瀏覽 DAG、任務與連線等操作。

可以做什麼
  • 依類別(DAG、任務、連線等)瀏覽 Airflow API 操作並選擇要執行的工具
  • 對設定的 Airflow 執行個體呼叫 REST 介面,安全模式下僅執行唯讀 GET 請求
  • 可將全部 API 操作一次以靜態工具提供,而非分層探索
  • 把本機 Markdown 指南作為唯讀資源提供給助理參考
  • 預設使用 stdio 傳輸,也可用 Streamable HTTP 供多個用戶端連線
適用情境
適合希望助理在桌面 MCP 用戶端中檢視或操作 Airflow 3 部署的情境,例如檢查 DAG、任務與連線,或在啟用非安全模式時觸發變更。
執行需求
以本機 Python 套件執行(例如透過 uvx)。需要 Airflow 基礎 URL(不含 /api/v2 後綴)以及有效的 JWT 驗證權杖,透過 AUTH_TOKEN 或 --auth-token 提供。需要能連線至 Airflow 執行個體的網路;伺服器會從基礎 URL 取得 OpenAPI 規格。
安裝前請注意
預設即為非安全模式,允許包含修改在內的所有操作;若只需唯讀存取請以 --safe 啟動。JWT 權杖可存取 Airflow API,請勿放入共用設定。HTTP 傳輸預設綁定 localhost,但可透過 --host 對外開放。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Airflow Mcp Server,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

airflow-mcp-server: An MCP Server for controlling Airflow 3

mcp-name: io.github.abhishekbhakat/airflow-mcp-server

MCPHub Certification

This MCP server is certified by MCPHub. This certification ensures that airflow-mcp-server follows best practices for Model Context Protocol implementation.

Find on Glama

[圖片]

Overview

A Model Context Protocol server for controlling Airflow via Airflow APIs.

Demo Video

https://github.com/user-attachments/assets/f3e60fff-8680-4dd9-b08e-fa7db655a705

Setup

Usage with Claude Desktop

Stdio Transport (Default)
json
{    "mcpServers": {        "airflow-mcp-server": {            "command": "uvx",            "args": [                "airflow-mcp-server",                "--base-url",                "http://localhost:8080",                "--auth-token",                "<jwt_token>"            ]        }    }}

See CONFIG.md for IDE-specific configuration examples across popular MCP clients.

HTTP Transport
json
{    "mcpServers": {        "airflow-mcp-server-http": {            "command": "uvx",            "args": [                "airflow-mcp-server",                "--http",                "--port",                "3000",                "--base-url",                "http://localhost:8080",                "--auth-token",                "<jwt_token>"            ]        }    }}

Note:

  • Set base_url to the root Airflow URL (e.g., http://localhost:8080).
  • Do not include /api/v2 in the base URL. The server will automatically fetch the OpenAPI spec from ${base_url}/openapi.json.
  • Only JWT token is required for authentication. Cookie and basic auth are no longer supported in Airflow 3.0.

Transport Options

The server supports multiple transport protocols:

Stdio Transport (Default)

Standard input/output transport for direct process communication:

bash
airflow-mcp-server --safe --base-url http://localhost:8080 --auth-token <jwt>
HTTP Transport

Uses Streamable HTTP for better scalability and web compatibility:

bash
airflow-mcp-server --safe --http --port 3000 --base-url http://localhost:8080 --auth-token <jwt>

Note: SSE transport is deprecated. Use --http for new deployments as it provides better bidirectional communication and is the recommended approach by FastMCP.

Operation Modes

The server supports two operation modes:

  • Safe Mode (--safe): Only allows read-only operations (GET requests). This is useful when you want to prevent any modifications to your Airflow instance.
  • Unsafe Mode (--unsafe): Allows all operations including modifications. This is the default mode.

To start in safe mode:

bash
airflow-mcp-server --safe

To explicitly start in unsafe mode (though this is default):

bash
airflow-mcp-server --unsafe

Tool Discovery Modes

The server supports two tool discovery approaches:

  • Hierarchical Discovery (default): Tools are organized by categories (DAGs, Tasks, Connections, etc.). Browse categories first, then select specific tools. More manageable for large APIs.
  • Static Tools (--static-tools): All tools available immediately. Better for programmatic access but can be overwhelming.

To use static tools:

bash
airflow-mcp-server --static-tools

Command Line Options

bash
Usage: airflow-mcp-server [OPTIONS]
  MCP server for Airflow
Options:  -v, --verbose      Increase verbosity  -s, --safe         Use only read-only tools  -u, --unsafe       Use all tools (default)  --static-tools     Use static tools instead of hierarchical discovery  --base-url TEXT    Airflow API base URL  --auth-token TEXT  Authentication token (JWT)  --http             Use HTTP (Streamable HTTP) transport instead of stdio  --sse              Use Server-Sent Events transport (deprecated, use --http                     instead)  --port INTEGER     Port to run HTTP/SSE server on (default: 3000)  --host TEXT        Host to bind HTTP/SSE server to (default: localhost)  --help             Show this message and exit.

Using Resources

Point the server at a folder of Markdown guides whenever you want agents to reference local documentation:

bash
airflow-mcp-server --base-url http://localhost:8080 --auth-token <jwt> --resources-dir ~/airflow-resources
  • Every top-level .md/.markdown file becomes a read-only resource (file:///<slug>) visible in your MCP client.
  • The first # Heading in each file (if present) is used as the resource title; otherwise the filename stem is used.
  • Set AIRFLOW_MCP_RESOURCES_DIR=/path/to/docs if you prefer environment-based configuration.
  • Update the files on disk and restart the server to refresh the resources list.

Considerations

Authentication

  • Only JWT authentication is supported in Airflow 3.0. You must provide a valid AUTH_TOKEN.

Page Limit

The default is 100 items, but you can change it using maximum_page_limit option in [api] section in the airflow.cfg file.

Transport Selection

  • Use stdio transport for direct process communication (default)
  • Use HTTP transport for web deployments, multiple clients, or when you need better scalability
  • Avoid SSE transport as it's deprecated in favor of HTTP transport

來源:README.md,提交 e080477

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.9.0最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分