abhishekbhakat/airflow-mcp-server

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",
" "
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",
" "
> Note:
> - Set baseurl 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 ${baseurl}/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
#### 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
> 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