MCP.so
ログイン

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

@abhishekbhakat

基本情報

カテゴリ

データと分析

ライセンス

MIT

トランスポート

stdio

作者

abhishekbhakat

airflow-mcp-server: An MCP Server for controlling Airflow について

MCP Server for Apache Airflow

airflow-mcp-server: An MCP Server for controlling Airflow の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

airflow-mcp-server: An MCP Server for controlling Airflow のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

What is airflow-mcp-server?

airflow-mcp-server is a Model Context Protocol server that enables AI assistants to control Apache Airflow 3 via Airflow APIs. It connects to an Airflow instance using a JWT token and exposes tools for managing DAGs, tasks, connections, and more.

How to use airflow-mcp-server?

Install via uvx and configure it in your MCP client (e.g., Claude Desktop) with the Airflow base URL and JWT token. Start with airflow-mcp-server --base-url http://localhost:8080 --auth-token <jwt>. Use --safe for read-only mode or --unsafe for full access (default). Choose between stdio (default) or HTTP transport with --http.

Key features of airflow-mcp-server

  • Controls Airflow via the Airflow REST API
  • Supports safe (read-only) and unsafe (full access) operation modes
  • Offers hierarchical tool discovery or static tools
  • Provides stdio, HTTP, and deprecated SSE transport options
  • Accepts local Markdown files as read-only resources
  • Requires only JWT authentication (Airflow 3)

Use cases of airflow-mcp-server

  • Querying DAG statuses, task instances, and pipeline runs
  • Triggering or pausing DAGs from an AI assistant
  • Viewing and managing Airflow connections and variables
  • Troubleshooting Airflow runs with natural language commands
  • Automating Airflow workflows via chat or agent interfaces

よくある質問

1

What authentication is required?

Only JWT token authentication is supported. Cookie and basic auth are no longer available in Airflow 3.0. Provide the token via `--auth-token`.

2

What transport options are available?

The server supports stdio (default for direct process communication) and HTTP (recommended for web deployments). SSE transport is deprecated.

3

How does safe mode differ from unsafe mode?

Safe mode (`--safe`) restricts all tools to read-only GET requests. Unsafe mode (`--unsafe`, the default) allows all operations including modifications.

4

How are tools organized?

By default, tools are organized hierarchically by categories (DAGs, Tasks, Connections, etc.). Use `--static-tools` to list all tools immediately without browsing categories.

5

Can I provide local documentation as resources?

Yes. Use `--resources-dir <path>` to point to a folder of Markdown files. Each `.md` file becomes a read-only resource visible in the MCP client.

コメント

「データと分析」の他のコンテンツ