How to Connect Bitbucket Data to Gemini Enterprise via CData Connect AI

Gemini Enterprise is Google's enterprise AI assistant, available as part of Google Workspace. With native support for Custom MCP Server data stores, Gemini Enterprise can be extended to query and act on live enterprise data via the Model Context Protocol (MCP). When combined with CData Connect AI Remote MCP, Gemini Enterprise can interact with Bitbucket data in real time using natural language — without data replication or custom integration logic.

CData Connect AI offers a dedicated cloud-to-cloud interface for connecting to Bitbucket data via a single managed MCP endpoint. The CData Connect AI Remote MCP Server enables secure communication between Gemini Enterprise and Bitbucket, allowing users to ask questions and take actions on live Bitbucket data through natural language prompts.

This article explains how to connect Gemini Enterprise to live Bitbucket data through CData Connect AI by creating a Custom MCP Server data store — giving users access to Bitbucket data directly from the Gemini Enterprise chat interface.

Prerequisites

1. A CData Connect AI account with at least one active connection (e.g., Bitbucket)
2. A Gemini Enterprise account (trial available)
3. A Google Cloud project with billing enabled
4. The Google Cloud CLI installed and configured
5. In your Google Cloud account:
   • Override the organization policy for Custom MCP data stores (learn more).
   • Grant the Discovery Engine Editor role to the administrator (learn more).

Step 1: Configure Bitbucket connectivity for Gemini Enterprise

Connectivity to Bitbucket from Gemini Enterprise is made possible through CData Connect AI Remote MCP. To interact with Bitbucket data from Gemini Enterprise, start by creating and configuring a Bitbucket connection in CData Connect AI.

1. Log into Connect AI, click Sources, and then click Add Connection

2. Select "Bitbucket" from the Add Connection panel

3. Enter the necessary authentication properties to connect to Bitbucket.

   For most queries, you must set the Workspace. The only exception to this is the Workspaces table, which does not require this property to be set, as querying it provides a list of workspace slugs that can be used to set Workspace. To query this table, you must set Schema to 'Information' and execute the query SELECT * FROM Workspaces>.

   Setting Schema to 'Information' displays general information. To connect to Bitbucket, set these parameters:

   • Schema: To show general information about a workspace, such as its users, repositories, and projects, set this to Information. Otherwise, set this to the schema of the repository or project you are querying. To get a full set of available schemas, query the sys_schemas table.
   • Workspace: Required if you are not querying the Workspaces table. This property is not required for querying the Workspaces table, as that query only returns a list of workspace slugs that can be used to set Workspace.

   Authenticating to Bitbucket

   Bitbucket supports OAuth authentication only. To enable this authentication from all OAuth flows, you must create a custom OAuth application, and set AuthScheme to OAuth.

   Be sure to review the Help documentation for the required connection properties for you specific authentication needs (desktop applications, web applications, and headless machines).

   Creating a custom OAuth application

   From your Bitbucket account:

   1. Go to Settings (the gear icon) and select Workspace Settings.
   2. In the Apps and Features section, select OAuth Consumers.
   3. Click Add Consumer.
   4. Enter a name and description for your custom application.
   5. Set the callback URL:
      • For desktop applications and headless machines, use http://localhost:33333 or another port number of your choice. The URI you set here becomes the CallbackURL property.
      • For web applications, set the callback URL to a trusted redirect URL. This URL is the web location the user returns to with the token that verifies that your application has been granted access.
   6. If you plan to use client credentials to authenticate, you must select This is a private consumer. In the driver, you must set AuthScheme to client.
   7. Select which permissions to give your OAuth application. These determine what data you can read and write with it.
   8. To save the new custom application, click Save.
   9. After the application has been saved, you can select it to view its settings. The application's Key and Secret are displayed. Record these for future use. You will use the Key to set the OAuthClientId and the Secret to set the OAuthClientSecret.
   
4. Click Save & Test
5. Navigate to the Permissions tab in the Add Bitbucket Connection page and update the User-based permissions.

