Apache Airflow MCP connector
The Apache Airflow connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent manage Apache Airflow users, roles, and permissions through one governed endpoint, with every change running as the signed-in person and recorded in an audit log.
- Connects with an API key
- Free 14-day trial
- No credit card
List all Apache Airflow users and their assigned roles.
Working in Apache Airflow with Elaichi
-
List all Apache Airflow users
-
Get single Apache Airflow user by ID
-
List all Apache Airflow roles
How to connect Apache Airflow to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Apache Airflow MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Apache Airflow MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Apache Airflow MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Apache Airflow MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Apache Airflow MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Apache Airflow to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Apache Airflow through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Apache Airflow is logged.
-
Data Engineering
Onboard a new engineer to Airflow
Create the Apache Airflow account for a new hire and attach the right role in one request, instead of clicking through the admin screens.
-
IT
Find out who still has access
Ask for the full list of Apache Airflow users and see at a glance which accounts belong to people who have moved teams or left.
-
Security
Review what a role can do
Pull up any Apache Airflow role, check the permissions behind it, and compare it against what the team actually needs.
-
Platform
Build a role for a new team
Create an Apache Airflow role scoped to what the analytics team needs, then adjust it as the team's work changes.
-
Compliance
Answer an access audit in minutes
List every Apache Airflow user, their roles, and the permissions those roles carry, ready to paste into an access review.
-
IT
Clean up a departed user's account
Look up the Apache Airflow user by ID, confirm the details, and remove the account when someone leaves the organization.
Try asking
- “List all Apache Airflow users and their assigned roles.”
- “Which Apache Airflow roles carry write permissions?”
- “Create an Apache Airflow user on the Viewer role.”
What connecting Apache Airflow gets you
6 screens from Elaichi, each doing one job for your Apache Airflow account.
Ask Elaichi to work across your apps.
List all Apache Airflow users and their assigned roles.
Which Apache Airflow roles carry write permissions?
Create an Apache Airflow user on the Viewer role.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Apache Airflow users in plain language.
Starter prompts return answers from live Apache Airflow users, roles and permissions.
Copy the endpoint
AI apps
One endpoint reaches Apache Airflow from any client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, no SDK and no shared key.
Tool catalog
11 Apache Airflow tools, no custom code.
Read, create, update and delete users and roles across Apache Airflow resources and methods.
Toolboxes
Every team gets its own Airflow toolbox.
Curate Apache Airflow toolboxes per team, from platform engineering to data operations.
Shared connections
Teammates use Airflow without seeing a credential.
The connections table shows who connected each Apache Airflow account and its sharing.
Audit log
Every Airflow role change has a name on it.
When, who, what happened, type and resource for each Apache Airflow call.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Apache Airflow digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Apache Airflow
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Apache Airflow
Queued
Automations
A schedule audits Airflow roles end to end.
Six steps fetch users and roles, group them, draft a digest, then post back.
Apache Airflow health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Roles
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Platform prod 34%
Data engineering 27%
Analytics EMEA 21%
Security review 18%
Collections and dashboards
Airflow user and role numbers, computed on schedule.
Four metrics, 14 days of users created and a breakdown by team.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Apache Airflow
All three can connect Apache Airflow to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Apache Airflow tools | Allow or restrict single Apache Airflow tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Apache Airflow call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Apache Airflow tools for your AI agents
11 tools are ready to call through Elaichi's MCP endpoint the moment you connect Apache Airflow, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Apache Airflow to Claude?
Connect Apache Airflow in Elaichi first: paste an Apache Airflow API key when prompted, and the connection is ready. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint.
Does Apache Airflow work with ChatGPT and Cursor as well as Claude?
Yes. Once Apache Airflow is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Apache Airflow once and every client can use it.
What can an AI agent actually do with my Apache Airflow data?
With this connector an agent can list Apache Airflow users, look up a single user, create new accounts, update them, and remove them. It can do the same for Apache Airflow roles, and it can list the permissions available in your deployment. It does not run or edit pipelines; this connector is about who has access to Apache Airflow and what they are allowed to do.
Does connecting Apache Airflow give the AI every user and role?
The AI only sees what the Apache Airflow API key it runs under is allowed to see, and every action is logged against the person who signed in to Elaichi. Elaichi can narrow that access further, for example to read-only on Apache Airflow users and roles, but it can never grant more than the key itself has.
Can I stop an agent from deleting or changing things in Apache Airflow?
Yes. Restrictions in Elaichi apply per action, so you can allow listing and looking up Apache Airflow users and roles while restricting create, update, and delete. A restricted action still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.
What happens to an Apache Airflow connection when someone leaves?
When you offboard someone in Elaichi, their access to Apache Airflow through Elaichi ends at once, across every client they used. If the connection was shared, it keeps working for everyone else on the team. Disconnecting Apache Airflow once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client in one step.
Does the Apache Airflow MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Apache Airflow is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Apache Airflow?
Yes. Both let Claude, ChatGPT or Cursor use Apache Airflow. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Apache Airflow call.
How is Elaichi different from Composio for Apache Airflow?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Apache Airflow: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Apache Airflow in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot