pulsemcp verified Safe content atomic mcp-remote

Apache Airflow (Bearer Token)

This MCP server provides AI assistants with comprehensive Apache Airflow management capabilities through Bearer token authentication, built by Nikhil Ganage as a fork of Gyeongmo Yang's original implementation with enhanced token-based security support. The implementation exposes the full Airflow REST API including DAG operations (listing, triggering, pausing), task instance management, connection handling, variable management, dataset operations, and monitoring functions, with optional read-only mode for safe querying and automatic UI link generation for enhanced workflow visibility. Serves data engineers needing AI-powered Airflow administration, teams requiring programmatic DAG management through conversational interfaces, and organizations wanting to integrate Airflow operations into their AI workflows with secure token-based authentication for cloud deployments like Astronomer.

Cognium trust score

99%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: devops-ci
Source: PulseMCP
Repository: github.com/nikhil-ganage/mcp-server-airflow-token
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve Apache Airflow (Bearer Token) from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"