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 Google Antigravity

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

Configure Google Antigravity to connect to the CloudBees Unify MCP Server so you can work with CloudBees Unify conversationally from Antigravity. For an overview of the CloudBees Unify MCP Server, refer to Understanding the CloudBees Unify MCP Server.

Prerequisites

Complete the following prerequisites before you begin:

  • Enable MCP support in Google Antigravity.

  • Have an active CloudBees Unify account.

  • Have a web browser available for OAuth authentication.

Add the CloudBees Unify MCP Server

Google Antigravity does not have a command-line tool to add your CloudBees Unify MCP Server with OAuth parameters. You need to manually add the CloudBees Unify MCP Server configuration to Antigravity’s mcp_config.json file.

  1. Locate your Antigravity MCP configuration file:

    • macOS/Linux: ~/.gemini/config/mcp_config.json

    • Windows: %USERPROFILE%\.gemini\config\mcp_config.json

  2. Open the file in a text editor.

  3. Add the CloudBees Unify MCP Server configuration to the mcpServers section:

    {
  "mcpServers": {
    "unify-mcp-server": {
      "serverUrl": "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.

    public-mcp-client is the shared OAuth client ID for the CloudBees Unify MCP Server. Use this exact value and do not register or generate a new client ID.

    This configuration uses the default toolset. If no X-MCP-Toolsets header is passed, the server applies its default set of tools. To explicitly control which toolset Antigravity can use, add a headers field:

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

    To restrict to read-only tools, ensuring the AI agent can view but not modify CloudBees Unify resources, add "X-MCP-Readonly": "true" to the headers block inside unify-mcp-server:

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

    To opt in to all tools, set X-MCP-Toolsets to all inside the headers block:

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

  4. Save the file.

Authenticate with CloudBees Unify

After adding the server configuration, you need to authenticate the first time you use the CloudBees Unify MCP Server.

  1. Start Google Antigravity.

  2. Perform an action that requires CloudBees Unify, such as asking about your components.

    Antigravity detects that authentication is required and opens a new browser window showing the CloudBees Unify sign-in page.

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

  4. Select your Root Organization from the list.

  5. The browser shows "Authentication successful".

  6. Return to Google Antigravity.

  7. Antigravity confirms the connection and completes your request.

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.

Verify the connection

Test the connection by asking Antigravity a question that requires CloudBees Unify:

What CloudBees Unify components do I have access to?

Antigravity should call the CloudBees Unify MCP Server and return your component list.

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

Manage the connection

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

Disconnect from the CloudBees Unify MCP Server

To temporarily disconnect from the CloudBees Unify MCP Server:

  1. Open your Antigravity mcp_config.json file (refer to Add the CloudBees Unify MCP Server for the file paths).

  2. Comment out or remove the unify-mcp-server entry from the mcpServers object.

  3. Save the file.

You can reconnect by uncommenting or re-adding the configuration.

Reauthenticate the CloudBees Unify MCP Server

If your authentication expires or you need to switch organizations, perform an action that requires CloudBees Unify. Antigravity prompts you to re-authenticate and opens a browser window to complete the OAuth flow.

Remove the CloudBees Unify MCP Server

To completely remove the CloudBees Unify MCP Server, open your Antigravity mcp_config.json file (refer to Add the CloudBees Unify MCP Server for the file paths), remove the unify-mcp-server entry from the mcpServers object, and save the file.

Troubleshooting

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

Connect Cursor
Connect VS Code