Integrate Goose with Live SingleStore 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 SingleStore data. You can list catalogs, explore schemas, and query records from SingleStore data using natural language prompts, with all data access running securely against authorized sources.

This article explains how to configure SingleStore 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 SingleStore data from the Goose chat.

Step 1: Configure SingleStore connectivity for Goose

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

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

2. Select SingleStore from the Add Connection panel

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

   The following connection properties are required in order to connect to data.

   • Server: The host name or IP of the server hosting the SingleStore database.
   • Port: The port of the server hosting the SingleStore database.
   • Database (Optional): The default database to connect to when connecting to the SingleStore Server. If this is not set, tables from all databases will be returned.

   Connect Using Standard Authentication

   To authenticate using standard authentication, set the following:

   • User: The user which will be used to authenticate with the SingleStore server.
   • Password: The password which will be used to authenticate with the SingleStore server.

   Connect Using Integrated Security

   As an alternative to providing the standard username and password, you can set IntegratedSecurity to True to authenticate trusted users to the server via Windows Authentication.

   Connect Using SSL Authentication

   You can leverage SSL authentication to connect to SingleStore data via a secure session. Configure the following connection properties to connect to data:

   • SSLClientCert: Set this to the name of the certificate store for the client certificate. Used in the case of 2-way SSL, where truststore and keystore are kept on both the client and server machines.
   • SSLClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
   • SSLClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
   • SSLClientCertType: The certificate type of the client store.
   • SSLServerCert: The certificate to be accepted from the server.

   Connect Using SSH Authentication

   Using SSH, you can securely login to a remote machine. To access SingleStore data via SSH, configure the following connection properties:

   • SSHClientCert: Set this to the name of the certificate store for the client certificate.
   • SSHClientCertPassword: If a client certificate store is password-protected, set this value to the store's password.
   • SSHClientCertSubject: The subject of the TLS/SSL client certificate. Used to locate the certificate in the store.
   • SSHClientCertType: The certificate type of the client store.
   • SSHPassword: The password that you use to authenticate with the SSH server.
   • SSHPort: The port used for SSH operations.
   • SSHServer: The SSH authentication server you are trying to authenticate against.
   • SSHServerFingerPrint: The SSH Server fingerprint used for verification of the host you are connecting to.
   • SSHUser: Set this to the username that you use to authenticate with the SSH server.
   
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 SingleStore connection configured and a PAT generated, Goose can now connect to SingleStore 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 SingleStore data through Connect AI.

Step 3: Query live SingleStore data from Goose

With the integration complete, use the Goose chat to interact with live SingleStore 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 SingleStore
   • Query the top 5 records from a table in SingleStore data
2. Goose calls the Connect AI MCP Server and returns live results from SingleStore data

At this point, your Goose agent communicates with the Connect AI MCP Server and retrieves live SingleStore 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.