Devart MCP Server for Zoho CRM (ADO.NET)

com.devart由 devart.com 發布v1.1.0更新於 Nov 3, 2026

Schema-aware read/write access to Zoho CRM through Devart dotConnect ADO.NET data provider.

概覽

AI 產生的概覽

本機 MCP 伺服器,透過 Devart dotConnect ADO.NET 或 ODBC 驅動程式,讓 AI 助理以感知結構描述的讀寫方式存取 Zoho CRM 資料。

可以做什麼
  • 以自然語言查詢 Zoho CRM 記錄,請求會轉為結構化查詢並回傳結構化結果
  • 讀取銷售漏斗、商機、潛在客戶、聯絡人、活動、預測與配額資料,用於分析與報表
  • 對 Zoho CRM 資料具備寫入能力,因為存取方式被描述為讀寫
  • 可依具名連線選擇 ADO.NET(dotConnect)或 ODBC 連線方式
適用情境
適合以 Zoho CRM 為主要客戶資料來源的團隊,讓助理直接查詢商機、潛在客戶、活動、預測與留存狀況,不必手動匯出。偏向銷售營運與報表情境,而非一般網頁或檔案工作。
執行需求
在 Windows 上以 .NET 8 本機程序執行;ADO.NET 版本會透過 NuGet 自動取得 dotConnect for Zoho CRM 套件,ODBC 版本則需手動安裝 Devart ODBC Driver for Zoho CRM。需在執行檔旁的 mcpserver.json 設定具名連線,清單宣告需要必填的連線字串密鑰 DEVART_MCP_ZOHOCRM_CONNECTION。另需 Zoho CRM 帳號(OAuth 或使用者憑證)與 Devart 授權金鑰,並在 AI 用戶端指向該執行檔與連線名稱。
安裝前請注意
連線字串包含 Zoho CRM 憑證與 Devart 授權金鑰,應妥善保管設定檔。存取為讀寫,助理可能修改 CRM 記錄而不只是讀取。所需的 Devart 驅動程式為付費產品,僅提供 30 天試用,長期使用需付費。查詢與結果會經由 Devart 連線驅動程式傳輸,選用的 HTTP 傳輸還會開放本機連接埠。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Devart MCP Server for Zoho CRM (ADO.NET),將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

[Devart MCP Server for Zoho CRM]

Version 1.1.0

What's new · Changelog

Devart MCP Server for Zoho CRM

Devart MCP Server for Zoho CRM enables AI clients to interact with your data through a secure server running in your environment. It turns a regular AI chat into a practical way to work with real-world business data — and it is faster than conventional export or manual querying.

Key benefits

Devart MCP Server for Zoho CRM allows you to:

  • Work with data intuitively through natural language.
  • Retrieve the required data for analysis within minutes.
  • Report on your data faster with AI-powered assistance.
  • Minimize manual data handling and integration maintenance.

How it works

Devart MCP Server for Zoho CRM helps AI clients communicate directly with Zoho CRM databases using natural-language prompts. It translates AI requests into structured queries, executes them through Devart connectivity drivers, and returns clean, structured results for seamless AI-powered data access.

[Devart MCP Server architecture]

Quick start

To get started with Devart MCP Server for Zoho CRM:

1. Download and install Devart ODBC Driver for Zoho CRM.

2. Download and install Devart MCP Server for Zoho CRM.

3. In Devart MCP Server for Zoho CRM, configure your data connection and integration settings.

[Devart MCP Server configuration]

4. Run your first natural-language query.

[Need an MCP Server for multiple data sources?]

Manual installation and configuration

Prerequisites

Before building and running Devart MCP Server for Zoho CRM, ensure the following components are installed:

  • .NET 8 SDK
  • ADO.NET connection — Devart.AI.McpServer.AdoNet.ZohoCrm.csproj Devart dotConnect for Zoho CRM (installed automatically via NuGet during build)
  • ODBC connection — Devart.AI.McpServer.Odbc.ZohoCrm.csproj Devart ODBC Driver for Zoho CRM (requires manual download and installation)

Step 1: Clone the repository

Clone the project repository and navigate to the project directory:

1. Open Command Prompt.

2. Enter the following command:

cmd
git clone https://github.com/devart-ai-connectivity/devart-mcp-server-zoho-crm.gitcd devart-mcp-server-zoho-crm

Step 2: Build the MCP Server from source

You can build Devart MCP Server for Zoho CRM from source using either of the supported database connectivity technologies: ADO.NET or ODBC.

  • To build the MCP server with ADO.NET, run the following command:
cmd
dotnet publish Devart.AI.McpServer.AdoNet/Devart.AI.McpServer.AdoNet.ZohoCrm/Devart.AI.McpServer.AdoNet.ZohoCrm.csproj -c ReleaseZohoCrm /p:TargetFramework=net8.0

The Devart dotConnect for Zoho CRM NuGet package is downloaded and restored automatically.

  • To build the MCP server with ODBC, select the command based on the bitness of your data source.

For 64-bit data source, run the following command:

cmd
dotnet publish Devart.AI.McpServer.Odbc/Devart.AI.McpServer.Odbc.ZohoCrm/Devart.AI.McpServer.Odbc.ZohoCrm.csproj -c ReleaseZohoCrm -r "win-x64" /p:TargetFramework=net8.0

For 32-bit data source, run the following command:

cmd
dotnet publish Devart.AI.McpServer.Odbc/Devart.AI.McpServer.Odbc.ZohoCrm/Devart.AI.McpServer.Odbc.ZohoCrm.csproj -c ReleaseZohoCrm -r "win-x86" /p:TargetFramework=net8.0

