Integrate OpenCode with Live SQL Server Data via CData Connect AI

Yazhini G
Yazhini G
Technical Marketing Engineer
Use the CData Connect AI Remote MCP Server to enable OpenCode to securely access and query live SQL Server data from within your AI coding agent.

OpenCode is an open source AI coding agent that connects to a wide range of LLM providers. It supports the model context protocol (MCP), allowing you to configure local or remote MCP servers in its configuration files to add external tools and data sources and give the agent access to live data.

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

This article explains how to configure SQL Server connectivity in Connect AI, generate the required personal access token, install OpenCode, add the Connect AI MCP Server in the project configuration file, configure an LLM provider, and verify the integration by querying live SQL Server data from OpenCode.

Step 1: Configure SQL Server connectivity for OpenCode

Connectivity to SQL Server from OpenCode is made possible through Connect AI's Remote MCP Server. To interact with SQL Server data from OpenCode, start by creating and configuring a SQL Server 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 SQL Server from the Add Connection panel
  4. Selecting data source
  5. Enter the necessary authentication properties to connect to SQL Server.

    Connecting to Microsoft SQL Server

    Connect to Microsoft SQL Server using the following properties:

    • Server: The name of the server running SQL Server.
    • User: The username provided for authentication with SQL Server.
    • Password: The password associated with the authenticating user.
    • Database: The name of the SQL Server database.

    Connecting to Azure SQL Server and Azure Data Warehouse

    You can authenticate to Azure SQL Server or Azure Data Warehouse by setting the following connection properties:

    • Server: The server running Azure. You can find this by logging into the Azure portal and navigating to "SQL databases" (or "SQL data warehouses") -> "Select your database" -> "Overview" -> "Server name."
    • User: The name of the user authenticating to Azure.
    • Password: The password associated with the authenticating user.
    • Database: The name of the database, as seen in the Azure portal on the SQL databases (or SQL warehouses) page.

    SSH Connectivity for SQL Server

    You can use SSH (Secure Shell) to authenticate with SQL Server, whether the instance is hosted on-premises or in supported cloud environments. SSH authentication ensures that access is encrypted (as compared to direct network connections).

    SSH Connections to SQL Server in Password Auth Mode

    To connect to SQL Server via SSH in Password Auth mode, set the following connection properties:

    • User: SQL Server User name
    • Password: SQL Server Password
    • Database: SQL Server database name
    • Server: SQL Server Server name
    • Port: SQL Server port number like 3306
    • UserSSH: "true"
    • SSHAuthMode: "Password"
    • SSHPort: SSH Port number
    • SSHServer: SSH Server name
    • SSHUser: SSH User name
    • SSHPassword: SSH Password

    SSH Connections to SQL Server in Public Key Auth Mode

    To connect to SQL Server via SSH in Password Auth mode, set the following connection properties:

    • User: SQL Server User name
    • Password: SQL Server Password
    • Database: SQL Server database name
    • Server: SQL Server Server name
    • Port: SQL Server port number like 3306
    • UserSSH: "true"
    • SSHAuthMode: "Public_Key"
    • SSHPort: SSH Port number
    • SSHServer: SSH Server name
    • SSHUser: SSH User name
    • SSHClientCret: the path for the public key certificate file
    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 OpenCode. 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 SQL Server connection configured and a PAT generated, OpenCode can now connect to SQL Server data through Connect AI.

Step 2: Install OpenCode and configure the Connect AI MCP Server

Next, install OpenCode, add the Connect AI Remote MCP Server in your project configuration file, and configure an LLM provider so the agent can discover and call live data tools through Connect AI.

  1. Download and install OpenCode by following the official installation guide
  2. Create a new folder for your project, or open an existing project directory
  3. In the root of that directory, create a file named opencode.json and paste the following configuration:
    {
      "$schema": "https://opencode.ai/config.json",
      "mcp": {
        "cdata-connect-ai": {
          "type": "remote",
          "url": "https://mcp.cloud.cdata.com/mcp",
          "enabled": true,
          "oauth": false,
          "headers": {
            "Authorization": "Basic your_base64_encoded_email_PAT"
          },
          "timeout": 30000
        }
      }
    }
    		

    Note: OpenCode 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==

  4. Open the project directory in OpenCode. Select the project from the project dropdown, or click Add project to point OpenCode at the folder that contains opencode.json Opening the project directory in OpenCode
  5. Configure an LLM provider so the agent can interpret prompts and call MCP tools. Open the model selector (Ctrl + '), choose a provider such as OpenAI, Anthropic, or Google, and enter your API key Selecting an LLM provider and model in OpenCode

With the MCP server added in opencode.json and an LLM provider configured, OpenCode is ready to query live SQL Server data through Connect AI.

Step 3: Query live SQL Server data from OpenCode

With the integration complete, use OpenCode to interact with live SQL Server data through natural language prompts handled by the configured LLM.

  1. In a new session, type a prompt in the chat input, for example:
    • Use the cdata-connect-ai tools to list all available catalogs
    • Show the available schemas and tables for SQL Server
    • Query the top 5 records from a table in SQL Server
  2. OpenCode calls the Connect AI MCP Server and returns live results from SQL Server data Querying live data from OpenCode

At this point, OpenCode communicates with the Connect AI MCP Server and retrieves live SQL Server data through remote MCP tools directly from your AI coding agent.

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.

Ready to get started?

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

Free Trial