Provides tools for interacting with Zendesk, enabling ticket search and analysis, and Help Center article management (list, search, create, update).
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 Server Fetch all tickets from the past week and analyze trends"
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.
A Zendesk MCP (Model Context Protocol) server for Kojo. Gives Claude access to support tickets and Help Center articles for trend analysis, knowledge base management, and customer insight research.
"Fetch all tickets from the past week and provide an analysis of any trends you find"
"Pull last month's solved tickets and identify the top 5 feature gaps driving support volume"
"Search our help center for articles about approvals — are there any gaps we should fill?"
"Draft a new help center article explaining how to set up invoice matching"
Related MCP server: Zendesk MCP Server
Tool | Description |
| Search tickets by date range and status. Returns full conversation transcripts. Supports natural language dates ("past month", "past 7 days"). |
| Search, list, or get Help Center articles. Includes section discovery for browsing the knowledge base structure. |
| Create new Help Center articles (drafts by default). |
| Update article title, body, or draft status. |
Log into Zendesk as an admin
Go to Admin Center > Apps and integrations > Zendesk API
Enable Token Access if not already enabled
Click Add API token, give it a name, and copy the token
git clone <repo-url>
cd zendesk-mcp
npm install
npm run buildAdd to your .mcp.json:
{
"mcpServers": {
"zendesk": {
"type": "stdio",
"command": "node",
"args": ["/absolute/path/to/zendesk-mcp/build/index.js"],
"env": {
"ZENDESK_SUBDOMAIN": "your-subdomain",
"ZENDESK_EMAIL": "your-email@example.com",
"ZENDESK_API_TOKEN": "your-api-token"
}
}
}
}Replace the env values with your own. The subdomain is the part before .zendesk.com in your Zendesk URL.
Variable | Description |
| Default permission group for new articles. If unset, Zendesk assigns its own default. |
Node.js 18+
A Zendesk account with API token access
Claude Code with MCP support
Create a new article in the Zendesk Help Center. The article is created as a draft by default to allow review before publishing. Requires a section_id — use read_articles with include_sections=true to discover available sections.
Inputs: body (required), title (required), section_id (required), draft, +4 more.
Fetch Zendesk support tickets with full conversation transcripts for trend analysis. Filters by date range and ticket status. Returns ticket metadata (subject, status, priority, tags, dates) and the complete conversation transcript for each ticket. Use for analyzing support trends, common issues, and customer sentiment.
Inputs: limit, status, end_date, start_date.
Read articles from the Zendesk Help Center (Guide). Supports four modes: "search" for full-text search, "list" to browse articles by section or labels, "get" to retrieve a single article by ID with full content, and "sections" to list all Help Center sections (lightweight — use this to discover section IDs before creating articles).
Inputs: mode (required), query, locale, sort_by, +6 more.
Update an existing Zendesk Help Center article's content (title, body, draft status). Uses the Zendesk Translations API to modify content for the specified locale. At least one of title, body, or draft must be provided.
Inputs: article_id (required), body, draft, title, +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
Each tool has a clearly distinct purpose: fetch_tickets is exclusively for support tickets, while read_articles, create_article, and update_article handle help center articles without overlap. Even though read_articles supports multiple modes, it does not conflict with the write tools.
All tool names follow a consistent verb_noun snake_case pattern (fetch_tickets, read_articles, create_article, update_article). The verbs are action-oriented and clearly indicate the operation, making the naming predictable and easy to navigate.
With only 4 tools, the set is compact but well-scoped for the two main domains (ticket analysis and article management). Each tool serves a necessary function without redundancy or bloat.
The article workflow is nearly complete, with read, create, and update operations, but it lacks delete functionality. Ticket handling only supports fetching, which aligns with the stated trend-analysis purpose but may be limiting for other use cases. Overall, the coverage is solid with minor gaps.
Connect Claude, ChatGPT or any AI assistant to Zendesk tickets, CSAT, macros and Help Center.
Read tickets, users, orgs, macros and satisfaction ratings; create, update and comment on tickets.
Ask questions about your support tickets, chats, agents and AI answer quality, with cited tickets.
Work your Zono Support help desk from an AI client: tickets, customers, purchases and knowledge.