
Airflow Mcp Server
io.github.abhishekbhakat由 GitHub 账号 abhishekbhakat 发布v0.9.0更新于 Oct 27, 2026
An MCP server for Apache Airflow
概览
一个让助手通过 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 规范。
安装
在 SourceWeft 中
- 打开 控制台中的 Airflow Mcp Server,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
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)
See CONFIG.md for IDE-specific configuration examples across popular MCP clients.
HTTP Transport
Note:
- Set
base_urlto the root Airflow URL (e.g.,http://localhost:8080).- Do not include
/api/v2in 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:
HTTP Transport
Uses Streamable HTTP for better scalability and web compatibility:
Note: SSE transport is deprecated. Use
--httpfor 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:
To explicitly start in unsafe mode (though this is default):
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:
Command Line Options
Using Resources
Point the server at a folder of Markdown guides whenever you want agents to reference local documentation:
- Every top-level
.md/.markdownfile becomes a read-only resource (file:///<slug>) visible in your MCP client. - The first
# Headingin each file (if present) is used as the resource title; otherwise the filename stem is used. - Set
AIRFLOW_MCP_RESOURCES_DIR=/path/to/docsif 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版本历史
1- v0.9.0最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分