Interact with Live AlloyDB Data in Warp via CData Connect AI

Yazhini G
Yazhini G
Technical Marketing Engineer
Use the CData Connect AI Remote MCP Server to let Warp securely interact with live AlloyDB data directly from the terminal and agent workflow.

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 AlloyDB data. You can explore AlloyDB data, ask questions in plain language, and work with your records without writing custom integration code.

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

Step 1: Configure AlloyDB connectivity for Warp

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

  1. Log into Connect AI, click Sources, and then click Add Connection
  2. Adding a connection in Connect AI
  3. Select AlloyDB from the Add Connection panel
  4. Selecting data source
  5. Enter the necessary authentication properties to connect to AlloyDB.

    The following connection properties are usually required in order to connect to AlloyDB.

    • Server: The host name or IP of the server hosting the AlloyDB database.
    • User: The user which will be used to authenticate with the AlloyDB server.
    • Password: The password which will be used to authenticate with the AlloyDB server.

    You can also optionally set the following:

    • Database: The database to connect to when connecting to the AlloyDB Server. If this is not set, the user's default database will be used.
    • Port: The port of the server hosting the AlloyDB database. This property is set to 5432 by default.

    Authenticating with Standard Authentication

    Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.

    No further action is required to leverage Standard Authentication to connect.

    Authenticating with pg_hba.conf Auth Schemes

    There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.

    Find instructions about authentication setup on the AlloyDB Server here.

    Authenticating with MD5 Authentication

    This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.

    Authenticating with SASL Authentication

    This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.

    Authenticating with Kerberos

    The authentication with Kerberos is initiated by AlloyDB Server when the ∏ is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos. 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 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. Creating a new PAT
  5. Copy the token when displayed and store it securely. It will not be shown again

With the AlloyDB connection configured and a PAT generated, Warp can now connect to AlloyDB 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 Opening the Tabs panel in Warp
  3. Click Settings, expand Agents, select Warp Agent, and toggle Warp Agent on Enabling the Warp Agent in Settings

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) Adding an LLM API key under Custom Inference

Add the Connect AI MCP Server

  1. Under Agents, click MCP servers, and then click Add Adding a new MCP server in Warp
  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...

    Configuring Connect AI MCP Server
  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 Verifying the Connect AI MCP Server is enabled in Warp

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

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

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

  1. Click the icon in the left navigation bar and select Agent Starting a new agent conversation in Warp
  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 AlloyDB
    • Fetch the five most recent records from AlloyDB data
    Entering a prompt in the Warp Agent
  3. The agent calls the Connect AI MCP Server and returns live results from AlloyDB data Interacting with live data from the Warp Agent

Your Warp Agent now calls the Connect AI MCP Server to interact with live AlloyDB 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.

Ready to get started?

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

Free Trial