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 notifications
Accessibility policy referenceShared responsibility model referenceSubscription and services agreementSupport policiesSupported browsers and external tools
Introduction
Understanding feature managementUnderstanding Configuration as CodeGet started with feature managementCreate and manage feature flagsConfigure feature flag targetingOrganize feature flagsImplement feature flag governanceConfiguration 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 keysMobile SDK referenceWeb SDK referenceBackend SDK referenceClient SDK referenceFlag implementation reference
Introduction
Understanding CI workflowsCreate a build workflowCreate 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 external secret providers
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

Get started with the CloudBees Unify MCP Server

3 minute read

This tutorial walks you through connecting your AI client to the CloudBees Unify MCP Server and running your first conversational commands. By the end, you can query CloudBees Unify directly from your AI client using natural language.

Approximate time to complete: 15 minutes.

Prerequisites

Complete the following prerequisites before you begin:

  • Sign in to an active CloudBees Unify account.

  • Install an MCP-compatible AI client (Claude Code, Claude Desktop, or Gemini).

  • Have access to at least one component or workflow in CloudBees Unify.

Configure your AI client

First, configure your AI client to connect to the CloudBees Unify MCP Server. The exact configuration depends on which AI client you use.

Follow the connection guide for your client, then return here to continue:

Authenticate with CloudBees Unify

When you first connect to the CloudBees Unify MCP Server, you sign in through your browser:

  1. Your AI client opens a browser window.

  2. The sign-in page for CloudBees Unify displays.

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

  4. Select your Root Organization from the list. You only see organizations you have access to.

  5. The browser displays "Authentication successful" and closes.

  6. Your AI client confirms the connection.

You only need to authenticate once. Your AI client stores your credentials securely for future tool calls.

If you’re already signed in to CloudBees Unify in your browser, authentication may complete automatically.

Verify the connection

Next, run a test to confirm your AI client can reach CloudBees Unify.

In your AI client, enter:

Who am I in CloudBees Unify?

The agent calls the user_whoami tool and returns your user information:

Example 1. Response
You are Sam Admin (sam.admin@example.com) in the Acme Corporation organization.

If you encounter an error message instead, refer to Troubleshoot common issues with the CloudBees Unify MCP Server.

List available tools

Ask your AI agent to show which CloudBees Unify capabilities are available:

What CloudBees Unify tools do you have access to?

The agent lists the available tools organized by category:

  • Component management

  • Workflow operations

  • Build status and logs

  • Security findings

  • Feature flags

  • CI controller status

  • User and team management

You can also view tools in your AI client’s CloudBees Unify MCP Server settings or tool list interface.

Try common operations

Now that you’re connected, try some common use cases.

List your components

Ask the agent to list the components you can access:

List all CloudBees Unify components I have access to.

The agent calls the appropriate tool and returns a list of components with their names, IDs, and status.

Check build status

Ask about a recent build for a specific component:

What’s the status of my latest build for the payment-service component?

The agent:

  1. Finds the payment-service component.

  2. Retrieves recent builds.

  3. Identifies the most recent one.

  4. Reports its status (success, failure, in progress).

View build logs

If a build failed, you can investigate immediately:

Show me the logs for build #42.

The agent fetches and displays the build logs, making it easy to diagnose issues without leaving your IDE.

Manage workflows

Ask the agent to list workflows for a component:

List all workflows for the api-gateway component.

The agent returns workflow names, trigger conditions, and current status.

Check security findings

Ask the agent to summarize security findings:

What security vulnerabilities were found in my last build?

The agent queries security findings and summarizes any issues discovered during the build process.

Understand tool behavior

When you ask a question in natural language:

  1. The AI agent determines what information it needs.

  2. It calls CloudBees Unify tools with appropriate parameters.

  3. Results return to the AI agent.

  4. The agent composes a natural language answer.

You don’t need to know the exact tool names or parameters, just ask in plain English.

For complex questions, the agent may call multiple tools in sequence to gather all needed information.

Explore further

Now that you’ve completed the basics, explore more advanced capabilities:

  • Configure feature flags for different environments.

  • Trigger workflows conversationally.

  • Investigate CI controller reports.

  • Query team membership and permissions.

Refer to CloudBees Unify MCP Server tool reference for the complete list of available operations.

Understanding MCP privacy and data handling
Connect Claude Code