Introduction
Understanding organizationsBest practices: organization designUnderstanding componentsManage organizationsManage componentsManage component Jira integrationsOrganization inheritance reference
Understanding users and teamsUnderstanding role-based access controlManage usersManage teamsConfigure role-based access controlRBAC permissions reference
Understanding authentication in CloudBees UnifyPersonal access tokensManage personal access tokensSet up multifactor authenticationConfigure SAML single sign-onConfigure OIDC authenticationConfigure network security policiesNetwork security reference
Understanding platform configurationUnderstanding environmentsManage properties and secretsManage environmentsTrack environment inventoryConfigure containersSet up preconfigured actionsConfigure notificationsSet up Slack webhook notifications
Accessibility policy referenceShared responsibility model referenceSubscription and services agreementSupport policiesSupported browsers and external tools
Introduction
Understanding application security posture managementUnderstanding Jira ticket creationUnderstanding security center workflowsConfigure security toolsConfigure implicit security analysisConfigure Jira ticketing for an applicationConfigure SBOM analysisDefine security SLAsTriage security findingsUse the organization security dashboardUse the component security centerUse the application security centerUse security overview
Get started with security scanningConfigure SAST scanningConfigure DAST scanningConfigure container scanningConfigure SCA scanningConfigure secret scanningConfigure IaC scanningVerify CloudBees action image signatures and SLSA attestationsSecurity scanner referenceSecurity findings taxonomy
Introduction
Actions catalog
Understanding workflowsCreate a build workflowCreate and manage workflowsCreate reusable workflowsTrigger workflows remotely
View pending approval tasks in your inboxMonitor workflow runsView test results in runsView evidence in runsView deployments in runsManage workflow artifacts
Understanding custom actionsCreate a custom action
Configure workflow credentialsConfigure AWS credentialsConfigure container registry credentialsConfigure Git credentialsIntegrate CyberArk Conjur secrets
Check out source codeBuild and publish container imagesTest and validate containers in workflows
Publish test resultsPublish evidence itemsGenerate a software bill of materialsManage ServiceNow change requestsServiceNow actions reference
Workflow syntax referenceJobs syntax referenceSteps syntax referenceServices syntax reference
Introduction
Understanding release orchestrationManage applicationsCreate deployer workflowsCreate staged workflowsCreate and manage releasesOrchestrate multi-workflow releasesRelease management reference
Understanding artifact managementRegister and track artifactsStore and retrieve artifactsPromote artifactsGenerate a software bill of materialsArtifact management reference
Deploy with HelmDeploy to KubernetesContainer deployment reference
Deploy to AWSAWS deployment reference
Deploy with enterprise platformsExecute remote deployment commandsEnterprise deployment reference
Verify deployments with New RelicDeployment verification reference
Introduction
Understanding feature managementUnderstanding Configuration as CodeGet started with feature managementCreate and manage feature flagsConfigure feature flag targetingOrganize feature flagsImplement feature flag governanceEnable secret modeConfiguration as Code reference
Understanding flag impressions and activity statusUnderstanding flag healthUnderstanding code referencesReview and clean up feature flagsSet up code references
Understanding Jira integration for feature flagsSet up the Jira integrationLink Jira tickets to feature flags
Understanding multiple SDK keysBuild your first mobile app with feature flagsBuild your first feature-flagged web applicationBuild your first feature-flagged backend serviceInstall client-side SDKsInstall server-side SDKsConfigure multiple SDK keysFlag implementation reference
Backend SDK referenceGo SDK referenceJava SDK referencePython SDK referenceRuby SDK referencePHP SDK reference.NET/C# (server-side) SDK referenceNode.js SDK referenceMobile SDK referenceAndroid SDK referenceiOS/tvOS SDK referenceObjective-C SDK referenceSwift SDK referenceReact Native SDK referenceWeb SDK referenceJavaScript (browser) SDK referenceJavaScript SSR SDK referenceClient SDK referenceJava client SDK reference.NET/C# (client-side) SDK referenceC (server-side) SDK referenceC++ (server-side) SDK referenceC (client-side) SDK referenceC++ client SDK reference

