zendesk-mcp
This server provides a set of AI-powered tools for Zendesk support workflows:
search_similar_tickets: Find past tickets similar to an issue via semantic and keyword search; accepts
issueand optionaltopK(default 5, max 20).get_customer_context: Retrieve a customer's organization and full ticket history by
requesterEmailororganizationname.assess_solutions_by_version: Search past solutions/workarounds for an issue and check applicability to a given
customerVersion, with optionaltopKlimit.summarize_daily_work: Summarize a day's Zendesk activity (tickets touched, solved, open, high-priority follow-ups) for a
date(defaults to today) and optionalassignee.sync_rag_store: Incrementally update the local RAG vector store with recently updated Zendesk tickets (no parameters).
Provides tools for Zendesk support workflows, including searching similar tickets, retrieving customer context (organization and ticket history), assessing solutions by version, and summarizing daily work activity.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@zendesk-mcp Search similar tickets for 'email not sending'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
zendesk-mcp
A custom MCP (Model Context Protocol) server for Zendesk support workflows, built with Node + TypeScript
and the official @modelcontextprotocol/sdk.
What it does
Exposes five tools that Claude (or any MCP client) can call:
Tool | Purpose |
| Semantic search (via an external vector index) + live Zendesk keyword search for similar past issues |
| Pull a customer's org + full ticket history before responding |
| Find past fixes for an issue and check if they apply to the customer's version |
| Roll up a day's Zendesk activity: tickets touched, by status, high-priority follow-ups |
| Incrementally pull Zendesk tickets updated since the last run and upsert them into the local RAG vector store |
Related MCP server: mcp-server-zendesk
Tool reference
Each tool's parameters are defined by its inputSchema in src/tools/*.ts — that file is the source of truth if this
table drifts. Params are passed as a JSON object matching the schema below.
Tool | Parameter | Type | Required | Default | Notes |
|
| string | yes | — | Description of the issue/symptom to search for |
| integer (1-20) | no |
| Max number of similar past tickets to return | |
|
| string (email) | one of | — | Single customer/requester email address |
| string | one of | — | Customer organization name, e.g. | |
|
| string | yes | — | Issue description to search past solutions for |
| string | yes | — | Customer's current product version, e.g. | |
| integer (1-20) | no |
| Max number of past-solution matches to consider | |
|
| string ( | no | today | Day to summarize |
| string (email) | no |
| Scopes results to this assignee; defaults to you | |
| — | (no parameters) | — | — | Safe to run any time; only processes tickets updated since the last sync |
Calling a tool through Claude
Describe what you want in plain language — Claude fills in the parameters:
Run summarize_daily_work for 2026-07-20
Search similar tickets for "PDF export hangs on large files", top 10
Get customer context for jane@example.com
Get customer context for the organization AnthologyCalling a tool via raw MCP JSON-RPC
This is the tools/call request the client actually sends (see test-client.mjs for a working example):
{
"method": "tools/call",
"params": {
"name": "summarize_daily_work",
"arguments": {
"date": "2026-07-20",
"assignee": "sophia.banda@nutrient.io"
}
}
}Omit any optional argument to fall back to its default (e.g. omit date for "today", omit assignee to scope to
ZENDESK_EMAIL).
Calling a tool from a plain terminal (no Claude Code needed)
The server is just a Node process speaking MCP over stdio — any MCP client can talk to it, including a terminal
script. Use run.mjs (loads your real .env, unlike test-client.mjs which uses fake credentials for smoke
testing):
node run.mjs <tool_name> '<json_args>'
# examples
node run.mjs get_customer_context '{"organization":"Anthology"}'
node run.mjs get_customer_context '{"requesterEmail":"jane@example.com"}'
node run.mjs summarize_daily_work '{"date":"2026-07-20"}'
node run.mjs search_similar_tickets '{"issue":"PDF export hangs on large files","topK":10}'
node run.mjs sync_rag_store '{}'Run npm run build first if you've made source changes — this calls the compiled server in build/, not the
TypeScript source directly.
Syncing the RAG store
The lancedb vector DB provider (see Setup below) is a local, file-based store extracted from a one-time export.
To keep it current without re-pulling that full export, run the incremental sync whenever you want — it only
processes Zendesk tickets updated since the last run (tracked in data/rag-store/.sync-state.json):
npm run sync-rag
# or, equivalently, via the MCP tool:
node run.mjs sync_rag_store '{}'How it's put together
src/
clients/
zendesk.ts – thin wrapper over the Zendesk REST API (search, tickets, users, orgs)
vectorDb.ts – adapter interface (VectorDb) + a mock implementation + a generic HTTP
implementation + a lancedb implementation, so the real backend can be
swapped in via .env only
embedder.ts – shared embedding model (Xenova/all-MiniLM-L6-v2) used by both the
lancedb query path and the ingestion pipeline, so vectors stay comparable
ingest/
syncRagStore.ts – incremental sync: fetch changed tickets, embed, upsert into LanceDB
cli.ts – thin CLI wrapper around syncRagStore.ts (`npm run sync-rag`)
tools/
searchSimilarTickets.ts
customerInfo.ts
assessSolutions.ts
dailySummary.ts
syncRagStoreTool.ts
index.ts – wires everything together and starts the server over stdio
test-client.mjs – a tiny MCP client used to sanity-check the server without wiring it into ClaudeWhy the adapter pattern for the vector DB
The exact shape of the backing RAG index isn't fixed yet. Rather than hard-coding a client, vectorDb.ts defines
a one-method interface:
interface VectorDb {
search(query: string, topK?: number): Promise<VectorMatch[]>;
}Everything else in the codebase (the tools) only depends on that interface, not on a specific backend.
VECTOR_DB_PROVIDER=mock in .env gives a fake in-memory index for building and testing end-to-end. Once the
real index's API is known:
use the built-in
HttpVectorDbif there's a query endpoint in front of it (adjust the request/response shape invectorDb.tsto match the actual API), oradd a new class (e.g.
PineconeVectorDb,QdrantVectorDb) implementing the same interface, and add a case for it invectorDbFromEnv().
No changes needed anywhere else.
Setup
npm install
cp .env.example .env # fill in your Zendesk subdomain/email/API token
npm run build.env fields:
ZENDESK_SUBDOMAIN/ZENDESK_EMAIL/ZENDESK_API_TOKEN— from Zendesk Admin Center > Apps and integrations > APIs > Zendesk API. Generate a token there and enable token access.VECTOR_DB_PROVIDER—mockto start;lancedbonce you have the real store extracted locally (see below); switch to something else once you have other real connection info.VECTOR_DB_PATH— only used by thelancedbprovider. Path to the extracted LanceDB store, e.g../data/rag-store/store. The store itself is a one-time export from a coworker (an AES-encrypted zip — get the password from them directly, never paste it into chat) extracted intodata/rag-store/(gitignored). Once extracted, keep it current withnpm run sync-rag— see "Syncing the RAG store" above.
Running it standalone (for testing)
node test-client.mjsThis spawns the built server, lists its tools, and calls assess_solutions_by_version against the mock vector
data — useful for iterating without wiring the server into an actual MCP client.
Registering it with Claude
Add it to your MCP client config (e.g. Claude Desktop's claude_desktop_config.json, or Claude Code's
.mcp.json):
{
"mcpServers": {
"zendesk-mcp": {
"command": "node",
"args": ["/absolute/path/to/zendesk-mcp/build/index.js"],
"env": {
"ZENDESK_SUBDOMAIN": "your-company",
"ZENDESK_EMAIL": "you@company.com",
"ZENDESK_API_TOKEN": "...",
"VECTOR_DB_PROVIDER": "mock"
}
}
}
}Notes / open items
(Internal notes — may be stale, keep or prune as they're resolved.)
The real vector index's query interface isn't confirmed yet (REST endpoint? Python service? direct DB connection to Pinecone/Qdrant/pgvector/etc). That determines whether
HttpVectorDbworks as-is, needs tweaking, or a new adapter class is needed.Once wired to the real index, revisit the
metadatashapeassess_solutions_by_versionexpects (fixedInVersion,product,tags) — align it with whatever fields the index actually stores per chunk.Consider adding a
list_productsorlist_versionstool if there's a canonical version list to validatecustomerVersionagainst.Add tests (e.g. with
node --test) forcompareVersionsinassessSolutions.ts— it's a naive semver comparator and worth hardening for versions like8.4.2-rc1.
Available Tools
4 toolsassess_solutions_by_versionassess_solutions_by_versionA
Search past solutions/workarounds for an issue and check whether each fix applies to a given product version. Use this to figure out if a known fix should already cover the customer's version, or if they need to upgrade.
Inputs: issue (required), customerVersion (required), topK.
get_customer_contextget_customer_contextA
Pull together everything known about a customer: their org, past tickets, and prior reported issues. Look up by requester email for a single contact, or by organization name for the whole account. Use this before responding to a ticket to understand history and avoid repeating past answers.
Inputs: organization, requesterEmail.
search_similar_ticketsSearch similar ticketsA
Find past Zendesk tickets similar to a described issue, using semantic search over ticket history plus a live Zendesk keyword search. Use this before triaging a new ticket to check for precedent.
Inputs: issue (required), topK.
summarize_daily_worksummarize_daily_workA
Summarize Zendesk activity for a given day (default: today) — tickets touched, solved, still open, and any high-priority items needing follow-up. Ask for this at end of day or during standup prep.
Inputs: date, assignee.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: finding similar tickets, gathering customer context, assessing solutions by version, and summarizing daily work. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., search_similar_tickets, get_customer_context), making them predictable and easy to navigate.
Four tools are appropriate for a focused support assistant server. Each tool addresses a specific need without superfluous or missing functionalities.
The tool set covers information retrieval and analysis but lacks core actions like creating, updating, or commenting on tickets, which are essential for full ticket lifecycle management. This creates dead ends for agents needing to take action.
Maintenance
Related MCP Connectors
Connect Claude, ChatGPT or any AI assistant to Zendesk tickets, CSAT, macros and Help Center.
Work your Zono Support help desk from an AI client: tickets, customers, purchases and knowledge.
Ask questions about your support tickets, chats, agents and AI answer quality, with cited tickets.
Zendesk configuration management for AI agents: propose, review, apply and roll back changes.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables comprehensive management of Zendesk tickets, comments, and Help Center articles through tools for searching, creating, and updating content. It includes specialized prompts for ticket analysis and response drafting to streamline support workflows.71Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to search tickets, manage tags, create tickets, inspect automations, and more in Zendesk.MIT
- AlicenseAqualityDmaintenanceEnables fetching and analyzing Zendesk support tickets and Help Center articles for trend analysis, knowledge base management, and drafting new articles.465 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables users to fetch, create, and update Zendesk tickets and comments, analyze tickets and draft responses, and query Help Center articles as a knowledge base.-