Note

The target platform must match the bitness of your ODBC data source.

Step 3: Configure the database connection for the MCP Server

1. Create an mcpserver.json configuration file in the directory containing the built MCP Server executable.

2. In the file, configure the database connection.

  • Configure a connection with ADO.NET.

Add the following configuration to the mcpserver.json file:

json
{  "Connections": [    {      "Name": "my_zohocrm",      "ConnectionString": "Authentication Type=OAuthInteractive;Domain=crm.zoho.com;License Key=your_license_key;",      "ProtocolType": "stdio"    }  ]}
  • Configure a connection with ODBC.

Add the following configuration to the mcpserver.json file:

json
{  "Connections": [    {      "Name": "my_zohocrm",      "DsnName": "your_dsn_name",      "ProtocolType": "stdio"    }  ]}
  • Configure a connection with ODBC using a connection string.

Add the following configuration to the mcpserver.json file:

json
{  "Connections": [    {      "Name": "my_zohocrm",      "ConnectionString": "Driver={Devart ODBC Driver for Zoho CRM};Server=localhost;User ID=zohocrm;Password=your_password;Database=your_database;",      "ProtocolType": "stdio"    }  ]}

where:

  • Name — The connection name.

  • ConnectionString (applies to ADO.NET) — A database-specific connection string used to establish a connection to the target database.

  • DsnName (applies to ODBC) — The name of your data source.

  • ProtocolType — A transport protocol. The possible options are: stdio or http.

  • HttpPort (required if ProtocolType is set to http) — The port number for the http protocol.

Step 4: Run the MCP server

After you configure the MCP Server, you can start it.

Note

This step is required only when ProtocolType is configured as http. If you use the stdio transport protocol, your AI client starts the server automatically.

  • To start the server with ADO.NET, run the following command:
cmd
Devart.AI.McpServer.AdoNet.ZohoCrm.exe run my_zohocrm
  • To start the server with ODBC, run the following command:
cmd
Devart.AI.McpServer.Odbc.ZohoCrm.exe run my_zohocrm

where my_zohocrm is the name of the ODBC connection.

Step 5: Integrate with Claude Desktop

1. Open claude_desktop_config.json, the Claude configuration file.

Tip

If you can't locate the configuration file, it may not exist yet. To create it, open Claude Desktop and navigate to File > Settings > Developer, then click Edit Config. The folder with the claude_desktop_config.json file opens.

2. Add one of the following objects, depending on the transport protocol used by MCP Server:

  • STDIO
json
{  "mcpServers": {    "devart": {      "command": "C:\\path\\to\\Devart.AI.McpServer.AdoNet.ZohoCrm.exe",      "args": [        "run",        "my_zohocrm"      ]    }  }}

where:

  • devart is the connector name that will appear in Claude Desktop.

  • C:\\path\\to\\Devart.AI.McpServer.AdoNet.ZohoCrm.exe is the path to the executable file. For an ODBC connection, use Devart.AI.McpServer.Odbc.ZohoCrm.exe.

  • my_zohocrm is the connection name specified in the mcpserver.json configuration file.

  • HTTP

    json
      "mcpServers": {    "devart": {      "command": "npx",      "args": [        "-y",        "mcp-remote",        "http://localhost:5000/sse"      ]    }  }

    where:

    • devart is the connector name that will appear in Claude Desktop.
    • 5000 is the MCP Server listening port.

3. Save the file.

4. Restart Claude Desktop.

Devart MCP Server for Zoho CRM is now integrated with Claude, and devart appears in the Claude Desktop app in Customize > Connectors.

You can also integrate Devart MCP Server for Zoho CRM with other AI clients such as Cline, Codex, Cursor, Visual Studio Code, Windsurf, Zed.

Supported clients

Devart MCP Server for Zoho CRM supports integration with the following AI clients:

  • Claude Desktop
  • Visual Studio Code
  • Cursor
  • Codex
  • Windsurf
  • Cline
  • Zed
  • ...and other MCP-compatible AI clients

Typical use cases

Devart MCP Server for Zoho CRM is a practical fit for teams working with Zoho CRM as their primary data source.

  • Sales pipeline and deal tracking
    Let sales managers and reps query deal stages, expected close dates, deal values, and pipeline distributions directly from Zoho CRM.

  • Lead and contact database analysis
    Search and analyze lead records, qualification statuses, source attribution, and follow-up histories stored in Zoho CRM.

  • Territory and team performance reporting
    Compare deal performance across territories, sales teams, and individual reps using Zoho CRM opportunity and activity data.

  • Activity and engagement history
    Access call logs, email records, meeting notes, and task histories from Zoho CRM contact and account timelines.

  • Forecast and quota analysis
    Query forecast categories, quota assignments, and attainment data from Zoho CRM to support sales planning.

  • Customer lifecycle and retention insights
    Analyze deal win/loss patterns, customer reactivation histories, and churn indicators from Zoho CRM data.

Licensing and activation

Devart MCP Server for Zoho CRM is distributed as a free single-source MCP server.

To connect to Zoho CRM, the server requires the corresponding Devart ODBC Driver for Zoho CRM, which is a paid product.

A 30-day free trial is available for the Devart ODBC Driver for Zoho CRM.

See the product page and documentation for the latest installation and activation details.

Support

Other Devart connectivity solutions

來源:README.md,提交 ec262ac

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v1.1.0最新Sep 23, 2026

評分

已滿足適用檢查項的 40%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。