Integrate Goose with Live HubDB Data via CData Connect AI

Goose is an open source AI agent that runs locally on your machine and works with a wide range of LLM providers. It supports the model context protocol (MCP) through its extensions framework, so you can add external tools and data sources and give the agent access to live systems beyond the model's training data.

By integrating Goose with CData Connect AI through the built-in MCP Server, Goose gains governed, real-time access to live HubDB data. You can list catalogs, explore schemas, and query records from HubDB data using natural language prompts, with all data access running securely against authorized sources.

This article explains how to configure HubDB connectivity in Connect AI, generate the required personal access token, install and set up Goose, add the Connect AI MCP Server as a custom extension, and verify the integration by querying live HubDB data from the Goose chat.

Step 1: Configure HubDB connectivity for Goose

Connectivity to HubDB from Goose is made possible through Connect AI's Remote MCP Server. To interact with HubDB data from Goose, 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 Goose. 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, Goose can now connect to HubDB data through Connect AI.

Step 2: Install and set up Goose

Next, install Goose, choose an LLM provider, and add the Connect AI Remote MCP Server as a custom extension so the agent can discover and call live data tools through Connect AI.

1. Download and install Goose by following the official installation guide, then launch the application
2. On the Welcome to goose screen, choose an AI provider. Select Use Free/Local Providers to run a local model, or Connect to a Provider to configure a provider such as OpenAI, Anthropic, or Google, and enter the required API key
3. In the left navigation, click Extensions, then click + Add custom extension
4. In the extension dialog, configure the server with the following values:
   • Extension Name: CData MCP, or any name of your choice
   • Type: Streamable HTTP
   • Endpoint: https://mcp.cloud.cdata.com/mcp
5. Under Request Headers, add the following two headers and click + Add after each pair:
   • Authorization: Basic your_base64_encoded_email_PAT
   • Content-Type: application/json

   Note: Goose will use Basic authentication with Connect AI. Combine your Connect AI user email and the PAT you created earlier in the format email:PAT, base64 encode the combined string, and prefix it with Basic. For example, given [email protected]:ABC123...XYZ789, the Authorization header value becomes something like: Basic dXNlckBkb21haW4uY29tOkFCQzEyMy4uLlhZWjc4OQ==

   
6. Click Save to save the configuration
7. Return to the chat, click the extensions icon at the bottom of the chat input, and confirm that the configured MCP is enabled

With the MCP server added and an LLM provider configured, Goose is ready to query live HubDB data through Connect AI.

Step 3: Query live HubDB data from Goose

With the integration complete, use the Goose chat to interact with live HubDB data through natural language prompts handled by the configured LLM.

1. With the CData MCP extension enabled, type a prompt in the chat, for example:
   • List catalogs from my CData MCP
   • Show the available schemas and tables for HubDB
   • Query the top 5 records from a table in HubDB data
2. Goose calls the Connect AI MCP Server and returns live results from HubDB data

At this point, your Goose agent communicates with the Connect AI MCP Server and retrieves live HubDB data through remote MCP tools directly from the chat.

Get CData Connect AI

To access hundreds of SaaS, big data, and NoSQL sources directly from your cloud applications, try CData Connect AI today. Download a free 14-day trial of CData Connect AI, and our Support Team is available to help with any questions you have.