airflow-mcp-server: An MCP Server for controlling Airflow

Created By
abhishekbhakata year ago
MCP Server for Apache Airflow
Overview

what is airflow-mcp-server?

The airflow-mcp-server is a Model Context Protocol server designed for controlling Apache Airflow through its APIs, allowing for enhanced interaction and automation.

how to use airflow-mcp-server?

To use the airflow-mcp-server, set up the server with the required environment variables and run the command specified in the setup instructions. You can integrate it with Claude Desktop for seamless operation.

key features of airflow-mcp-server?

  • Complete access to an Airflow deployment for AI integration.
  • Read-only access via Airflow Plugin for better understanding of deployments.
  • Ability to automate DAG creation and scheduling through AI.

use cases of airflow-mcp-server?

  1. Automating the creation and management of DAGs in Airflow.
  2. Providing insights into Airflow deployments for large teams.
  3. Enhancing AI capabilities in managing workflows within Airflow.

FAQ from airflow-mcp-server?

  • Can I use airflow-mcp-server with any version of Airflow?

The airflow-mcp-server is designed to work with the Apache Airflow REST API, so compatibility depends on the API version.

  • Is there a demo available for airflow-mcp-server?

Yes! A demo video is available on the project's GitHub page.

  • How do I set up the airflow-mcp-server?

Follow the setup instructions provided in the documentation, including downloading the OpenAPI spec from the Airflow REST API.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
abhishekbhakat
Star
13
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago