This release is a pre-release and may not be stable for production use.
airbyte-ops-mcp
MCP and API interfaces that let the agents do the admin work.
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"
}
}
}
}
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="..."
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.
Metadata
Release files for airbyte-internal-ops 0.1.2.post2.dev20080805740
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| airbyte_internal_ops-0.1.2.post2.dev20080805740.tar.gz | 1.2 MB | With provenance | Details for airbyte_internal_ops-0.1.2.post2.dev20080805740.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| airbyte_internal_ops-0.1.2.post2.dev20080805740-py3-none-any.whl | Python 3 | none | any | Details for airbyte_internal_ops-0.1.2.post2.dev20080805740-py3-none-any.whl |
Total release size: 2.3 MB
Release files / airbyte_internal_ops-0.1.2.post2.dev20080805740.tar.gz
| Download URL | airbyte_internal_ops-0.1.2.post2.dev20080805740.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aeee0c833a60abaffd3f75a8f08d59e790715340f06fd12386ce51d81708c36e
|
|
BLAKE2b-256 checksum How to use checksums |
c505cb4f3ba1a85144cbb733c4ad50af14959db01eef0d50ee7803ac6195995a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 9, 2025.
Transparency logRelease files / airbyte_internal_ops-0.1.2.post2.dev20080805740-py3-none-any.whl
| Download URL | airbyte_internal_ops-0.1.2.post2.dev20080805740-py3-none-any.whl |
|---|---|
| Size | 1.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e501c15e6f1d0156ddcc7786ebe557253063d8d8ba8d58cd1c3e45770ea3dbb6
|
|
BLAKE2b-256 checksum How to use checksums |
df8fbf3fde3154ea9a4f9a8feeee15f3483399de9bc8bca9a2f7c2be8f94c986
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 9, 2025.
Transparency logSecurity for airbyte-internal-ops 0.1.2.post2.dev20080805740
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for airbyte_internal_ops-0.1.2.post2.dev20080805740.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 9, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.