Install the CloudBees Unify MCP Server

2 minute read

Install the latest CloudBees Unify MCP Server 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 Unify MCP Server

To use the CloudBees Unify MCP Server, 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 Unify MCP Server 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.

OS Link SHA-256 Signature

Linux / Windows WSL - AMD64

Download

SHA-256

Signature

Linux / Windows WSL - ARM64

Download

SHA-256

Signature

Darwin / MacOS (Intel / AMD64)

Download

SHA-256

Signature

Darwin / MacOS (Silicon / ARM64)

Download

SHA-256

Signature

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

Download

SHA-256

Signature

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

Download

SHA-256

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-unify-mcp-server-image.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-unify-mcp-server-image.pub \
    docker.io/cloudbees/unify-mcp-server:latest

Verification for index.docker.io/cloudbees/unify-mcp-server:latest --
The following checks were performed on each of these signatures:
  - The cosign claims were validated
  - Existence of the claims in the transparency log was verified offline
  - The signatures were verified against the specified public key

[... detailed JSON output ...]
▼

An exit code of 0 from cosign verify indicates that the images were verified successfully.

Verify and install native binaries

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

  1. To verify the integrity, compute the SHA-256 checksum of the binary and compare it to the provided SHA-256 file.

  2. To verify the signature, use Cosign as follows:

    $ cat > cloudbees-unify-mcp-server.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-unify-mcp-server.pub \
     --signature cloudbees-unify-mcp-server.sig \
     cloudbees-unify-mcp-server
Verified OK
    ▼

  3. (Linux/macOS only) After downloading and verifying the binary, make the binary executable:

    $ chmod u+x cloudbees-unify-mcp-server
    ▼
    For system-wide access, move the binaries to a directory in your PATH.

Troubleshoot

The Docker container will not start

This is often caused by an invalid configuration.

Your best course of action is to find the logs for the failed Docker container launch. For example:

$ docker ps -a | grep cloudbees-unify-mcp-server
617379696134   cloudbees/unify-mcp-server:latest "/cloudbees-unify-mcp-server stdi…"   9 minutes ago   Up 9 minutes beautiful_swamp
$ docker logs 617379696134
<illuminating log messages>
▼
macOS refuses to open the native binary

macOS Gatekeeper may block the native binary from running, displaying one of these messages:

  • cannot be opened because it is from an unidentified developer

  • cannot be opened because Apple cannot check it for malicious software

This happens because the binary is not notarized by Apple. However, you can verify its integrity using the SHA-256 checksum and signature verification as described in Verify and install native binaries.

To override the macOS Gatekeeper and allow the binary to run:

  1. Go to System Settings  Privacy & Security.

  2. Scroll down to the Security section.

  3. Next to the message about the blocked binary, select Open Anyway or Allow Anyway.

  4. When prompted, select Open to confirm.

Alternatively, you can use the command line to remove the quarantine attribute:

$ xattr -d com.apple.quarantine cloudbees-unify-mcp-server
▼
Set up CloudBees Unify MCP Server