AirTrack

Created By
Rakesh-infosrca year ago
Integrate mcp-server-airflow to Open Web UI
Overview

What is AirTrack?

AirTrack is a Model Context Protocol (MCP) server for Apache Airflow that enables standardized access to Directed Acyclic Graph (DAG) metadata, run status, and task insights, facilitating seamless integration with MCP clients for monitoring and automation.

How to use AirTrack?

To use AirTrack, set up the Airflow environment using Docker, and run the MPC server by following the provided instructions in the project documentation. Ensure both services are running for full functionality.

Key features of AirTrack?

  • Standardized access to Airflow's REST API through MCP.
  • Integration with various MCP clients for enhanced monitoring.
  • Future development plans for live updates, security enhancements, and AI troubleshooting.

Use cases of AirTrack?

  1. Monitoring Airflow DAGs and task statuses through a unified interface.
  2. Automating workflows that require interaction between Airflow and other applications.
  3. Enhancing Airflow's capabilities with real-time updates and analytics.

FAQ from AirTrack?

  • What is the purpose of AirTrack?

AirTrack serves to standardize interactions with Apache Airflow, making it easier to monitor and automate workflows.

  • How do I install AirTrack?

Follow the installation instructions in the project documentation, which includes setting up Docker and the MPC application.

  • Is AirTrack compatible with all versions of Airflow?

AirTrack is designed to work with the official Apache Airflow client library, ensuring compatibility with supported versions.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Rakesh-infosrc
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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