CloudBees Unify MCP Server

Installation

Use the remote endpoint https://mcp.cloudbees.io/v1/mcp; the legacy local stdio server is deprecated and no local binary or Docker image is required for the remote flow.

Configuration

The documented clients are Claude Code and Gemini. Authenticate with OAuth using the shared public-mcp-client client id.

Claude Code uses an HTTP MCP entry similar to claude mcp add "unify-mcp-server" "https://mcp.cloudbees.io/v1/mcp" --transport http --client-id public-mcp-client.

Gemini uses a manual MCP server entry with httpUrl, authProviderType: dynamic_discovery, the same OAuth client id, and the documented OAuth scopes.

Capabilities

The server exposes CloudBees Unify tools for components, workflows, builds, security findings, feature flags, release orchestration, analytics, and related platform resources.

Security and Privacy

OAuth is browser-based. CloudBees enforces RBAC after authentication, logs tool calls server-side, and only receives tool-call contents and parameters, not the surrounding AI conversation.

Limitations

All tools are visible to authenticated users, but role-based access still limits what resources can be used. The earlier local stdio server is deprecated, and DCR/CIMD client registration methods are not currently supported.