Query Live Act CRM Data in Zed Editor via CData Connect AI

Zed is a high-performance, open-source code editor built for speed and collaboration. Its built-in AI agent panel supports LLM-powered interactions and MCP (Model Context Protocol) tool integrations, enabling developers to access live external data sources directly within the editor.

By integrating Zed with CData Connect AI through the built-in MCP (Model Context Protocol) Server, the Zed AI agent gains governed, real-time access to live Act CRM data. This enables developers to query schemas, retrieve records, and explore Act CRM data without leaving the editor or writing custom integration code.

This article explains how to configure Act CRM connectivity in Connect AI, register the CData MCP Server in Zed, and query live Act CRM data from the Zed agent panel.

Step 1: Configure Act CRM connectivity for Zed

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

1. Log into Connect AI, click Sources, and then click Add Connection
👁 Adding a connection in Connect AI

2. Select Act CRM from the Add Connection panel
👁 Selecting data source

3. Enter the necessary authentication properties to connect to Act CRM.

   The and properties, under the Authentication section, must be set to valid Act! user credentials. In addition to the authentication values, see the following:

   • Connecting to Act! Premium

     In addition to the authentication values, the to Act! is also required; for example https://eup1-iis-04.eu.hosted.act.com/.

     Additionally, you must specify the you will connect to. This is found by going to the About Act! Premium menu of your account, at the top right of the page, in the ? menu. Use the Database Name in the window that appears.

   • Connecting to Act! Premium Cloud

     To connect to your Act! Premium Cloud account, you also need to specify the property. This property is found in the URL address of the Cloud account; for example https://eup1-iis-04.eu.hosted.act.com/ActCloudName/.

   Note that retrieving ActCRM metadata can be expensive. It is advised that you set the property to store the metadata locally.

   👁 Configuring a connection (Salesforce is shown)
   
4. Click Save & Test
5. Navigate to the Permissions tab and update user-based permissions
👁 Updating permissions

Add a Personal Access Token

A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Zed. 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
👁 Creating a new PAT

4. Copy the token when displayed and store it securely. It will not be shown again

With the Act CRM connection configured and a PAT generated, Zed can now connect to Act CRM data through Connect AI.

Step 2: Configure Connect AI in Zed

Now, let's register the CData Connect AI MCP endpoint in Zed so that the built-in AI agent can discover and call live data tools.

1. Download and install Zed
2. Open the agent panel by pressing Ctrl + Shift + /, or by clicking the sparkle icon at the bottom right of the editor
3. In the agent panel, click the ... (toggle agent menu) and select Add Custom Server from the dropdown 👁 Opening the agent menu to add a custom MCP server
   
4. Select the Configure Remote option to configure CData's MCP
5. An Add MCP Server dialog opens displaying a remote server configuration template. Replace the placeholder content with the following JSON:

   {
    "cdata": {
    "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...

   👁 Pasting the CData Connect AI MCP Server configuration
   
6. Click Add Server or press Ctrl + Enter to register the MCP server

Configure an LLM provider

Zed requires at least one LLM provider to power the agent's reasoning. Configure a provider so the agent can interpret queries and call MCP tools through Connect AI.

1. Click the ... (toggle agent menu) and select Settings
2. Under LLM Providers, expand your preferred provider (e.g., Anthropic, OpenAI, Google AI) and enter your API key
3. Under Model Context Protocol (MCP) Servers, confirm that cdata appears with a green dot and the toggle is enabled 👁 Verifying the CData MCP Server is enabled in Zed Settings
   

With the MCP server registered and an LLM provider configured, the Zed agent is ready to query live Act CRM data through Connect AI.

Step 3: Query live Act CRM data from the Zed agent

With the integration complete, use the Zed agent panel to explore and interact with live Act CRM data through natural language prompts.

1. Open the agent panel using Ctrl + Shift + / and start a new thread
2. Enter a prompt to interact with your data, for example:
   • List all catalogs in my cdata connection
   • Show the available schemas and tables for Act CRM
   • Query the top 5 records from a table in Act CRM data
3. The agent calls the CData Connect AI MCP Server and returns live results from Act CRM data 👁 Querying live data from the Zed agent panel
   

At this point, your Zed agent communicates with the CData Connect AI MCP Server and retrieves live Act CRM data through remote MCP tools directly from the editor.

Get CData Connect AI

To access hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today! Start a free 14-day trial of CData Connect AI today, and as always, our world-class Support Team is available to assist you with any questions you may have.