Introduction
Understanding organizationsUnderstanding componentsManage organizationsManage componentsManage component Jira integrations
Understanding users and teamsUnderstanding role-based access controlManage usersManage teamsConfigure role-based access controlRBAC permissions reference
Understanding authentication in CloudBees UnifySet 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 CI workflowsUnderstanding custom actionsCreate a build workflowCreate a custom actionCreate and manage workflowsCreate reusable workflowsTest and validate containers in workflowsCheck out source codeTrigger workflows remotelyWorkflow syntax referenceJobs syntax referenceSteps syntax referenceServices syntax reference
View pending approval tasks in your inboxMonitor workflow runsView test results in runsView evidence in runsView deployments in runsManage workflow artifactsPublish test resultsPublish evidence itemsGenerate a software bill of materialsManage ServiceNow change requests
Configure workflow credentialsConfigure AWS credentialsConfigure container registry credentialsConfigure Git credentialsIntegrate CyberArk Conjur secrets
Understanding GitHub Actions integrationSet up GitHub Actions integrationDisplay GitHub Actions workflows and runsRegister GHA build artifactsPublish GHA deployed artifactsPublish GHA test resultsPublish GHA evidence itemsTrigger CloudBees workflows from GitHub ActionsScan with GitHub Actions
Understanding CloudBees CI and Jenkins® integrationConnect CI and Jenkins controllersMonitor CI and Jenkins buildsRegister CI build artifactsRegister CI deployed artifactsPublish CI test resultsConfigure CI security scanningCI and Jenkins integration reference
Build and publish container imagesUnderstanding external CI/CD integrationsRun external CI/CD jobsExternal CI/CD action 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

2 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.

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