Problem
The Airbyte Replication MCP server is documented mainly for local stdio clients (Claude Desktop, Cursor, etc.). Many remote MCP platforms require a public HTTPS endpoint using Streamable HTTP — stdio-based servers cannot be used directly.
The repo already includes hosted HTTP support (airbyte-mcp-http, Dockerfile.mcp, Streamable HTTP on port 8080), but this path is not well documented. Users who want to connect from a remote MCP client have no clear guide from “local stdio MCP” to “deployed HTTPS MCP.”
There is also no official Airbyte-hosted public MCP endpoint in this repository. Self-hosting with TLS termination at a reverse proxy is the expected model.
Goal
Make it straightforward to deploy the Replication MCP server over HTTPS and connect it to remote MCP clients (e.g. Dust, MCP Inspector over HTTP, custom integrations).
Problem
The Airbyte Replication MCP server is documented mainly for local stdio clients (Claude Desktop, Cursor, etc.). Many remote MCP platforms require a public HTTPS endpoint using Streamable HTTP — stdio-based servers cannot be used directly.
The repo already includes hosted HTTP support (airbyte-mcp-http, Dockerfile.mcp, Streamable HTTP on port 8080), but this path is not well documented. Users who want to connect from a remote MCP client have no clear guide from “local stdio MCP” to “deployed HTTPS MCP.”
There is also no official Airbyte-hosted public MCP endpoint in this repository. Self-hosting with TLS termination at a reverse proxy is the expected model.
Goal
Make it straightforward to deploy the Replication MCP server over HTTPS and connect it to remote MCP clients (e.g. Dust, MCP Inspector over HTTP, custom integrations).