airbyte-mcp

airbyte-mcp

Enables interaction with an Airbyte instance through natural language, supporting workspaces, sources, destinations, connections, jobs, logs, tags, streams, and connector definitions.

Category
Visit Server

README

Airbyte MCP Server (airbyte-mcp)

MCP server for the Airbyte Public API. Built with the official MCP Python SDK (FastMCP).

Lets any MCP-compatible client (Cursor, Claude Desktop, Claude Code, MCP Inspector, etc.) interact with your Airbyte instance through natural language.

Features

  • 30 tools covering workspaces, sources, destinations, connections, jobs, job logs, tags, streams, and connector definitions
  • Read and write operations for core resources (create, update, delete)
  • Job diagnostics via the internal Configuration API (self-managed): detailed failure reasons, per-stream stats, and structured logs
  • Automatic token exchange with in-memory caching and transparent 401 retry
  • Markdown and JSON response formats on summary tools; JSON-only for log tools
  • Pagination support (limit/offset) on all list tools
  • Two transport modes: stdio (local) and streamable HTTP (remote)
  • Works with self-managed Airbyte (abctl) and Airbyte Cloud

Available Tools

Tool Description
Health
airbyte_health_check Ping the Airbyte API
Workspaces
airbyte_list_workspaces List workspaces with pagination
airbyte_get_workspace Get workspace details by ID
Sources
airbyte_list_sources List source connectors (filter by workspace)
airbyte_get_source Get source details by ID
airbyte_create_source Create a new source connector
airbyte_update_source Update an existing source
Destinations
airbyte_list_destinations List destination connectors (filter by workspace)
airbyte_get_destination Get destination details by ID
airbyte_create_destination Create a new destination connector
airbyte_update_destination Update an existing destination
Connections
airbyte_list_connections List connections / pipelines (filter by workspace)
airbyte_get_connection Get connection details including stream config
airbyte_create_connection Create a new connection (pipeline)
airbyte_update_connection Update an existing connection
Jobs
airbyte_list_jobs List jobs (filter by connection, type, status, dates)
airbyte_get_job Get job details (status, duration, bytes/rows synced)
airbyte_trigger_sync Trigger a sync or reset job
airbyte_cancel_job Cancel a running job
Job Logs (Internal API)
airbyte_get_job_details Per-attempt stats, failure reasons, and stacktraces
airbyte_get_job_logs Structured log entries for all attempts
airbyte_get_attempt_logs Structured log entries for a specific attempt
Streams
airbyte_get_stream_properties Get stream properties for a source/destination pair
Tags
airbyte_list_tags List tags
airbyte_create_tag Create a tag
airbyte_update_tag Update a tag
airbyte_delete_tag Delete a tag
Connector Definitions
airbyte_list_source_definitions List source connector definitions
airbyte_get_source_definition Get a source connector definition
airbyte_list_destination_definitions List destination connector definitions
airbyte_get_destination_definition Get a destination connector definition

See docs/endpoints.md for the full Airbyte API endpoint checklist.

Prerequisites

Quickstart

1. Clone and install

git clone https://github.com/trustxai/airbyte-mcp.git
cd airbyte-mcp
uv sync

2. Configure credentials

cp .env.example .env

For self-managed (abctl), retrieve credentials:

abctl local credentials

Edit .env with your client-id and client-secret. See docs/authentication.md for details.

3. Run the server

stdio (Cursor / Claude Desktop / Docker)

uv run airbyte-mcp

Streamable HTTP (remote / MCP Inspector)

uv run airbyte-mcp-http
# Listening on http://127.0.0.1:8080/mcp

Client Configuration

Every MCP client (Cursor, Claude Desktop, etc.) can run the server in one of two ways:

  • uv — quickest to set up, but requires uv installed locally.
  • Docker — no Python / uv required on the host; everything runs in a container. Build the image once and every client config reuses it.

Host networking note: if Airbyte is running on your host machine (e.g. via abctl), inside the Docker container localhost does not point to your host. Use http://host.docker.internal:8000/api/public/v1 on macOS/Windows, or add --network=host to the docker run args on Linux.

Build the Docker image (one-time)

docker build -t airbyte-mcp:latest .

Cursor

Add to .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (global):

Option A — uv

