Set up the CloudBees CI MCP Router

2 minute read

Prior to installing the CloudBees CI MCP Router, install the MCP Server plugin to one or more CloudBees CI controllers and configure authentication by generating an API token from the operations center and encoding it for HTTP basic authentication.

Prerequisites

Before you begin, ensure that you have the following prerequisites in place:

  • CloudBees CI on modern cloud platforms running version 2.528.1.29783 or later.

    CloudBees CI on traditional platforms is not supported.
  • Access to one or more controllers where you can install the MCP Server plugin.

  • An account with sufficient permissions to generate an API token in the operations center.

Install the MCP Server plugin

Before configuring authentication, install the MCP Server plugin to one or more controllers.

Generate an API token

You must generate an API token from the operations center.

If you generate an API token from a controller instead of the operations center, the token is not valid for use with the CloudBees CI MCP Router and a connection cannot be established.

To generate an API token:

  1. Sign in to the operations center.

  2. Select in the upper-right corner, and then select Security.

  3. Select Add new token.

  4. Enter a name to distinguish the token, and then select Generate.

  5. Copy the token and store it in a secure location for later use.

    Once you leave the page, you cannot view or copy the token again.
  6. Select Done to add the token.

  7. Select Save to save your changes.

Encode credentials for HTTP basic authentication

Use basic HTTP authentication with the MCP agent by encoding it with the API token.

To encode credentials on Linux, macOS, or Windows:

Open a terminal and run the following command, replacing <username> and <token> with your actual username and the API token you generated in the operations center:

Linux or macOS
Windows (PowerShell)
echo -n "<username>:<token>" | base64
[Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes("<username>:<token>"))

If successful, the Base64-encoded credential is output, similar to the following:

dXNlcm5hbWU6dG9rZW4=

Store the encoded credential in a secure location for later use.

Base64 encoding is not encryption. Anyone with access to the encoded string can decode it and obtain your credentials. Always protect the encoded credentials as if they are the original username and token.