Create an OAuth App in CData Connect AI

Gemini Enterprise uses OAuth 2.0 Authorization Code with PKCE to authenticate users against the CData Connect AI MCP Server. This requires creating a user-based OAuth App in your CData Connect AI account.

1. Click the Gear icon () in the top-right corner of Connect AI to open Settings.
2. Navigate to OAuth Apps and click + Create App. The Create OAuth App dialog appears.
3. Enter the following settings:
   • Name — Enter a descriptive name (e.g., GeminiEnterpriseOAuth).
   • Authentication Flow — Select User-based (Authorization Code).
   • Callback URL — Enter https://vertexaisearch.cloud.google.com/oauth-redirect.
   
4. Click Confirm. CData Connect AI creates the OAuth App and generates a Client ID and Client Secret.
5. Copy both the Client ID and Client Secret values. You will need them in Step 5.

With the connection configured and an OAuth App created, we are ready to create the custom MCP server data store in Gemini Enterprise.

Step 2: Create the custom MCP server data store

1. Open Gemini Enterprise and navigate to the Data stores screen.
2. Click Create data store.
3. On the Select a data source page, enter Custom MCP Server in the Search sources field. The Custom MCP Server card displays.
4. Click Add MCP server. The MCP Server Configuration page displays.
5. In the Authentication settings section, enter values in the following required fields:
   • MCP Server URL: https://mcp.cloud.cdata.com/mcp
   • Authorization URL: https://cloud-login.cdata.com/authorize
   • Token URL: https://cloud-login.cdata.com/oauth/token
   • Client ID and Client Secret: From the OAuth App created in Step 1
   
6. Click Login, and complete the sign-in.
7. Click Continue, and the Advanced options section opens.

8. In the MCP Server Description field, enter a description that helps Gemini Enterprise understand what the server does and when to use it. For more information, see Write effective MCP server descriptions and instructions.

9. Click Continue.

10. In the Configure your data connector section, select the Location of your data connector from the Multi-region field list.

11. In Your data connector name, enter a name for your data store.

12. Click Create. Gemini Enterprise creates your data store and displays your data stores on the Data Stores page.

    Note: By default, no tools or actions from your custom MCP servers are enabled. You must enable the tools or actions.

Step 3: Enable actions

After creating the custom MCP server data store, you must enable at least one tool or action before it can be used in Gemini Enterprise.

1. Go to your custom MCP server data store.

2. Open the Actions tab and select Reload custom actions to reauthenticate.

   Note: This action performs a tools/list call on the MCP server to retrieve available tools, which are then displayed on the screen.

3. Select the actions to enable.
4. Click Enable actions.

Step 4: Connect the MCP server data store to a Gemini Enterprise app

After creating the custom MCP server data store and enabling actions, you must connect the data store to a Gemini Enterprise app before it can be used.

1. In the Google Cloud console, go to the Gemini Enterprise page.
2. From the navigation menu, click Apps.
3. Select the Gemini Enterprise app where you want to connect your data store.
4. From the navigation menu of the app, click Connected data sources.
5. Click Add existing data stores and select your data store.
6. Click Connect.

Step 5: Query live Bitbucket data with natural language

With the data store connected, Gemini Enterprise users can interact with live Bitbucket data using natural language from the Gemini Enterprise web application. Each user authenticates with their own Connect AI credentials via the OAuth flow on first use.

1. Open Gemini Enterprise, click Connections and authorize CData Connect AI.
2. Ask natural language questions about your Bitbucket data:
   • "Show me all Bitbucket data from the last 30 days"
   • "What are the top records in Bitbucket data by revenue?"
   • "List all active Bitbucket data and their current status"
   • "Summarize Bitbucket data activity for this quarter"
3. The agent automatically discovers available connections in Connect AI, identifies the most relevant Bitbucket connection, generates SQL, and returns results — all without requiring the user to write queries or understand the underlying data structure.

Get CData Connect AI

To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from Gemini Enterprise and other AI platforms, try CData Connect AI today!