{
  "mcpServers": {
    "airbyte": {
      "command": "uv",
      "args": ["--directory", "/path/to/airbyte-mcp", "run", "airbyte-mcp"],
      "env": {
        "AIRBYTE_API_URL": "http://localhost:8000/api/public/v1",
        "AIRBYTE_CLIENT_ID": "<your-client-id>",
        "AIRBYTE_CLIENT_SECRET": "<your-client-secret>"
      }
    }
  }
}

Option B — Docker

{
  "mcpServers": {
    "airbyte": {
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "--name", "airbyte-mcp",
        "-e", "AIRBYTE_API_URL",
        "-e", "AIRBYTE_CLIENT_ID",
        "-e", "AIRBYTE_CLIENT_SECRET",
        "airbyte-mcp:latest"
      ],
      "env": {
        "AIRBYTE_API_URL": "http://host.docker.internal:8000/api/public/v1",
        "AIRBYTE_CLIENT_ID": "<your-client-id>",
        "AIRBYTE_CLIENT_SECRET": "<your-client-secret>"
      }
    }
  }
}

Claude Desktop

Add to claude_desktop_config.json:

Option A — uv

{
  "mcpServers": {
    "airbyte": {
      "command": "uv",
      "args": ["--directory", "/path/to/airbyte-mcp", "run", "airbyte-mcp"],
      "env": {
        "AIRBYTE_API_URL": "http://localhost:8000/api/public/v1",
        "AIRBYTE_CLIENT_ID": "<your-client-id>",
        "AIRBYTE_CLIENT_SECRET": "<your-client-secret>"
      }
    }
  }
}

Option B — Docker

{
  "mcpServers": {
    "airbyte": {
      "command": "docker",
      "args": [
        "run", "--rm", "-i",
        "--name", "airbyte-mcp",
        "-e", "AIRBYTE_API_URL",
        "-e", "AIRBYTE_CLIENT_ID",
        "-e", "AIRBYTE_CLIENT_SECRET",
        "airbyte-mcp:latest"
      ],
      "env": {
        "AIRBYTE_API_URL": "http://host.docker.internal:8000/api/public/v1",
        "AIRBYTE_CLIENT_ID": "<your-client-id>",
        "AIRBYTE_CLIENT_SECRET": "<your-client-secret>"
      }
    }
  }
}

Claude Code (HTTP)

Option A — uv

uv run airbyte-mcp-http &
claude mcp add --transport http airbyte http://127.0.0.1:8080/mcp

Option B — Docker

docker build -f Dockerfile.http -t airbyte-mcp-http:latest .
docker run -d --rm --name airbyte-mcp-http \
  -p 8080:8080 \
  -e AIRBYTE_API_URL=http://host.docker.internal:8000/api/public/v1 \
  -e AIRBYTE_CLIENT_ID=<your-client-id> \
  -e AIRBYTE_CLIENT_SECRET=<your-client-secret> \
  airbyte-mcp-http:latest
claude mcp add --transport http airbyte http://127.0.0.1:8080/mcp

MCP Inspector

# Start the server in HTTP mode (uv or docker — either works)
uv run airbyte-mcp-http
#   or: docker run --rm -p 8080:8080 --env-file .env airbyte-mcp-http:latest

# In another terminal
npx @modelcontextprotocol/inspector
# Then connect to http://127.0.0.1:8080/mcp in the inspector UI

Running Manually (without a client)

If you just want to exercise the server from the CLI:

# stdio (uv)
uv run airbyte-mcp

# stdio (Docker)
docker run --rm -i --env-file .env airbyte-mcp:latest

# HTTP (uv)
uv run airbyte-mcp-http

# HTTP (Docker)
docker run --rm -p 8080:8080 --env-file .env airbyte-mcp-http:latest

Environment Variables

Variable Required Default Description
AIRBYTE_API_URL No http://localhost:8000/api/public/v1 Airbyte API base URL
AIRBYTE_CLIENT_ID Yes* Application client ID
AIRBYTE_CLIENT_SECRET Yes* Application client secret
AIRBYTE_ACCESS_TOKEN No Pre-fetched token (skips exchange)
HTTP_HOST No 127.0.0.1 HTTP transport bind address
HTTP_PORT No 8080 HTTP transport port

*Not required if AIRBYTE_ACCESS_TOKEN is provided.

Documentation

Contributing

Contributions are welcome! See docs/CONTRIBUTING.md to get started.

License

Apache-2.0 — see LICENSE for details.

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured