Loading...
This MCP server provides a standardized interface to Apache Airflow's REST API, enabling interaction with DAGs, tasks, variables, connections, and other Airflow components.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
This MCP server provides a standardized interface to Apache Airflow's REST API, enabling interaction with DAGs, tasks, variables, connections, and other Airflow components.
This MCP server offers extensive control over Apache Airflow. It is safe to use for read-only operations and monitoring. However, caution is advised when performing write or delete operations, especially when dealing with sensitive data or critical workflows. Proper authentication and authorization are crucial to mitigate risks.
Performance depends on the complexity of the Airflow DAGs and the resources available to the Airflow cluster. Optimize DAGs for efficient execution and scale the cluster as needed.
Cost depends on the resources consumed by the Airflow cluster and the frequency of API calls. Monitor resource usage and optimize API call frequency to minimize costs.
npx -y @smithery/cli install @yangkyeongmo/mcp-server-apache-airflow --client claude{
"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"
}
}
}
}AIRFLOW_HOSTAIRFLOW_USERNAMEAIRFLOW_PASSWORDAIRFLOW_API_VERSIONList DAGsRetrieves a list of available DAGs in Airflow.
Read-only operation, no side effects.
Create DAG RunTriggers a new DAG run for a specified DAG.
Creates a new DAG run, potentially consuming resources.
Update ConnectionModifies an existing connection in Airflow.
Modifies connection details, potentially affecting access to external systems.
Delete DAGRemoves a DAG from Airflow.
Destructive operation, permanently removes the DAG.
Set Task Instances StateUpdates the state of specific task instances within a DAG run.
Can alter the execution flow and outcome of a DAG run.
API Key
hybrid
This MCP server offers extensive control over Apache Airflow. It is safe to use for read-only operations and monitoring. However, caution is advised when performing write or delete operations, especially when dealing with sensitive data or critical workflows. Proper authentication and authorization are crucial to mitigate risks.
Autonomy is determined by the permissions granted to the API key used to access the Airflow REST API. Exercise caution when granting write or delete permissions.
Production Tip
Implement robust error handling and monitoring to ensure the reliability of Airflow workflows in production.
The MCP server uses the Apache Airflow REST API, which typically supports authentication via API keys, OAuth, or other configured authentication mechanisms.
Use Airflow's built-in secrets management features to store sensitive credentials securely. Avoid storing credentials directly in DAG code or variables.
Yes, the server provides endpoints to create and manage DAG runs, allowing you to trigger DAGs programmatically.
The server provides endpoints to retrieve DAG run details, including status, logs, and task instance information.
Airflow's built-in retry logic will attempt to rerun the task based on the configured retry policy. You can also configure error handling to take specific actions on task failure.
Yes, you can update DAGs using the provided API endpoints. However, be cautious when updating DAGs in production, as it may disrupt running workflows.
The server provides endpoints to create, read, update, and delete Airflow variables. Use variables to store configuration parameters and other dynamic values.