Introduction
Understanding organizationsUnderstanding componentsManage organizationsManage componentsManage component Jira integrations
Set up your first organizationUnderstanding 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
Monitor 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 Code

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

Configure Claude Code to connect to the CloudBees Unify MCP Server so you can work with CloudBees Unify conversationally from your terminal. For an overview of the CloudBees Unify MCP Server, refer to Understanding the CloudBees Unify MCP Server.

Prerequisites

Complete the following before you begin:

  • Install Claude Code on your machine.

  • Have an active CloudBees Unify account.

  • Have a web browser available for OAuth authentication.

Add the CloudBees Unify MCP Server

Add the CloudBees Unify MCP Server using either a command or by editing the configuration file directly.

Option 1: Add via command (recommended)

In your terminal, run:

claude mcp add \
  "unify-mcp-server" \
  "https://mcp.cloudbees.io/v1/mcp" \
  --transport http \
  --client-id public-mcp-client
▼

Claude Code adds the CloudBees Unify MCP Server to your MCP configuration using the default toolset unless you configure headers.

public-mcp-client is the shared OAuth client ID for the CloudBees Unify MCP Server. Use this exact value. You do not need to register your own.
If you get an error about --client-id being an unknown option, run claude update to get the latest version.

Filter tools using toolset headers

To connect with specific toolsets, pass --header flags:

claude mcp add \
  "unify-mcp-server" \
  "https://mcp.cloudbees.io/v1/mcp" \
  --transport http \
  --client-id public-mcp-client \
  --header "X-MCP-Toolsets: workflows,application-security"
▼

To restrict to read-only tools:

claude mcp add \
  "unify-mcp-server" \
  "https://mcp.cloudbees.io/v1/mcp" \
  --transport http \
  --client-id public-mcp-client \
  --header "X-MCP-Toolsets: workflows,application-security" \
  --header "X-MCP-Readonly: true"
▼

To opt in to all tools:

claude mcp add \
  "unify-mcp-server" \
  "https://mcp.cloudbees.io/v1/mcp" \
  --transport http \
  --client-id public-mcp-client \
  --header "X-MCP-Toolsets: all"
▼

Omit --header entirely to use the default toolset.

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

Toolset filtering using X-MCP-Toolsets and X-MCP-Readonly headers is supported for all MCP clients, including Antigravity, Cursor, Claude Code, and Gemini.

Option 2: Add via configuration file

  1. Locate your Claude Code MCP configuration file:

    • macOS: ~/.claude.json

    • Linux: ~/.claude.json

    • Windows: %USERPROFILE%\.claude.json

  2. Open the file in a text editor.

  3. Add the CloudBees Unify MCP Server entry:

    {
  "mcpServers": {
    "unify-mcp-server": {
      "type": "http",
      "url": "https://mcp.cloudbees.io/v1/mcp",
      "oauth": {
        "clientId": "public-mcp-client"
      }
    }
  }
}
    ▼

    If you already have other MCP servers configured, add the unify-mcp-server entry to the existing mcpServers object.

Filter tools using toolset headers

To request specific toolsets, add a headers field alongside the oauth block:

{
  "mcpServers": {
    "unify-mcp-server": {
      "type": "http",
      "url": "https://mcp.cloudbees.io/v1/mcp",
      "oauth": {
        "clientId": "public-mcp-client"
      },
      "headers": {
        "X-MCP-Toolsets": "workflows,application-security"
      }
    }
  }
}
▼

To restrict to read-only tools:

"headers": {
  "X-MCP-Toolsets": "workflows,application-security",
  "X-MCP-Readonly": "true"
}
▼

To opt in to all tools:

"headers": {
  "X-MCP-Toolsets": "all"
}
▼

Omit headers entirely to use the default toolset.

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

Toolset filtering using X-MCP-Toolsets and X-MCP-Readonly headers is supported for all MCP clients, including Antigravity, Cursor, Claude Code, and Gemini.

  1. Save the file.

  2. Restart Claude Code.

  3. If prompted, enter /mcp and select Connect to reauthenticate.

Authenticate with CloudBees Unify

After adding the server, authenticate with CloudBees Unify:

  1. In Claude Code, enter /mcp to open the MCP servers panel.

  2. Find "unify-mcp-server" in the list.

  3. Select Connect or Authenticate.

  4. A new browser window opens showing the CloudBees Unify sign-in page:

    1. Sign in using Google, GitHub, or your SSO provider.

    2. Select your Root Organization from the list.

    3. The browser shows "Authentication successful".

    4. Return to Claude Code.

  5. Claude Code confirms the connection.

If you’re already signed in to CloudBees Unify in your browser, the organizations you have access to are listed. Be sure your Root Organization is selected. Only organizations you have access to are listed.

Verify the connection

For example, ask Claude Code:

List my CloudBees Unify components.

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

You can also verify the connection in the CloudBees Unify MCP Server panel:

  1. Enter /mcp in Claude Code.

  2. Confirm "unify-mcp-server" displays a connected status indicator.

  3. Select View Tools to list the available CloudBees Unify tools.

Manage the connection

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

Disconnect from the CloudBees Unify MCP Server

If you need to disconnect:

  1. In Claude Code, enter /mcp to open the MCP servers panel.

  2. Find "unify-mcp-server".

  3. Select Disconnect.

Your configuration remains in place; you can reconnect at any time.

Reauthenticate the CloudBees Unify MCP Server

If your authentication expires or you need to switch organizations:

  1. In Claude Code, enter /mcp to open the MCP servers panel.

  2. Find "unify-mcp-server".

  3. Select Reauthenticate.

  4. Complete the OAuth flow in your browser.

  5. Select the desired organization.

Remove the CloudBees Unify MCP Server

To completely remove the CloudBees Unify MCP Server, run:

claude mcp remove unify-mcp-server
▼

Alternatively, open your MCP configuration file (refer to Option 2: Add via configuration file above), remove the unify-mcp-server entry from the mcpServers object, save the file, and restart Claude Code.

Troubleshooting

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

Get started with the CloudBees Unify MCP Server
Connect Gemini