Devart MCP Server for Zoho Desk (ADO.NET)

com.devartPublished by devart.comv1.1.0Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Lets an assistant query and modify Zoho Desk helpdesk data through Devart's ADO.NET or ODBC connectivity drivers.

What you can do
Provides schema-aware read and write access to Zoho Desk from an AI client, translating natural-language prompts into structured queries and returning structured results. Typical uses include ticket volume and queue analysis, agent workload and resolution metrics, SLA breach patterns, CSAT trends, escalation and priority analysis, and knowledge base article analytics. It runs as a local server and can be configured over stdio or HTTP.
When to use it
Worth adding when Zoho Desk is a primary data source and you want to explore tickets, agents, SLAs, CSAT, or knowledge base metrics conversationally instead of exporting data or writing queries by hand. It suits support and operations teams doing recurring reporting on helpdesk data.
Requirements
Windows desktop with .NET 8 SDK for building from source, plus a Devart dotConnect for Zoho Desk ADO.NET provider (restored via NuGet) or a manually installed Devart ODBC Driver for Zoho Desk. A connection string or DSN is configured in mcpserver.json and supplied through the DEVART_MCP_ZOHODESK_CONNECTION environment variable. Zoho Desk credentials and a Devart license key are part of that connection configuration.
Before you install
The connection string carries Zoho Desk credentials and a Devart license key, so keep the DEVART_MCP_ZOHODESK_CONNECTION value and mcpserver.json out of shared or version-controlled files. The server offers read and write access, so assistant-issued changes to tickets or other records should be reviewed. The required Devart ODBC Driver for Zoho Desk is a paid product with a 30-day trial.

Installation

In SourceWeft

  1. Open Devart MCP Server for Zoho Desk (ADO.NET) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

Source: README.md at commit f47b215

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.0LatestSep 23, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.