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 分

    请在仓库或注册中心条目中声明许可证。