airbyte-oss-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIRBYTE_URL | No | Base URL of your Airbyte instance. Default is http://localhost:8000 | http://localhost:8000 |
| AIRBYTE_ENVS | No | JSON map of named envs for multi-instance setups | |
| AIRBYTE_API_TOKEN | No | Bearer token if public API auth is enabled | |
| AIRBYTE_READ_ONLY | No | When false, exposes cancel_job and trigger_sync. Default is true | true |
| AIRBYTE_DEFAULT_ENV | No | Default key when AIRBYTE_ENVS has multiple entries |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_instance_statusA | Global Airbyte health snapshot. Start here for monitoring workflows. Returns health text, workspace count, connection counts by status, and counts of running / pending / failed sync jobs (recent sample). |
| list_connectionsA | List Airbyte connections with schedule and status metadata. Filters:
|
| get_connectionA | Get one connection by exact name or connectionId UUID. Returns connection metadata with stream summaries (name, namespace, prefix, syncMode) and the three most recent sync jobs. |
| list_jobsA | List recent sync jobs, newest first. Returns jobId, status, startTime, duration, bytesSynced, rowsSynced, connectionId, and connectionName. Filters:
|
| get_active_syncsB | List all currently running sync jobs with connection names. Best tool to answer 'what is blocking the Airbyte worker pool?' or 'why is this sync taking so long?' |
| find_duplicate_destination_tablesA | Detect multiple active connections writing the same BigQuery project.dataset.table. Best-effort audit using connection stream config and destination settings. Skips non-BigQuery destinations and inactive connections. |
| get_jobC | Get public job metadata for a sync job id. |
| get_job_detailsA | Get job plus attempt stats via the internal OSS jobs API. Includes per-attempt totalStats and failure summaries (without raw logs). |
| get_job_failure_summaryA | Consolidated failure diagnosis for a sync job (prefer over raw logs). Returns root-cause failure messages from the latest failed attempt, plus job/connection context and row/byte stats when available. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Tools are mostly distinct, but there is overlap among get_job, get_job_details, and get_job_failure_summary, which could confuse an agent about which to use. Additionally, get_active_syncs overlaps with list_jobs filtered by status. Descriptions help but ambiguity remains.
Most tools follow a 'get_' or 'list_' pattern, but get_active_syncs uses 'get' for a list operation and find_duplicate_destination_tables uses 'find_', which is a minor deviation from the prevailing pattern.
With 9 tools, the server is well-scoped for its intended purpose of monitoring and auditing Airbyte instances. Each tool has a clear role and no unnecessary redundancy.
The tool set is heavily biased towards read and monitoring operations, missing essential CRUD capabilities like creating or updating connections and triggering syncs. This leaves significant gaps for a full Airbyte management server.