The interesting design choice is that read_skill_docs exists at all. Rather than exposing every connector's schema as tools and paying for it in context on every turn, Airbyte gives the agent a way to look things up when it needs them — the outline first, then one section. That keeps a large integration surface affordable. The two-layer auth is the part to plan for: connecting to Airbyte does not connect you to Salesforce, and each connector wants its own trip through a consent screen.
Airbyte's fully managed agent endpoint — nothing to install and no pipeline to deploy. The four tools it exposes are about discovery: what connectors you have, what each one can do, and where to find the usage docs the agent needs before touching records.
- inspect_connector — a connector's metadata, its docs skill and whether the Context Store is ready
- read_skill_docs — the usage documentation for a connector, either as an outline or one named section
- list_skills and search_skills — browse or search what the agent can reach
- Through those connectors: list, search, read, create and update records across the CRM, billing, messaging and project tools you have connected, with field trimming to keep responses small
Two layers of authorisation: sign in to Airbyte for the MCP connection itself, then authorise each third-party connector separately in the browser. MCP is on every Airbyte Agents plan including Free; usage bills as agent operations.
Paste a URL, then sign in — add the endpoint to your client and sign in to the vendor