Integrate Cline with Live Bitbucket Data via CData Connect AI

Cline is an autonomous AI coding agent that runs inside modern IDEs such as VS Code and Cursor. It enables developers to build agent-driven workflows that can reason through tasks, execute actions, and interact with external systems directly from the editor using a structured execution model.

By integrating Cline with CData Connect AI through the built-in MCP (Model Context Protocol) Server, the agent gains the ability to query, analyze, and act on live Bitbucket data in real time. This integration bridges Cline's in-IDE agent framework with the governed enterprise connectivity of CData Connect AI, ensuring all data access runs securely against authorized sources without manual data movement.

This article outlines the steps to configure Bitbucket connectivity in Connect AI, generate the required personal access token, register the Connect AI MCP Server in Cline, and verify that the agent can successfully interact with live Bitbucket data from within the IDE.

Step 1: Configure Bitbucket connectivity for Cline

Connectivity to Bitbucket from Cline is made possible through CData Connect AI's Remote MCP Server. To interact with Bitbucket data from Cline, 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 and update user-based permissions

Add a Personal Access Token

A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Cline. It is best practice to create a separate PAT for each integration to maintain granular access control.

1. Click the gear icon () at the top right of the Connect AI app to open Settings
2. On the Settings page, go to the Access Tokens section and click Create PAT
3. Give the PAT a descriptive name and click Create

4. Copy the token when displayed and store it securely. It will not be shown again

With the Bitbucket connection configured and a PAT generated, Cline can now connect to Bitbucket data through the CData Connect Ai.

Step 2: Install and set up Cline

Cline is distributed as an IDE extension and can be installed in environments such as VS Code or Cursor. In this example, Cursor is used, but the steps are identical for supported IDEs.

1. Open Cursor and install the Cline extension from the Extensions Marketplace
2. Complete the initial Cline setup flow, including model selection and permission prompts
3. After setup is complete, the Cline agent panel opens automatically inside the IDE

Step 3: Add the Connect AI Remote MCP Server

Once Cline is running, add the CData Connect AI Remote MCP Server so the agent can access live Bitbucket data through Connect AI.

1. In the Cline panel, click MCP Servers
2. Open Remote Servers and click Edit Configuration
3. This opens a JSON configuration file. Paste the configuration below

   {
     "mcpServers": {
       "mcp": {
         "url": "https://mcp.cloud.cdata.com/mcp",
         "type": "streamableHttp",
         "headers": {
           "Authorization": "Basic your_email:your_PAT"
         },
         "disabled": false,
         "autoApprove": []
       }
     }
   }
   

   Note: Cline will use Basic authentication with Connect AI. Combine your Connect AI user email and the PAT you created earlier. For example, [email protected]:ABC123...XYZ789 and add the value for the Authorization header like, Basic [email protected]:ABC123...XYZ789.

   
4. Save the file and return to the MCP Servers screen to confirm the server is listed and enabled

Step 4: Query live data from Cline

With the MCP server registered, Cline can now interact with live data sources exposed by Connect AI.

1. Click the icon in the Cline panel to start a New Task/Chat
2. At the bottom of the chat window, confirm that the configured MCP server is selected
3. Start interacting with the agent by entering prompts such as:
   • List connections
   • Show schemas for a catalog
   • Query recent records from Bitbucket data
   

Cline is now fully configured to access and query live Bitbucket data through the CData Connect AI Remote MCP Server, enabling real-time, data-driven workflows directly from your IDE.

Get CData Connect AI

To access hundreds of SaaS, Big Data, and NoSQL sources through secure, AI-ready interfaces, try CData Connect AI today.