Interact with Live HubDB Data in Warp via CData Connect AI

Warp is an agentic development environment that combines a modern terminal with an AI agent. It supports large language model (LLM) interactions and Model Context Protocol (MCP) server integrations, so the agent can reach live external data sources without leaving the terminal.

By integrating Warp with CData Connect AI through its built-in MCP Server, the Warp Agent gets governed, real-time access to live HubDB data. You can explore HubDB data, ask questions in plain language, and work with your records without writing custom integration code.

This article walks through configuring HubDB connectivity in Connect AI, configuring the CData MCP Server in Warp, and interacting with live HubDB data from the Warp Agent.

Step 1: Configure HubDB connectivity for Warp

Connectivity to HubDB from Warp is made possible through Connect AI's Remote MCP Server. To interact with HubDB data from Warp, start by creating and configuring a HubDB connection in Connect AI.

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

2. Select HubDB from the Add Connection panel

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

   There are two authentication methods available for connecting to HubDB data source: OAuth Authentication with a public HubSpot application and authentication with a Private application token.

   Using a Custom OAuth App

   AuthScheme must be set to "OAuth" in all OAuth flows. Be sure to review the Help documentation for the required connection properties for you specific authentication needs (desktop applications, web applications, and headless machines).

   Follow the steps below to register an application and obtain the OAuth client credentials:

   1. Log into your HubSpot app developer account.
      • Note that it must be an app developer account. Standard HubSpot accounts cannot create public apps.
   2. On the developer account home page, click the Apps tab.
   3. Click Create app.
   4. On the App info tab, enter and optionally modify values that are displayed to users when they connect. These values include the public application name, application logo, and a description of the application.
   5. On the Auth tab, supply a callback URL in the "Redirect URLs" box.
      • If you're creating a desktop application, set this to a locally accessible URL like http://localhost:33333.
      • If you are creating a Web application, set this to a trusted URL where you want users to be redirected to when they authorize your application.
   6. Click Create App. HubSpot then generates the application, along with its associated credentials.
   7. On the Auth tab, note the Client ID and Client secret. You will use these later to configure the driver.

   8. Under Scopes, select any scopes you need for your application's intended functionality.

      A minimum of the following scopes is required to access tables:

      • hubdb
      • oauth
      • crm.objects.owners.read
   9. Click Save changes.
   10. Install the application into a production portal with access to the features that are required by the integration.
       • Under "Install URL (OAuth)", click Copy full URL to copy the installation URL for your application.
       • Navigate to the copied link in your browser. Select a standard account in which to install the application.
       • Click Connect app. You can close the resulting tab.

   Using a Private App

   To connect using a HubSpot private application token, set the AuthScheme property to "PrivateApp."

   You can generate a private application token by following the steps below:

   1. In your HubDB account, click the settings icon (the gear) in the main navigation bar.
   2. In the left sidebar menu, navigate to Integrations > Private Apps.
   3. Click Create private app.
   4. On the Basic Info tab, configure the details of your application (name, logo, and description).
   5. On the Scopes tab, select Read or Write for each scope you want your private application to be able to access.
   6. A minimum of hubdb and crm.objects.owners.read is required to access tables.
   7. After you are done configuring your application, click Create app in the top right.
   8. Review the info about your application's access token, click Continue creating, and then Show token.
   9. Click Copy to copy the private application token.

   To connect, set PrivateAppToken to the private application token you retrieved.

   
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 Warp. 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 HubDB connection configured and a PAT generated, Warp can now connect to HubDB data through Connect AI.

Step 2: Configure Connect AI in Warp

Enable the Warp Agent, configure an LLM provider, and the Connect AI MCP endpoint in Warp so the agent can discover and call live data tools.

1. Download and install Warp, and then sign up or log in to your Warp account
2. Click the Tabs panel icon at the top left of the window, or press Ctrl + Shift + B
3. Click Settings, expand Agents, select Warp Agent, and toggle Warp Agent on

Configure an LLM provider

The Warp Agent needs an LLM provider to interpret your prompts and decide which MCP tools to call. Add an API key for your preferred provider.

1. On the same Warp Agent page, scroll down to the Custom Inference section
2. Enter the API key for the LLM provider of your choice (e.g., OpenAI, Anthropic, or Google)

Add the Connect AI MCP Server

1. Under Agents, click MCP servers, and then click Add
2. In the Add New MCP Server editor, paste the following JSON configuration:

   {
     "mcpServers": {
       "CData_Connect_AI": {
         "url": "https://mcp.cloud.cdata.com/mcp",
         "headers": {
           "Authorization": "Basic your_base64_encoded_email_PAT"
         }
       }
     }
   }

   Note: Combine your Connect AI email and PAT in the format email:PAT, Base64 encode the combined string, and prefix it with Basic. For example, given [email protected]:ABC123...XYZ, the header value becomes something like: Basic dXNlckBteWRvbWFpbjphSzkvbVB4Mi9Rcjd2TjQ...

   
3. Click Save to add the MCP server
4. Under My MCPs, confirm that CData_Connect_AI appears with the toggle enabled and the tools available

With the MCP server and an LLM provider configured, the Warp Agent is ready to interact with live HubDB data through Connect AI.

Step 3: Interact with live HubDB data from the Warp Agent

Use natural language prompts in the Warp Agent to explore live HubDB data.

1. Click the icon in the left navigation bar and select Agent
2. Enter a prompt to interact with your data, for example:
   • List the sources available in my CData_Connect_AI mcp connection
   • Show me what I can explore in HubDB
   • Fetch the five most recent records from HubDB data
   
3. The agent calls the Connect AI MCP Server and returns live results from HubDB data

Your Warp Agent now calls the Connect AI MCP Server to interact with live HubDB data through remote MCP tools, all from the terminal.

Get CData Connect AI

To interact with hundreds of SaaS and enterprise data sources directly from your AI agents and cloud applications, try CData Connect AI. Download a free 14-day trial of CData Connect AI, and our Support Team is available to answer any questions.