Integrate Cursor with Live Bitbucket Data via CData Connect AI

Yazhini G
Yazhini G
Technical Marketing Engineer
Leverage the CData Connect AI Remote MCP Server to enable Cursor to securely access and act on live Bitbucket data from within the editor.

Cursor is an AI-powered code editor that embeds conversational and agent-style assistance alongside your development workflow. By extending Cursor with MCP (Model Context Protocol) tools, you can give its AI agents secure access to external systems such as APIs and databases.

Integrating Cursor with CData Connect AI via the built-in MCP server allows the editor's AI to query, analyze, and act on live Bitbucket data without copying data into the IDE. The result is a development experience where you can chat with your governed enterprise data directly from Cursor.

This article outlines how to configure Bitbucket connectivity in Connect AI, generate the required access token, register Connect AI's MCP Server in Cursor, and then use the AI chat pane to explore live Bitbucket data.

Step 1: Configure Bitbucket connectivity for Cursor

Connectivity to Bitbucket from Cursor is made possible through CData Connect AI's Remote MCP Server. To interact with Bitbucket data from Cursor, 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. Adding a connection in Connect AI
  3. Select Bitbucket from the Add Connection panel
  4. Selecting data source
  5. 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.
    Configuring a connection (Salesforce is shown)
  6. Click Save & Test
  7. Navigate to the Permissions tab and update user-based permissions
  8. Updating permissions

Add a Personal Access Token

A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Cursor. 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. Creating a new PAT
  5. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use

With the Bitbucket connection configured and a PAT generated, Cursor can now connect to Bitbucket data through Connect AI.

Step 2: Configure Connect AI in Cursor

Next, configure Cursor to use Connect AI. Cursor reads MCP configuration from an mcp.json file in the user configuration directory and exposes the registered servers under the Tools & MCP settings. Once configured, Cursor's AI chat can call the tools exposed by CData Connect AI.

  1. Download the Cursor desktop application and complete the sign-up flow for your account
  2. From the top menu, click Settings to open the settings panel Opening Cursor Settings
  3. In the left navigation, open the Tools & MCP tab and click Add Custom MCP Tools & MCP tab with Add Custom MCP
  4. Cursor opens an mcp.json file in the editor
  5. Add the following configuration. Make sure to base64-encode your email:PAT before inserting into the header:
    
    {
      "mcpServers": {
        "cdata-mcp": {
          "url": "https://mcp.cloud.cdata.com/mcp",
          "headers": {
            "Authorization": "Basic your_base64_encoded_email_PAT"
          }
        }
      }
    }
    		
    Configuring mcp.json with Connect AI
  6. Save the file
  7. Return to Settings and then select Tools & MCP. You can now see cdata-mcp enabled with an active indicator Connect AI enabled

Step 3: Chat with CData Connect AI from Cursor

  1. From the top bar, click Toggle AI Pane to open the chat window Opening the AI pane
  2. Test the connection by entering "List connections"
  3. You can also run queries like "Query Bitbucket data and list the high priority accounts" Querying Bitbucket data from Connect AI

Cursor is now fully integrated with the CData Connect AI MCP Server and can act on live Bitbucket data directly from the editor.

Get CData Connect AI

To access hundreds of SaaS, Big Data, and NoSQL sources directly from your development tools, try CData Connect AI today!

Ready to get started?

Learn more about CData Connect AI or sign up for free trial access:

Free Trial