Airbyte MCP connector
The Airbyte connector brings your Airbyte sources, destinations, connections, applications and tags to Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client through one governed endpoint, with every change made under the person who signed in.
- Connects with an API key
- Free 14-day trial
- No credit card
List every Airbyte connection that syncs into our Snowflake destination.
Working in Airbyte with Elaichi
-
List all Airbyte applications
-
Get single Airbyte application by ID
-
List all Airbyte sources
How to connect Airbyte to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Airbyte 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.
Airbyte 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.
Airbyte 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.
Airbyte 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.
Airbyte 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 Airbyte 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 Airbyte through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Airbyte is logged.
-
Data engineering
Set up a new source after a request
Create the Postgres or Salesforce source, point it at the warehouse destination, and create the connection between them, all from one chat instead of a run of forms.
-
Analytics
Find which connection feeds a dashboard
Ask which Airbyte connections land in the analytics destination and which sources they pull from, so you know where a number came from before you trust it.
-
RevOps
Get the CRM into the warehouse
Start the sign-in for a new HubSpot or Salesforce source, then wire it to the existing destination so pipeline data shows up alongside everything else.
-
Marketing ops
Check which ad platforms are syncing
List the sources tagged for marketing, see which destination each one feeds, and update a source whose settings changed after a platform migration.
-
IT
Clean up stale sources and destinations
Pull the full list of sources and destinations, spot the ones nobody has touched, and delete them so the workspace only holds what is still in use.
-
Security
Issue and retire application tokens
List the Airbyte applications in your workspace, create a token for a service that needs one, and delete an application the moment it should no longer have access.
Try asking
- “List every Airbyte connection that syncs into our Snowflake destination.”
- “Which sources are tagged marketing and where does each one land?”
- “Create a Postgres source for the billing database and connect it.”
What connecting Airbyte gets you
6 screens from Elaichi, each doing one job for your Airbyte account.
Ask Elaichi to work across your apps.
List every Airbyte connection that syncs into our Snowflake destination.
Which sources are tagged marketing and where does each one land?
Create a Postgres source for the billing database and connect it.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about your Airbyte pipelines in plain language.
Answers come from live sources, destinations and connections, not from a stale wiki.
Copy the endpoint
AI apps
One Airbyte endpoint for every MCP client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK and no shared API key.
Tool catalog
63 Airbyte tools, no custom code required.
Sources, destinations, connections, applications and tags, every one covered out of the box.
Toolboxes
Each team gets its own Airbyte toolbox.
Data engineering manages sources and destinations, analytics works with connections, scoped per team.
Shared connections
Share Airbyte access, never the API key.
One person connects Airbyte, teammates work through it, and the credential stays out of sight.
Audit log
Every Airbyte change has a name on it.
When, who, what happened and which source or connection, in one append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Airbyte digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch sources
Airbyte
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
Airbyte
Queued
Workflows
A schedule starts the work, you approve it.
Airbyte connections are fetched, grouped, drafted into a digest, approved, then posted back.
Airbyte health
Refreshed 4 minutes ago · every 15 minutes · from the sources collection
Sources
1,284 ↓ 12%
Destinations
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Sources created
Last 14 days
By team
Share of activity
Data platform 34%
Analytics 27%
RevOps 21%
Marketing 18%
Collections and dashboards
Airbyte health, computed, not asked for.
Numbers come straight from Airbyte, no model in the reporting, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Airbyte
All three can connect Airbyte 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 Airbyte tools | Allow or restrict single Airbyte 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 Airbyte 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.
Airbyte tools for your AI agents
63 tools are ready to call through Elaichi's MCP endpoint the moment you connect Airbyte, 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 Airbyte to Claude?
Connect Airbyte in Elaichi by pasting your Airbyte API key when prompted, then paste https://api.elaichi.ai/mcp into Claude under Customize, then Connectors, then Add. There is no OAuth application to register in Airbyte and no client ID or secret to generate. The whole thing takes a few minutes.
Does Airbyte work with ChatGPT and Cursor as well as Claude?
Yes. Once Airbyte is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Airbyte once and every client picks it up.
What can an AI agent actually do with my Airbyte data?
It can list your Airbyte sources, destinations and connections, create new ones, update a source or destination whose settings changed, delete what is no longer needed, and manage applications, tokens and tags. In practice that means asking which connection feeds the warehouse, or telling it to set up a new source and wire it to a destination. Short, concrete asks work better than long paragraphs.
Does connecting Airbyte give the AI every workspace and pipeline?
No. Access to Airbyte follows the person who signed in, so an agent can only reach the workspaces, sources and destinations that person can already reach in Airbyte. Elaichi can narrow that access further with roles and restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in Airbyte?
Yes. Restrictions in Elaichi work per action, so you can restrict deleting Airbyte sources, destinations or connections for a role or for one person while leaving listing and creating open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to an Airbyte connection when someone leaves?
Offboarding that person in Elaichi ends their access to Airbyte at once, across every client they used. A shared Airbyte connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Airbyte once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Does the Airbyte MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Airbyte 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 Airbyte?
Yes. Both let Claude, ChatGPT or Cursor use Airbyte. 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 Airbyte call.
How is Elaichi different from Composio for Airbyte?
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 Airbyte: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Airbyte 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