Skip to main content

airbyte-ops-mcp

MCP and API interfaces that let the agents do the admin work.

How to Contribute

  • CONTRIBUTING.md — contributor setup, local testing, and development workflows.
  • AGENTS.md — agent-specific operating guidance.

Documentation

Ops Repo Subprojects

Subproject Root dir Description Release notes
airbyte-internal-ops . MCP server and airbyte-ops CLI for Airbyte admin operations. v0 releases
airbyte-cloud-cli airbyte-cloud-cli/ Standalone CLI for Airbyte Cloud operations. v0 releases
Sentry infrastructure infra/sentry/ Pulumi project for connector error monitoring configuration. N/A
Agent message bus infrastructure infra/agent-message-bus/ Pulumi and Cloud Run app for internal agent messaging. N/A

GitHub's Releases UI does not group releases by package automatically. Use a tag filter with the exact tag namespace and at least major-version precision, such as tag:v0 or tag:airbyte-cloud-cli/v0, or use the links above.

Installing Ops MCP in your Client

This config example will help you add the MCP server to your client:

{
  "mcpServers": {
    "airbyte-ops-mcp": {
      "type": "stdio",
      "command": "uv",
      "args": [
        "run",
        "--project=/Users/aj.steers/repos/airbyte-ops-mcp/",
        "airbyte-ops-mcp"
      ],
      "env": {
        "AIRBYTE_MCP_ENV_FILE": "/Users/{user-id}/.mcp/airbyte_mcp.env"
      }
    },
    "airbyte-coral-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "--python=3.11",
        "--from=airbyte@latest",
        "airbyte-mcp"
      ],
      "env": {
        "AIRBYTE_MCP_ENV_FILE": "/Users/{user-id}/.mcp/airbyte_mcp.env"
      }
    }
  }
}

Connecting to the hosted MCP servers

Use interactive OAuth by default. The client opens a browser to complete the login flow; do not add a headers block:

{
  "mcpServers": {
    "airbyte-ops-mcp": {
      "type": "http",
      "url": "https://mcp.internal.airbyte.ai/ops-mcp"
    },
    "airbyte-cloud-mcp": {
      "type": "http",
      "url": "https://mcp.internal.airbyte.ai/cloud-mcp"
    }
  }
}

MCP client configuration syntax is client-specific. The block above uses the common type: "http" and url spelling. For Goose, use type: "streamable_http" and uri instead:

{
  "mcpServers": {
    "airbyte-ops-mcp": {
      "type": "streamable_http",
      "uri": "https://mcp.internal.airbyte.ai/ops-mcp"
    },
    "airbyte-cloud-mcp": {
      "type": "streamable_http",
      "uri": "https://mcp.internal.airbyte.ai/cloud-mcp"
    }
  }
}

Use the hosted endpoint path exactly as shown; do not append /mcp.

For a headless client, use the two credential headers instead:

{
  "mcpServers": {
    "airbyte-ops-mcp": {
      "type": "http",
      "url": "https://mcp.internal.airbyte.ai/ops-mcp",
      "headers": {
        "Client-Id": "${AIRBYTE_CLOUD_CLIENT_ID}",
        "Client-Secret": "${AIRBYTE_CLOUD_CLIENT_SECRET}"
      }
    },
    "airbyte-cloud-mcp": {
      "type": "http",
      "url": "https://mcp.internal.airbyte.ai/cloud-mcp",
      "headers": {
        "Client-Id": "${AIRBYTE_CLOUD_CLIENT_ID}",
        "Client-Secret": "${AIRBYTE_CLOUD_CLIENT_SECRET}"
      }
    }
  }
}

Whether ${ENV} references are expanded inside a headers block depends on the client; if not, provide the credential values through that client's supported secret configuration.

The credential-header form is enabled on airbyte-ops-mcp. It is not yet enabled on airbyte-cloud-mcp; sending those headers there currently triggers the client's OAuth fallback, which opens a browser consent page at https://mcp.internal.airbyte.ai/cloud-mcp/consent and can leave the client waiting instead of showing the underlying 401. The PyAirbyte server must first receive the corresponding support. See docs/authentication.md for the full authentication model and security guidance.

Your .env file should include the following values:

# Creds for Airbyte Cloud OAuth
AIRBYTE_CLOUD_CLIENT_ID="..."
AIRBYTE_CLOUD_CLIENT_SECRET="..."

# Required for elevated admin operations
AIRBYTE_INTERNAL_ADMIN_FLAG=airbyte.io
AIRBYTE_INTERNAL_ADMIN_USER={my-id}@airbyte.io

# Workspace ID for Testing
AIRBYTE_CLOUD_TEST_WORKSPACE_ID="..."

Onboarding

If this is your first time working with Airbyte's connector tooling, see ONBOARDING.md for instructions on setting up required credentials like GCP_GSM_CREDENTIALS.

Connector Registry

For an overview of the connector registry architecture, operations, and CLI commands, see docs/connector-registry.md.

For release-block marker operations that prevent republishing known-bad connector code after a yank, see docs/release-blocks.md.

For details on known, intentional differences between the new Registry 2.0 generation pipeline and the legacy pipeline, see Connector Registry 2.0 Migration Changes in CONTRIBUTING.md.

Getting Started

Once configured, use the test_my_tools prompt by typing "/test" into your agent and selecting the auto-complete option for the test_my_tools prompt.

This prompt will step through all the tools, demoing their capabilities.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

airbyte_internal_ops-0.100.0.tar.gz (1.7 MB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

airbyte_internal_ops-0.100.0-py3-none-any.whl (726.9 kB view details)

Uploaded Python 3

File details

Details for the file airbyte_internal_ops-0.100.0.tar.gz.

File metadata

  • Download URL: airbyte_internal_ops-0.100.0.tar.gz
  • Upload date:
  • Size: 1.7 MB
  • Tags: Source
  • Uploaded using Trusted Publishing? Yes
  • Uploaded via: twine/7.0.0 CPython/3.13.14

File hashes

Hashes for airbyte_internal_ops-0.100.0.tar.gz
Algorithm Hash digest
SHA256 220f16822a35a1ddf553e68618f593b1f89cd693000b6c8d5931e36a9e60d4ce
MD5 621af05b391fea918abced578459a017
BLAKE2b-256 7efdc8cf3a85ca28bfd6470ffb1028c7829c5c2a104fc2c5b5d6b01308be742d

See more details on using hashes here.

Provenance

The following attestation bundles were made for airbyte_internal_ops-0.100.0.tar.gz:

Publisher: publish.yml on airbytehq/airbyte-ops-mcp

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file airbyte_internal_ops-0.100.0-py3-none-any.whl.

File metadata

File hashes

Hashes for airbyte_internal_ops-0.100.0-py3-none-any.whl
Algorithm Hash digest
SHA256 1b05a611e7445e599e6f872fedecab5a8e7e317f2a73c41c72221807bb60edf5
MD5 7390c761ed933ab1fac9449399f7ebc9
BLAKE2b-256 3884fde3aed43dc962468fb930608e1f2b0b13d9afa917c1d4c3984004b1da8b

See more details on using hashes here.

Provenance

The following attestation bundles were made for airbyte_internal_ops-0.100.0-py3-none-any.whl:

Publisher: publish.yml on airbytehq/airbyte-ops-mcp

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Release history Release notifications | RSS feed

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page