Airbyte MCP Server for Claude
Connect Claude to your data through Airbyte's 50+ agent connectors — query CRMs, billing systems, project management tools, communication platforms, and more — with the official Airbyte remote MCP server for AI agents.
Open the source and read safety notes before installing.
Safety notes
- The server is hosted and managed by Airbyte — credentials for connected services are entered via browser OAuth flows or secure forms, never in the AI chat.
- Depending on the connector, the MCP can create and update records (not just read) — review Claude's proposed actions before confirming writes.
- Access is scoped by the permissions granted during OAuth; use least-privilege scopes for each connected service.
Privacy notes
- Data retrieved from connected services (contacts, deals, invoices, messages) is surfaced in Claude's context.
- All credential flows are browser-based and never transmitted through the AI chat interface.
Prerequisites
- An Airbyte account (free to start) and connected data sources.
- Authenticate via OAuth on first tool use — credentials for third-party services are entered in the browser, not in the chat.
- An MCP client such as Claude Code or Claude Desktop.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Scope
- Source repo
- Estimated setup
- 10 minutes
- Difficulty
- beginner
- Website
- https://airbyte.com
Full copyable content
{
"mcpServers": {
"airbyte-agent": {
"type": "http",
"url": "https://mcp.airbyte.ai/mcp"
}
}
}About this resource
Overview
The Airbyte Agent MCP Server is the official remote Model Context Protocol server from
Airbyte for AI agents. It exposes 50+ Airbyte agent connectors to Claude — enabling natural
language queries and actions across CRMs, billing systems, project management platforms,
communication tools, and more. The server is hosted and managed by Airbyte at
https://mcp.airbyte.ai/mcp; no local installation is required.
Authentication is via OAuth 2.0 with your Airbyte account; credentials for individual third-party services are entered in the browser, never in the AI chat, for security.
Key capabilities
- CRM data — list, search, and retrieve contacts, deals, leads, and accounts.
- Billing & finance — access invoices, subscriptions, and billing records.
- Project management — list issues, tasks, and project data.
- Communication — access messages, tickets, and support records.
- Create & update — some connectors support creating and updating records in addition to reading.
- Entity discovery — automatically discover available entities and actions per connected service.
Supported actions include list, get, search, create, and update — varying by connector.
How it compares
| Server | Data sources covered | Write actions | No local install | Auth |
|---|---|---|---|---|
| Airbyte MCP | 50+ connectors | Yes (per-connector) | Yes | OAuth |
| Zapier MCP | 7000+ apps (read-heavy) | Limited | Yes | OAuth |
| Composio MCP | 100+ tools | Yes | Yes | OAuth |
| n8n MCP | 400+ integrations | Yes | No (self-hosted) | API key |
Airbyte's MCP is notable for its deep, schema-aware data access — each connector exposes structured entity types rather than generic webhook actions.
Installation
Claude Code
claude mcp add --transport http airbyte-agent https://mcp.airbyte.ai/mcp
After adding, run /mcp in Claude Code to connect your Airbyte account and configure data
source access.
Claude Desktop
Open Settings → Connectors to add the Airbyte MCP server through the built-in interface.
Requirements
- An Airbyte account with connected data sources.
- An MCP client (Claude Code or Claude Desktop).
Security
- Credentials are always entered in the browser — Airbyte's servers handle token storage.
- Scope each connected service to the minimum required permissions during OAuth consent.
- Review write operations (create/update) before confirming — these modify real data in connected systems.
Source Verification Notes
Verified on 2026-06-18:
- Airbyte's Agent MCP documentation at
docs.airbyte.com/ai-agents/interfaces/mcp/confirms the hosted endpointhttps://mcp.airbyte.ai/mcp, OAuth 2.0 authentication, browser-based credential flows, and the Claude Code installation command. - Airbyte's developers MCP overview at
docs.airbyte.com/developers/mcp-serversdescribes the primary MCP use case for AI agents with Airbyte connectors. - Airbyte's main repository
github.com/airbytehq/airbyteis the authoritative source for the Airbyte platform. - Claude Code's MCP documentation describes the
--transport httpinstallation pattern used above.
Source citations
Add this badge to your README
How it compares
Airbyte MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Airbyte MCP Server for Claude Connect Claude to your data through Airbyte's 50+ agent connectors — query CRMs, billing systems, project management tools, communication platforms, and more — with the official Airbyte remote MCP server for AI agents. Open dossier | Baselight MCP Server for Claude Official Baselight remote MCP server for searching and querying a catalog of 70,000+ public datasets from Claude via OAuth or x-api-key authentication. Open dossier | Cirra AI Salesforce Admin MCP Server for Claude Commercial Cirra AI MCP server that connects Claude and other MCP clients to Salesforce orgs via OAuth for metadata, permissions, flows, Apex, and SOQL administration through natural language. Open dossier | Customer.io MCP Server for Claude Manage Customer.io from Claude — create segments, inspect customer profiles, send broadcasts and campaigns, work with journeys, and access the full Journeys UI and CDP Data Pipelines APIs — with the official Customer.io remote MCP server. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | Airbyte | Baselight | Cirra AI | Customer.io |
| Added | 2026-06-18 | 2026-06-14 | 2026-06-14 | 2026-06-18 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓The server is hosted and managed by Airbyte — credentials for connected services are entered via browser OAuth flows or secure forms, never in the AI chat. Depending on the connector, the MCP can create and update records (not just read) — review Claude's proposed actions before confirming writes. Access is scoped by the permissions granted during OAuth; use least-privilege scopes for each connected service. | ✓Query tools may return large result sets; scope filters to avoid excessive data transfer. Some datasets are community-contributed; validate schema and quality before production use. OAuth tokens and API keys grant persistent catalog access until revoked. Do not run unreviewed SQL-like queries against sensitive production mirrors without safeguards. | ✓Cirra runs as the connected Salesforce user; destructive metadata changes follow your org permissions. Review flow, Apex, and permission-set edits before approving automated tool calls in production orgs. OAuth tokens grant persistent org access until revoked in Salesforce or Cirra. Prefer sandbox connections while testing new admin automation workflows. | ✓The server exposes three tool categories: read (GET), write (POST/PUT/PATCH), and delete (DELETE) — approve each independently. By default, the MCP server cannot delete customer profiles or modify live active campaigns — only create new items — reducing accidental audience impact. Write and delete tools can trigger real sends and modify live data; review Claude's proposed actions before confirming. |
| Privacy notes | ✓Data retrieved from connected services (contacts, deals, invoices, messages) is surfaced in Claude's context. All credential flows are browser-based and never transmitted through the AI chat interface. | ✓Search terms and query filters are sent to Baselight and may appear in usage logs. Dataset rows returned through MCP may include PII or licensed third-party content subject to dataset terms. Avoid pasting raw dataset excerpts containing personal data into public channels. | ✓Org metadata, record samples, and SOQL results are processed by Cirra under its own data-handling terms. Cirra states it does not store Salesforce data on its servers and encrypts data in transit. Do not paste OAuth codes, refresh tokens, or session cookies into public issues or shared chat logs. | ✓Customer profiles, segment definitions, journey configurations, and campaign data from your Customer.io workspace are surfaced in Claude's context. Customer.io's MCP server is authenticated via OAuth — no API keys are stored in your MCP config. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.