Devart MCP Server for Zoho Desk (ADO.NET)

com.devart由 devart.com 发布v1.1.0更新于 Oct 24, 2026

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

已验证STDIO仅桌面数据与分析商业与电商

概览

AI 生成的概览

让助手通过 Devart 的 ADO.NET 或 ODBC 连接驱动查询和修改 Zoho Desk 工单数据。

可以做什么
为 AI 客户端提供对 Zoho Desk 的感知架构的读写访问,把自然语言请求转换为结构化查询并返回结构化结果。典型用途包括工单量与队列分析、坐席工作量与解决量指标、SLA 违约模式、CSAT 趋势、升级与优先级分析,以及知识库文章分析。它以本地服务器方式运行,可通过 stdio 或 HTTP 配置。
适用场景
当 Zoho Desk 是主要数据源,且希望以对话方式查看工单、坐席、SLA、CSAT 或知识库指标,而不是导出数据或手写查询时,适合添加。适用于需要定期对客服数据进行报表的支持与运营团队。
运行要求
Windows 桌面环境,从源码构建需要 .NET 8 SDK,以及 Devart dotConnect for Zoho Desk ADO.NET 提供程序(通过 NuGet 还原)或手动安装的 Devart ODBC Driver for Zoho Desk。连接字符串或 DSN 在 mcpserver.json 中配置,并通过 DEVART_MCP_ZOHODESK_CONNECTION 环境变量提供。Zoho Desk 凭据和 Devart 许可证密钥包含在该连接配置中。
安装前请注意
连接字符串包含 Zoho Desk 凭据和 Devart 许可证密钥,请勿将 DEVART_MCP_ZOHODESK_CONNECTION 的值和 mcpserver.json 放入共享或版本控制文件中。该服务器提供读写访问,助手对工单或其他记录的修改应经过审核。所需的 Devart ODBC Driver for Zoho Desk 为付费产品,提供 30 天试用。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Devart MCP Server for Zoho Desk (ADO.NET),将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

[Devart MCP Server for Zoho Desk]

Version 1.1.0

What's new · Changelog

Devart MCP Server for Zoho Desk

Devart MCP Server for Zoho Desk 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 Desk 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 Desk helps AI clients communicate directly with Zoho Desk 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 Desk:

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

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

3. In Devart MCP Server for Zoho Desk, 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 Desk, ensure the following components are installed:

  • .NET 8 SDK
  • ADO.NET connection — Devart.AI.McpServer.AdoNet.ZohoDesk.csproj Devart dotConnect for Zoho Desk (installed automatically via NuGet during build)
  • ODBC connection — Devart.AI.McpServer.Odbc.ZohoDesk.csproj Devart ODBC Driver for Zoho Desk (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-desk.gitcd devart-mcp-server-zoho-desk

Step 2: Build the MCP Server from source

You can build Devart MCP Server for Zoho Desk 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.ZohoDesk/Devart.AI.McpServer.AdoNet.ZohoDesk.csproj -c ReleaseZohoDesk /p:TargetFramework=net8.0

The Devart dotConnect for Zoho Desk 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.ZohoDesk/Devart.AI.McpServer.Odbc.ZohoDesk.csproj -c ReleaseZohoDesk -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.ZohoDesk/Devart.AI.McpServer.Odbc.ZohoDesk.csproj -c ReleaseZohoDesk -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_zohodesk",      "ConnectionString": "Authentication Type=OAuthInteractive;DataCenter=US;OrganizationId=your_organization_id;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_zohodesk",      "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_zohodesk",      "ConnectionString": "Driver={Devart ODBC Driver for Zoho Desk};Server=localhost;User ID=zohodesk;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.ZohoDesk.exe run my_zohodesk
  • To start the server with ODBC, run the following command:
cmd
Devart.AI.McpServer.Odbc.ZohoDesk.exe run my_zohodesk

where my_zohodesk 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.ZohoDesk.exe",      "args": [        "run",        "my_zohodesk"      ]    }  }}

where:

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

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

  • my_zohodesk 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 Desk 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 Desk with other AI clients such as Cline, Codex, Cursor, Visual Studio Code, Windsurf, Zed.

Supported clients

Devart MCP Server for Zoho Desk 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 Desk is a practical fit for teams working with Zoho Desk as their primary data source.

  • Ticket volume and queue analysis
    Query open ticket counts, inbound volumes by channel, queue depths, and ticket age distributions from Zoho Desk in natural language.

  • Agent productivity and workload monitoring
    Analyze ticket assignments, resolution counts, handle times, and workload balance across support agents in Zoho Desk.

  • SLA compliance and breach analysis
    Monitor SLA adherence, identify breach patterns, and analyze first response and resolution time performance from Zoho Desk data.

  • Customer satisfaction and CSAT trends
    Query CSAT scores, feedback comments, satisfaction trends by department, and low-rating patterns from Zoho Desk survey data.

  • Escalation and priority analysis
    Investigate escalation rates, ticket priority distributions, and re-open patterns to identify service quality issues in Zoho Desk.

  • Knowledge base and self-service analytics
    Analyze article views, search queries, and deflection rates from Zoho Desk knowledge base data to improve self-service content.

Licensing and activation

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

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

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

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

Support

Other Devart connectivity solutions

来源:README.md,提交 f47b215

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

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

评分

已满足适用检查项的 40%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

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