MCP Server Apache Airflow

🚀 Apache Airflow MCP Server

The Apache Airflow MCP Server is a tool for managing third - party services integrated with Airflow, enabling users to execute various maintenance commands and handle related tasks.

🚀 Quick Start

To start using the Apache Airflow MCP Server, you need to complete the installation and configuration steps. For detailed information, please refer to the "📦 Installation" and "💻 Usage Examples" sections.

✨ Features

Introduction

MCP (Maintenance Command Processor) is a tool for Apache Airflow, used to manage third - party services integrated with Airflow. Through MCP, you can execute various maintenance commands and handle related tasks.

Supported API Groups

The following are all the API groups supported by the MCP server and their corresponding interfaces:

📦 Installation

Dependencies

This project depends on the official Apache Airflow client library (apache - airflow - client), which will be automatically handled during installation.

Environment Variables

Set the following environment variables:

AIRFLOW_HOST=<Your-Airflow-Host>
AIRFLOW_USERNAME=<Your-Airflow-Username>
AIRFLOW_PASSWORD=<Your-Airflow-Password>

Integration with Claude Desktop

Add the following content to the claude_desktop_config.json file:

{
  "mcpServers": {
    "mcp-server-apache-airflow": {
      "command": "uvx",
      "args": ["mcp-server-apache-airflow"],
      "env": {
        "AIRFLOW_HOST": "https://Your-Airflow-Host",
        "AIRFLOW_USERNAME": "Your-Username",
        "AIRFLOW_PASSWORD": "Your-Password"
      }
    }
  }
}

The alternative configuration using uv is as follows:

{
  "mcpServers": {
    "mcp-server-apache-airflow": {
      "command": "uv",
      "args": [
        "--directory",
        "/Actual-Path/mcp-server-apache-airflow",
        "run",
        "mcp-server-apache-airflow"
      ],
      "env": {
        "AIRFLOW_HOST": "https://Your-Airflow-Host",
        "AIRFLOW_USERNAME": "Your-Username",
        "AIRFLOW_PASSWORD": "Your-Password"
      }
    }
  }
}

Replace /Actual-Path/mcp-server-apache-airflow with the actual location where you cloned the code.

Custom API Groups

Select the API groups to use via the --apis flag:

# Enable all default API groups
$ mcp-server-apache-airflow --apis default

# Enable specific API groups (e.g., config, dag)
$ mcp-server-apache-airflow --apis config,dag

💻 Usage Examples

Environment Variable Configuration

Set the following environment variables:

• AIRFLOW_HOST: The address of the Airflow server, defaulting to http://localhost:8080
• AIRFLOW_USERNAME: The login username, defaulting to admin
• AIRFLOW_PASSWORD: The user password, defaulting to <PASSWORD>

Starting the MCP Service

Execute the following command in the project root directory to start the MCP server:

$ python -m mcp_server --apis default

🔧 Technical Details

API Endpoints

Configuration Interface

• Get Configuration

  GET /api/v1/config
  

Connection Interface

• List All Connections

  GET /api/v1/connections
  

• Delete a Specified Connection

  DELETE /api/v1/connections/{connection_id}
  

DAG Interface

• Create or List DAGs

  POST, GET /api/v1/dags
  

• Get Information about a Specified DAG

  GET /api/v1/dags/{dag_id}
  

• Delete a Specified DAG

  DELETE /api/v1/dags/{dag_id}
  

• Pause or Resume a DAG

  PATCH /api/v1/dags/{dag_id}/paused
  

DAG Run Interface

• Create or List DAG Runs

  POST, GET /api/v1/dagruns
  

• Get Information about a Specified DAG Run

  GET /api/v1/dagruns/{dag_run_id}
  

Dataset Interface

• Create or List Datasets

  POST, GET /api/v1/datasets
  

• Delete a Specified Dataset

  DELETE /api/v1/datasets/{dataset_uri}
  

• Get Queued Events Associated with a Dataset

  GET /api/v1/datasets/{dataset_uri}/dag_runs/queued_events
  

• Delete Queued Events Associated with a Dataset

  DELETE /api/v1/datasets/{dataset_uri}/dag_runs/queued_events
  

Event Log Interface

• Get a Specified Event Log

  GET /api/v1/event_logs/{event_log_id}
  

• Delete a Specified Event Log

  DELETE /api/v1/event_logs/{event_log_id}
  

Import Error Interface

• Get a Specified Import Error

  GET /api/v1/import_errors/{import_error_id}
  

• Delete a Specified Import Error

  DELETE /api/v1/import_errors/{import_error_id}
  

Monitoring Interface

• Get System Health Status

  GET /api/v1/health
  

Plugin Interface

• List All Plugins

  GET /api/v1/plugins
  

Provider Interface

• List All Providers

  GET /api/v1/providers
  

Task Instance Interface

• Create or List Task Instances

  POST, GET /api/v1/task_instances
  

• Get Information about a Specified Task Instance

  GET /api/v1/task_instances/{task_instance_id}
  

• Update or Delete a Specified Task Instance

  PATCH, DELETE /api/v1/task_instances/{task_instance_id}
  

• List Task Instances under a DAG

  GET /api/v1/dags/{dag_id}/task_instances
  

Variable Interface

• Create or List Variables

  POST, GET /api/v1/variables
  

• Get the Value of a Specified Variable

  GET /api/v1/variables/{variable_key}
  

• Delete a Specified Variable

  DELETE /api/v1/variables/{variable_key}
  

XCom Interface

• Create or List XCom Data

  POST, GET /api/v1/xcoms
  

• Get the Value of a Specified XCom

  GET /api/v1/xcoms/{xcom_key}
  

• Delete a Specified XCom

  DELETE /api/v1/xcoms/{xcom_key}
  

🤝 Contribution Guidelines

How to Contribute Code

1. Fork this repository.
2. Create a feature branch.
3. Commit your code and create a Pull Request.

How to Report Issues

Please submit the issues you encounter in the Issues section.

📄 License

[Add license information here]