Included as an agent-facing connector layer that gives MCP clients typed, credentialed actions over third-party business systems, while Airbyte separately offers documentation search and experimental replication-control MCP servers.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Agent MCP connectors and skills; external-system entities such as contacts, companies, deals, tickets, messages, customers, payments, and files; Airbyte connector credentials; plus separate replication sources, destinations, configurations, and sync jobs.
Through Agent MCP, inspect connector metadata and skill documentation, then list, get, search, or read the entity types supported by each authenticated connector. Knowledge MCP searches Airbyte documentation and code; Replication MCP can list connectors and validate configurations.
Agent MCP may expose connector-specific create and update actions, including operations in CRM, messaging, payment, and other connected services. The experimental Replication MCP can run syncs; supported mutations are defined by the chosen connector or replication tool, not by a universal Airbyte action set.
Agent MCP first authorizes the MCP client to Airbyte with OAuth 2.0 scoped to the Airbyte account or organization, then separately authenticates every third-party connector through its OAuth or API-key flow. Connector credentials are stored server-side and are not exposed to the agent.
Airbyte centralizes connector credentials on its server and exposes typed actions rather than raw secrets. The same connector permissions apply across web, MCP, SDK, and API interfaces; the MCP client may add its own workspace app and action controls.
Connector entity and action coverage varies by service. Agent MCP requires an Airbyte Agents account and credentials for each connector. The Knowledge MCP answers product and developer questions rather than accessing customer business data, while Replication MCP is experimental and runs locally through PyAirbyte. Airbyte documents a US-only limitation for ChatGPT Agent Engine integration.
First-party access
Agent access
Support: Official MCP server
Read scope: Use Agent MCP only for the list, get, search, and read actions published by each authenticated connector; use Knowledge MCP for Airbyte documentation and specifications; use Replication MCP to inspect available connectors and validate sync configurations.
Write scope: Connector skills can create or update supported third-party entities and perform service-specific actions; Replication MCP can start sync work. No write should be generalized from one connector to another.
Authentication: OAuth 2.0 authenticates the client to the hosted Agent MCP, followed by a separate browser credential flow for each connector using that service's OAuth or API key.
Approval boundary: Present the selected connector, external account, entity, and exact action before any create, update, message, payment, or sync operation. Connector authorization and a valid tool call are not substitutes for approval of the business effect.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Airbyte ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party developer documentation or platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party MCP documentation or product announcement recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party webhook, event, SDK, embedded-app, or extension documentation.
Inventory source: structurally normalized; content was not individually reopened in this pass.
Airbyte explicitly describes Data Activation as Reverse ETL that moves warehouse insights to operational tools. Database connectors alone are not counted as SQL/query access to Airbyte itself.
Targeted first-party access review
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
