The CloudBees MCP server respects your privacy:
-
The CloudBees MCP server only communicates with servers and services specific to CloudBees Unify services.
-
The CloudBees MCP server does not transmit usage telemetry to any service.
-
The CloudBees MCP server does not transmit error reporting telemetry to any service unless explicitly enabled.
CloudBees Unify
For information about how your data is handled within CloudBees systems and data processors, refer to the CloudBees Privacy Policy.
| Only the API calls required to deliver the MCP services are made to the CloudBees Unify backend. However, there may not be a 1:1 mapping, nor is this mapping documented beyond the code. |
User-Agent
The CloudBees MCP server sends a versioned User-Agent with all HTTP calls to the CloudBees Unify environment so it is able to detect and monitor MCP and API usage as part of normal HTTP traffic. The user agent does not identify you beyond the version, platform, and architecture of the CloudBees MCP server that you’re connecting with. For example, the cloudbees-mcp/27e6eeab-03a7-4fac-8dec-8a4f7d50602d/darwin-arm64 UUID is an opaque UUID for the binary; it is the same for every download of that version. This behavior cannot be disabled without recompiling the CloudBees MCP server with the code removed.
Search for User-Agent to find the user agent code.
|
Error reporting
If your CloudBees MCP server installation has an unexpected error, details of the error are logged to the CloudBees reporting service (Sentry), to help identify and reproduce the problem.
Detailed context elements (for example, credentials and query data) are not sent to our server.
By default, error reporting is disabled in all builds. If you are experiencing errors, enable error reporting with the --error-reporting=true option, and then contact CloudBees Support.
|