MCP on

Chainguard MCP servers overview

Wed, 16 Sep 2026 00:00:00 +0000

Four of Chainguard’s MCP servers give an AI tool direct access to live product data: the container images in cgr.dev, the Wolfi package index, upstream version and end-of-life history, and the Chainguard platform API. An MCP client connected to them can answer questions such as what a given image’s SBOM contains, which Wolfi package replaces a Debian one, or whether an upstream release is still supported, using data from the product itself rather than from a model’s training data.

cg-api: the Chainguard platform API MCP server

Wed, 16 Sep 2026 00:00:00 +0000

cg-api exposes the Chainguard platform API — the same API behind chainctl and the Chainguard Console — to an MCP client. Through it, a client can resolve which organizations and folders you belong to, list the image repositories and tags your account holds, inspect roles, role bindings, identity providers, and cloud account associations, and read security advisories. It is the broadest of Chainguard’s four product-data MCP servers, and the only one that reaches organization and IAM data.

cg-apk: the Chainguard APK registry MCP server

Wed, 16 Sep 2026 00:00:00 +0000

cg-apk gives an AI tool read-only access to the Chainguard APK registry — the Wolfi package index that Chainguard container images are built from. This lets a client look up a package by name to find its current version, license, and origin, then read the SPDX SBOM and the melange build recipe embedded in the APK itself. That combination answers questions the package index alone cannot: not just which version of openssl ships today, but which upstream commit it was built from and what build definition produced it.

cg-oci: the Chainguard container registry MCP server

Wed, 16 Sep 2026 00:00:00 +0000

cg-oci gives an AI tool read-only access to the Chainguard container registry at cgr.dev. Through it, a client can list the repositories and tags your account can reach, fetch a manifest or image config by tag or digest, and read the signed attestations attached to an image — its SPDX SBOM, its apko build configuration, and its SLSA build provenance. Every response comes from the registry as it exists at the moment of the call, so an AI tool can answer what a specific image actually contains rather than what its documentation says it contains.

cg-versions: the upstream version history MCP server

Wed, 16 Sep 2026 00:00:00 +0000

cg-versions gives an AI tool a read-only catalog of the upstream projects Chainguard tracks version information for. Through it, a client can find a tracked project, list its version streams with their end-of-life dates, and read the release history of one stream, whole or a page at a time, with attribution back to the upstream tag and commit each release came from. It answers questions about what upstream projects have published and what is still supported: whether Python 3.9 is past end of life, which streams of a project are still receiving releases, and which upstream commit a given version corresponds to.