Connect Claude Desktop

3 minute read
How-to guide— Task-oriented: directions to achieve a specific goal.

Connect Claude Desktop to the CloudBees Unify MCP Server so you can work with CloudBees Unify conversationally from Claude Desktop. For an overview of the CloudBees Unify MCP Server, refer to Understanding the CloudBees Unify MCP Server.

Claude Desktop calls MCP servers "connectors." The CloudBees Unify MCP Server is available as a connector directly from the Anthropic Claude Directory — no manual configuration required.

Prerequisites

Complete the following before you begin:

  • Install Claude Desktop on your machine.

  • Have an active CloudBees Unify account.

  • Have a web browser available for OAuth authentication.

Add the CloudBees Unify MCP Server

  1. In Claude Desktop, open Settings and select Connectors.

  2. Select the Discover tab.

  3. Search for CloudBees and locate CloudBees Unify MCP Server in the results.

  4. Select + next to CloudBees Unify MCP Server.

    A browser window opens to begin the sign-in flow.

  5. Sign in to CloudBees Unify using Google, GitHub, or your SSO provider.

  6. Select your Root Organization from the list.

    Only organizations you have access to are listed.

  7. Select Open desktop app to return to Claude Desktop.

    Claude Desktop completes the connection.

    During setup, Claude Desktop may display a notice that community connectors have undergone automated review but are not verified by Anthropic. This is expected — the CloudBees Unify MCP Server is distributed through the Anthropic Claude Directory and this notice appears for all directory-listed connectors. Proceed with the setup.

Filter tools

For optimal performance, enable no more than two toolsets at a time. Enabling all available toolsets increases the number of tools exposed to the CloudBees Unify MCP Server, which may degrade performance and response quality. Enable only the toolsets required for your workflow.

The CloudBees Unify MCP Server connected through the Claude Directory uses the all toolset by default. To select specific toolsets, add a custom connector using a URL that includes the toolset query parameter.

For instructions on adding a custom connector in Claude Desktop, refer to Get started with custom connectors using remote MCP in the Anthropic Help Center.

When adding the CloudBees Unify MCP Server as a custom connector, use the following server URL:

https://mcp.cloudbees.io/v1/mcp
▼

To filter to specific toolsets, append the toolset query parameter:

https://mcp.cloudbees.io/v1/mcp?toolset=workflows,application-security
▼

To restrict to read-only tools, add the readonly parameter:

https://mcp.cloudbees.io/v1/mcp?toolset=workflows,application-security&readonly=true
▼

The OAuth client ID is public-mcp-client. Use this exact value. Do not register your own OAuth client ID.

For the full list of available toolsets, refer to CloudBees Unify MCP Server tool reference.

After you add the connector, it appears in your connectors list as type Web with a Custom badge and a Connect button.

Verify the connection

After connecting, the CloudBees Unify MCP Server appears as an active connector in Claude Desktop. Start a new conversation to use the CloudBees Unify MCP Server.

Test the connection with an example prompt:

List my CloudBees Unify components.

Claude Desktop calls the CloudBees Unify MCP Server and returns your component list.

If you receive an error, refer to Troubleshoot CloudBees Unify MCP Server issues.

Manage the connection

After connecting to the CloudBees Unify MCP Server, you can reauthenticate or remove the connector as needed.

Reauthenticate the CloudBees Unify MCP Server

If your authentication expires or you need to switch organizations:

  1. In Claude Desktop, open Settings and select Connectors.

  2. Find CloudBees Unify MCP Server and select it to reauthenticate.

  3. Complete the OAuth flow in your browser.

  4. Select your organization.

Remove the CloudBees Unify MCP Server connector

To remove the CloudBees Unify MCP Server connector:

  1. In Claude Desktop, open Settings and select Connectors.

  2. Find CloudBees Unify MCP Server and select Disconnect.

To reconnect, return to the Discover tab.

Troubleshoot

If you encounter connection or authentication issues, refer to Troubleshoot CloudBees Unify MCP Server issues.

Connect Claude Code
Connect Gemini