airflow-mcp-server
by MCP-Mirror
An MCP (Model Context Protocol) server for controlling Airflow via Airflow APIs. It allows interaction with Airflow instances using the Model Context Protocol.
Last updated: N/A
What is airflow-mcp-server?
This is a Model Context Protocol (MCP) server designed to control and interact with Apache Airflow instances. It leverages Airflow's APIs to provide a standardized way to manage and monitor Airflow workflows.
How to use airflow-mcp-server?
To use the server, configure it with the Airflow base URL and a valid JWT token for authentication. You can then interact with the server using the Model Context Protocol. The provided JSON configuration snippet demonstrates how to integrate it with Claude Desktop. You can start the server in either safe mode (read-only) or unsafe mode (full access).
Key features of airflow-mcp-server
Airflow 3 readiness
OpenAPI Spec parsing
Safe/Unsafe operation modes
Airflow config fetch for page limit
JWT Authentication
Use cases of airflow-mcp-server
Automating Airflow workflow management
Integrating Airflow with other MCP-compatible tools
Monitoring Airflow instance status
Triggering Airflow DAGs remotely
Managing Airflow configurations
FAQ from airflow-mcp-server
What authentication methods are supported?
What authentication methods are supported?
Only JWT authentication is supported in Airflow 3.0.
What is the default page limit for API responses?
What is the default page limit for API responses?
The default page limit is 100 items, configurable in the airflow.cfg file.
What is Safe Mode?
What is Safe Mode?
Safe Mode allows only read-only operations (GET requests), preventing modifications to the Airflow instance.
What is Unsafe Mode?
What is Unsafe Mode?
Unsafe Mode allows all operations, including modifications to the Airflow instance. It is the default mode.
Where do I find the OpenAPI spec?
Where do I find the OpenAPI spec?
The server automatically fetches the OpenAPI spec from ${base_url}/openapi.json
.