Metadata-Version: 2.4
Name: airbyte-internal-ops
Version: 0.63.0
Summary: MCP and API interfaces that let the agents do the admin work
Author-email: Aaron Steers <aj@airbyte.io>
Keywords: admin,airbyte,api,mcp
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Requires-Python: <3.13,>=3.11
Requires-Dist: airbyte-cdk<8.0,>=7.3.9
Requires-Dist: airbyte-connector-models<=0.1.4,>=0.1.3
Requires-Dist: airbyte-protocol-models-pdv2>=0.13.0
Requires-Dist: airbyte<1.0.0,>=0.45.0
Requires-Dist: asyncclick<9.0,>=8.1.7
Requires-Dist: asyncer<1.0,>=0.0.4
Requires-Dist: click<9.0,>=8.1.3
Requires-Dist: cloud-sql-python-connector[pg8000]<2.0,>=1.7.0
Requires-Dist: cyclopts<5.0,>=4.0.0
Requires-Dist: docker<7.0,>=6.0
Requires-Dist: dpath<3.0,>=2.1.5
Requires-Dist: fastmcp-extensions<1.0.0,>=0.4.0
Requires-Dist: fastmcp<4.0,>=3.0
Requires-Dist: fsspec>=2024.0.0
Requires-Dist: gcsfs>=2024.0.0
Requires-Dist: gitpython<4.0,>=3.1.29
Requires-Dist: google-cloud-logging<4.0,>=3.9.0
Requires-Dist: google-cloud-secret-manager<3.0,>=2.18.0
Requires-Dist: google-cloud-storage<3.0,>=2.8.0
Requires-Dist: jinja2<4.0,>=3.1.2
Requires-Dist: markdown-it-py<3.0,>=2.2.0
Requires-Dist: packaging>=23.0
Requires-Dist: pydantic>=2.0.0
Requires-Dist: pydash<8.0,>=6.0.2
Requires-Dist: pygithub<3.0,>=2.0
Requires-Dist: python-dotenv<2.0,>=1.0.0
Requires-Dist: pyyaml<7.0,>=6.0.0
Requires-Dist: requests<3.0,>=2.31.0
Requires-Dist: rich<14.0,>=13.0.0
Requires-Dist: ruamel-yaml>=0.18
Requires-Dist: s3fs>=2024.0.0
Requires-Dist: semver<4.0,>=3.0.1
Requires-Dist: sentry-sdk>=2.50.0
Requires-Dist: simpleeval<1.0,>=0.9.13
Requires-Dist: slack-sdk<4.0,>=3.36.0
Requires-Dist: sqlalchemy<3.0,>=2.0.0
Requires-Dist: toml<1.0,>=0.10.2
Description-Content-Type: text/markdown

# airbyte-ops-mcp

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

## How to Contribute

- [CONTRIBUTING.md](./CONTRIBUTING.md) — contributor setup, local testing, and development workflows.
- [AGENTS.md](./AGENTS.md) — agent-specific operating guidance.

## Documentation

- [CLI Reference](https://airbytehq.github.io/airbyte-ops-mcp/airbyte_ops_mcp/cli.html) — `airbyte-ops` command-line interface
- [MCP Tools Reference](https://airbytehq.github.io/airbyte-ops-mcp/airbyte_ops_mcp/mcp.html) — Model Context Protocol server tools

## Ops Repo Subprojects

| Subproject | Root dir | Description | Release notes |
| --- | --- | --- | --- |
| `airbyte-internal-ops` | `.` | MCP server and `airbyte-ops` CLI for Airbyte admin operations. | [v0 releases](https://github.com/airbytehq/airbyte-ops-mcp/releases?q=tag:v0) |
| `airbyte-cloud-cli` | `airbyte-cloud-cli/` | Standalone CLI for Airbyte Cloud operations. | [v0 releases](https://github.com/airbytehq/airbyte-ops-mcp/releases?q=tag:airbyte-cloud-cli/v0) |
| 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:

```json
{
  "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"
      }
    }
  }
}
```

Your `.env` file should include the following values:

```ini
# 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](./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](./docs/connector-registry.md).

For release-block marker operations that prevent republishing known-bad connector code after a yank, see [docs/release-blocks.md](./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](./CONTRIBUTING.md#connector-registry-20-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.
