Cyborg MCP Servers
Model Context Protocol (MCP) servers for the Cyborg ecosystem, packaged as a single installable distribution with per-server extras. Usable standalone with Claude Code, Cursor, and other MCP clients, and programmatically in-process by other Python hosts.
Servers
| Server | Console script | Extra | Docs |
|---|---|---|---|
| argo-k8s — Argo Workflows / Kubernetes / Argo CD / Peribolos troubleshooting | argo-k8s-mcp |
[argo] |
docs/argo-k8s.md |
| orgdata — organizational data queries (employees, teams, orgs, Jira ownership) | orgdata-mcp-server |
[orgdata], [gcs] |
docs/orgdata.md |
Both servers' code ships in every install; the extras gate dependencies, not
modules. A server whose extra is missing errors with a friendly hint (e.g.
install 'cyborg-mcp-servers[argo]') instead of a raw ImportError.
Install
Requires Python 3.11+. Tagged releases publish to PyPI (via Trusted Publishing); you can also install from a GitHub Release asset or directly from git. (The first PyPI publish needs a one-time project + Trusted Publisher setup — see RELEASING.md.)
# Both servers, all transports and data sources:
uv pip install "cyborg-mcp-servers[all] @ git+https://github.com/openshift-eng/cyborg-mcp-servers"
# Just one server:
uv pip install "cyborg-mcp-servers[argo] @ git+https://github.com/openshift-eng/cyborg-mcp-servers"
uv pip install "cyborg-mcp-servers[orgdata,gcs] @ git+https://github.com/openshift-eng/cyborg-mcp-servers"
Extras: argo, orgdata, gcs (orgdata GCS data source), http (streamable-HTTP
transport; also ships transitively with mcp), dev, and all
(= argo,orgdata,gcs,http).
Run
argo-k8s-mcp # stdio (default); or: argo-k8s-mcp http --port 8080
orgdata-mcp-server stdio # or: orgdata-mcp-server http --port 8000
Client configuration (.mcp.json)
{
"mcpServers": {
"argo-k8s": {
"type": "stdio",
"command": "argo-k8s-mcp",
"env": { "ARGO_MCP_KUBECONFIG_CONTEXT": "your-cluster-context" }
},
"orgdata": {
"type": "stdio",
"command": "orgdata-mcp-server",
"args": ["stdio"],
"env": {
"ORGDATA_GCS_BUCKET": "resolved-org",
"ORGDATA_GCS_OBJECT_PATH": "orgdata/comprehensive_index_dump.json",
"ORGDATA_GCS_PROJECT_ID": "openshift-crt"
}
}
}
}
See each server's doc for the full configuration reference.
In-process use
argo-k8s exposes its tools as an importable library for agent frameworks — see
argo_k8s_mcp.api and docs/argo-k8s.md. orgdata is best
consumed in-process via its underlying library,
orgdatacore, rather than the MCP
server.
Development
make install-dev # uv sync with all extras + dev tooling
make all # lint + format-check + typecheck + test (the CI gate)
make test # pytest (both suites, under tests/)
See CONTRIBUTING.md and RELEASING.md.
Layout
cyborg-mcp-servers/
├── pyproject.toml # one package, per-server extras, hatch-vcs version
├── src/
│ ├── argo_k8s_mcp/ # argo-k8s server + in-process api
│ └── orgdata_mcp/ # orgdata server
├── tests/{argo_k8s,orgdata}/
├── deploy/argo-k8s/ # RBAC manifests for in-cluster deployment
├── scripts/ # cluster setup helpers
└── docs/ # per-server references
Metadata
Release files for cyborg-mcp-servers 0.1.2
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 |
|---|---|---|---|---|
| cyborg_mcp_servers-0.1.2.tar.gz | 71.7 kB | With provenance | Details for cyborg_mcp_servers-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cyborg_mcp_servers-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for cyborg_mcp_servers-0.1.2-py3-none-any.whl |
Total release size: 150.3 kB
Release files / cyborg_mcp_servers-0.1.2.tar.gz
| Download URL | cyborg_mcp_servers-0.1.2.tar.gz |
|---|---|
| Size | 71.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
27a72984c3c915af43e879bb3f2df1561df1d127d82ed5df355aaf16854ef926
|
|
BLAKE2b-256 checksum How to use checksums |
405dbcd365baa895a704a954ffb52e0d13cb5a91a8b2009c58cbaae1ef0edef6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logRelease files / cyborg_mcp_servers-0.1.2-py3-none-any.whl
| Download URL | cyborg_mcp_servers-0.1.2-py3-none-any.whl |
|---|---|
| Size | 78.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f3d6856ceacae1f6f9c494394263cc36d8bf78973d3c128ff01e8051a86b9602
|
|
BLAKE2b-256 checksum How to use checksums |
aa6f626a89826349b1a04eb5cee55412617e4e385ccc339081211d5b024f546c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 11, 2026.
Transparency logSecurity for cyborg-mcp-servers 0.1.2
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 cyborg_mcp_servers-0.1.2.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 Nov 11, 2026.
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.