Download CloudBees MCP

2 minute read

Download the latest CloudBees MCP early-access container images and binaries.

During the early-access period:

  • CloudBees does not apply version numbers to these assets, opting to deliver new features and fixes faster by updating the latest version instead.

  • CloudBees recommends using these assets only in non-production environments.

Download the CloudBees MCP server

To use the CloudBees MCP, you must have the container image/binary available locally or in your cluster. The method depends on your deployment environment. Choose one of the following methods:

Download for Docker

You can download the CloudBees MCP image from Docker Hub. This is a multi-architecture image that will run under Docker on amd64 and arm64 CPUs.

Download native binaries

You can download precompiled native binaries for Linux, macOS, and Windows.

The cloudbees-mcp update command always downloads and replaces the binary, even if it is already up-to-date. Use this to ensure you are running the latest version.
OS Link SHA256 Signature

Linux / Windows WSL - AMD64

Download

SHA256

Signature

Linux / Windows WSL - ARM64

Download

SHA256

Signature

Darwin / MacOS (Intel / AMD64)

Download

SHA256

Signature

Darwin / MacOS (Silicon / ARM64)

Download

SHA256

Signature

Windows (Intel) - legacy build, not typically required.

Download

SHA256

Signature

Windows (ARM64) - for advanced or non-standard environments.

Download

SHA256

Signature

Verify the signature

All of CloudBees software distributions are signed using sigstore/cosign.

Refer to the following Cosign documentation for installation and signature verification steps:

Verify Docker images

After downloading the Docker image, you can verify its signature.

$ cat > cloudbees-mcp.pub <<EOF -----BEGIN PUBLIC KEY----- MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA5zmVkDnpCVKyx2BMHywG N5dbo+//NfSui89OYE1KmN4jWY1s5cifWl1Vf2OOYQE/REcLLrsBBtz+pgoc6hou jZILMU1LD6QkqZy3SlI8eXP9FauL7J301sW0EVx6i6HQErI32N8tsAGcBGolaq7L bc/8ymHQxtnj8/d3ek3zVQbOtddfves3+ZlKjTvNhyDDYT4/37+UHVyzI78J8QFe QA3aLLaiGNBbF+7OlsImlwdxbdZSLnFZWEjM6CJb6/OQ5VVfL96yY+gr9Xu6KjqE lcA38x3nWEC8YtVbA14FijvCKa4yZ2hSf0uwXLdrLGdqi5zFKrcCY6c3cyVYP05h 7yMnOolfOCMODw/0Y3499ExyB9T7Bha1FiU+GjqEvfqBrJkihRkUwAOox1kkGqB1 kzWIEmTaJe/a5I9CFzcLiNAIdwqZp1bfcuqLQGf1l32LYp+BaUj6TMG41fhAyO4B UQa26GbLEEgL4YxltkeHVfnEtQus/mApE/n5tIiElTjcEGcValospGr4VkFqviqn o8jXXmIhDhb5fNl3ETOVDT/zOXvAu1YC5tKoYpNMEOvOD+yiZYQjsu8gYYJUC+Kw /m5drPbwgFdqKak8v+VHhPvI3/7eev/a6IPpSPHVOMgvypyVFXs4vV7TjH5vCn/1 w/tOI37axvU+gaj7R4gLUCECAwEAAQ== -----END PUBLIC KEY----- EOF $ cosign verify \ --key cloudbees-mcp.pub \ docker.io/cloudbees/cloudbees-mcp:latest Verified OK

Verify native binaries

After downloading the native binary, you can verify its signature.

$ cat > cloudbees-mcp.pub <<EOF -----BEGIN PUBLIC KEY----- MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEAs6gFdCxqDM3yrXy39GjC veINWm80WfC3C6ojBWMSaNLlZkAij+SwNfCgWp7vsfMDe6MdsPf4IwGc5+YTAM4j k0uCn/hS5GkMujqhtpr3hrTJKkyhRJKfQW1gepE2Xy8pIwlwhJwrMuf5/9ElvcUb GM8jns8tSGW91k78xZIDaMFbGX0sJyhFXY7hsA/3jnq8in39xSPxAfmFqeO1DPT2 7C6AxHYvQCvg4XGPK8jw/73q0fHWD/4k4cTOjtldxdN6PSUbM9nTwRMDrGl/+Lt8 g5hXRLly3rcjKlpIeLoxbyqps0buTzn9QnA94zQECuawmXjC+FTi0HEBwpGXK8Zn lM1AougI/fuYHxG0s3Usl2AlbuuW+LKqDj7e5bOhao+Ri1q5M7nVYwHoHDoo4QsN DYTqRkTlInPUZq67oIUcnM5KrA/BrRWCJOeQSnMKOn1QQbEmwKFHbmgVn5pHLueI EXJgbSlVj2bBTwhqUrvrOt9q6zjJYUUIJ0/JDT4N7v+ZdOlsUUVbdkYwgQPj6JNv oK3COl3Ffb8jUWQMMXJGFEsfbOXkvqijkmM9mmDZYT8hblCVa0+nJO3qtTDEkfyT pgDlrhUpuezyyC/78Ol4pci1l4r6tpzzk9+jZyCI5jmC+0jvlyZElOfQ3ZOFTJPq RBMIcT74EXmNIOIO67QStmsCAwEAAQ== -----END PUBLIC KEY----- EOF $ cosign verify-blob \ --key cloudbees-mcp.pub \ --signature cloudbees-mcp.sig \ cloudbees-mcp Verified OK