# Airbyte: MCP server status, API access gate and what it does > Open-source/cloud ELT platform with 600+ connectors moving data from SaaS tools and databases into... Official MCP, Free to start. Checked 2026-09-07. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* *Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.* --- [Directory](../index.md) / [RevOps Infra](../categories/revops-infra.md) / Airbyte # Airbyte [Official MCP](../mcp/official.md) [Free to start](../gates/free.md) [RevOps Infra](../categories/revops-infra.md) RESEARCHED Checked 2026-09-07 CLI: airbyte-config (community) > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1. Vendor: [airbyte.com](https://airbyte.com) · entry id 06-airbyte · source 06-revops-infra.md line 334 **What it does** Open-source/cloud ELT platform with 600+ connectors moving data from SaaS tools and databases into warehouses; increasingly positions itself as a context layer for AI agents via a hosted Context Store. **AI features, separated from automation with an AI label on it** A real, substantive "Agents" product line (app.airbyte.ai) using a Connect-Ask-Act model that lets agents query/act on connected data - not just a copilot bolt-on. Whether the core Connector Builder itself has natural-language-assisted connector generation was not confirmed either way and is left as unknown rather than guessed. **RevOps role** Upstream data-integration layer - gets GTM tool data (and 600+ other sources) into the warehouse, and now also positions as the retrieval/action layer for AI agents to reach across GTM systems directly. **MCP server** - **Status bucket**: Official MCP - **Auth**: Two-layer OAuth 2.0 - OAuth into the Airbyte account/org for the MCP server itself, plus separate OAuth or API-key auth per connected third-party service (Salesforce, HubSpot, GitHub, Stripe, etc.), entered in-browser, never in agent chat. Hosted endpoint: https://mcp.airbyte.ai/mcp. - **Parsed URLs**: 2 found in the mcp_url field - **Endpoint probe**: docs page, not an endpoint - **Docs URL**: [https://docs.airbyte.com/ai-agents/interfaces/mcp](https://docs.airbyte.com/ai-agents/interfaces/mcp) - **Probed**: 2026-09-04, HTTP 200 The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-09-07. On 2026-09-04 the recorded URL served a documentation page, not an MCP endpoint. That is where to read about the server, not where to connect to it. An agent needs the second. mcp_status, verbatim from the file: official mcp_url, verbatim from the file: https://mcp.airbyte.ai/mcp ; https://docs.airbyte.com/ai-agents/interfaces/mcp - [https://mcp.airbyte.ai/mcp](https://mcp.airbyte.ai/mcp) - [https://docs.airbyte.com/ai-agents/interfaces/mcp](https://docs.airbyte.com/ai-agents/interfaces/mcp) **What this server exposes** - **Tools named**: 4 - **Strongest evidence**: in the vendor docs - **Harvested**: 2026-09-27 - **Catalogue shape**: a fixed catalogue the vendor publishes A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything. - **inspect_connector** reports a connector's metadata, its docs_skill_id, and Context Store readiness evidence: in the vendor docs · calling it reads - **list_skills** browse available skills evidence: in the vendor docs · calling it reads - **read_skill_docs** returns a connector's usage docs, an outline of entities and actions, or a specific section when the agent passes one evidence: in the vendor docs · calling it reads - **search_skills** search through available skills evidence: in the vendor docs · calling it reads 141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the [tools index](../tools-index.md). **Command line** This is a third party's CLI. It was published by somebody other than the vendor, so it is that author's surface for the vendor's API and not the vendor's published surface. The two must not be read as the same thing. - **Binary**: airbyte-config - **Status**: community CLI, third party - **Strongest evidence**: npm - **Harvested**: 2026-09-27 Install, as the source shows it: ``` npm install -g airbyte-config-cli ``` quoted from [https://www.npmjs.com/package/airbyte-config-cli](https://www.npmjs.com/package/airbyte-config-cli) on 2026-09-27, via npm, a third party source Packages seen, with the version on 2026-09-27: - [npm: airbyte-config-cli 1.0.0, third party](https://www.npmjs.com/package/airbyte-config-cli) A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27. **Access gate** - **Gate bucket**: Free to start - **Can a solo operator reach it**: Yes, without talking to anyone api_gate, verbatim from the file: free - Core (self-managed, open source) is always free; Cloud has a genuine self-serve $0/mo tier (1,000 Agent Operations/month); cheapest paid Standard tier starts at $10/mo. **API documentation** No documentation URL recorded. 727 of 1252 entries are in the same position. Blank is legal and it is published as blank. **GitHub health** Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build. The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale. **On GitHub** No GitHub organisation could be tied to airbyte.com with evidence on 2026-09-08. Recorded by the harvest: github candidates were seen but none passed the evidence rules. 5 candidate accounts seen and rejected by the evidence rules: airbyte, airbytehq, AirbyteTeam, airbytez, Airbyte-Solutions-Team. A name match alone is never accepted; the account has to point at the vendor domain. **Jobs it can do** - [Sync records between systems](../jobs/sync-records-between-systems.md) A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records. Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total. **Sources** - [https://airbyte.com/](https://airbyte.com/) - [https://airbyte.com/pricing](https://airbyte.com/pricing) - [https://docs.airbyte.com/ai-agents/interfaces/mcp](https://docs.airbyte.com/ai-agents/interfaces/mcp) - [https://mcp.airbyte.ai/mcp](https://mcp.airbyte.ai/mcp) 4 source URLs. Raw sources field, verbatim: https://airbyte.com/, https://airbyte.com/pricing, https://docs.airbyte.com/ai-agents/interfaces/mcp, https://mcp.airbyte.ai/mcp **Notes, verbatim from the file** One of the more clearly "official and productized" MCP implementations in this file - hosted, documented, and multi-client (Claude, ChatGPT, Cursor, VS Code, Codex). 2026-09-07: Official MCP registry entry io.github.airbytehq/agents lists remote https://mcp.airbyte.ai/mcp; that URL returned 401 to an MCP initialize. airbytehq is Airbyte's own GitHub org (https://mcp.airbyte.ai/mcp). **Provenance** - **Entry id**: 06-airbyte - **Source file**: 06-revops-infra.md - **Source line**: 334 - **Tier**: RESEARCHED - **last_checked**: 2026-09-07 - **Data baked**: 2026-09-27 Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).