zendesk-mcp-server
Provides tools for searching and retrieving Zendesk support tickets, help center articles, and feature feedback. Enables querying tickets with filters (status, tags, dates, priority), retrieving ticket details and comments, searching knowledge base articles, analyzing feature feedback, and finding tickets by tags.
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 What are users saying about the new dashboard?"
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 Server
Model Context Protocol server that connects AI assistants to Zendesk, enabling natural language queries over support tickets, help articles, and customer feedback.
Search your Zendesk data using AI in Cursor, Claude Desktop, or any MCP-compatible tool.
Features
🔍 Search Support Tickets - Query tickets with advanced filters (status, tags, dates, priority)
📚 Search Knowledge Base - Find relevant help articles and documentation
📊 Feature Feedback Analysis - Get comprehensive feedback about specific features including bug reports, feature requests, and support questions
🎫 Ticket Details - Retrieve full ticket information including all comments
📖 Article Content - Access complete help center articles
🏷️ Tag-based Search - Find all tickets with specific tags
Related MCP server: zendesk-mcp
Installation
Option 1: Use via npx (Recommended)
No installation required! Just configure and use:
{
"mcpServers": {
"zendesk": {
"command": "npx",
"args": ["-y", "zendesk-mcp-server"],
"env": {
"ZENDESK_SUBDOMAIN": "your-company",
"ZENDESK_EMAIL": "your-email@company.com",
"ZENDESK_API_TOKEN": "your-api-token-here"
}
}
}
}Option 2: Install Globally
npm install -g zendesk-mcp-serverThen configure:
{
"mcpServers": {
"zendesk": {
"command": "zendesk-mcp-server",
"env": {
"ZENDESK_SUBDOMAIN": "your-company",
"ZENDESK_EMAIL": "your-email@company.com",
"ZENDESK_API_TOKEN": "your-api-token-here"
}
}
}
}Option 3: Local Development
git clone https://github.com/wlaubernds/zendesk-mcp-server.git
cd zendesk-mcp-server
npm install
npm run buildThen use the local path in your config:
{
"mcpServers": {
"zendesk": {
"command": "node",
"args": ["/path/to/zendesk-mcp-server/dist/index.js"],
"env": {
"ZENDESK_SUBDOMAIN": "your-company",
"ZENDESK_EMAIL": "your-email@company.com",
"ZENDESK_API_TOKEN": "your-api-token-here"
}
}
}
}Getting Your Zendesk API Credentials
Log in to your Zendesk Admin Center
Navigate to Apps and integrations > APIs > Zendesk API
Click the Settings tab
Under Token Access, click Add API token
Give it a description (e.g., "MCP Server")
Copy the token (you'll only see it once!)
Your subdomain is the first part of your Zendesk URL:
https://YOUR-SUBDOMAIN.zendesk.com
Configuration
Add the configuration to your MCP settings file:
Cursor:
~/.cursor/mcp.jsonClaude Desktop:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
See examples/cursor-config.json for a complete example.
Usage
Once configured, you can use natural language to query your Zendesk data:
Example Queries
Analyze feature feedback:
"Show me all feedback about our mobile app from the last 3 months"Search tickets:
"Find all high priority bug reports from this week"
"What are users saying about the new dashboard?"Weekend summaries:
"Summarize all tickets from this weekend"Specific ticket details:
"Get full details and comments for ticket #12345"Search help articles:
"Find all help articles about password reset"Available Tools
The MCP server provides these tools that AI assistants can use:
Tool | Description |
| Search tickets with advanced query syntax (status, priority, tags, dates) |
| Get full details of a specific ticket including all comments |
| Search help center articles |
| Get full content of a specific article |
| Comprehensive analysis of feedback for a specific feature |
| Get all tickets with a specific tag |
Zendesk Query Syntax
When searching tickets, you can use these filters:
status:- new, open, pending, hold, solved, closedpriority:- low, normal, high, urgenttags:- ticket tagssubject:- search in subject linecreated>orcreated<- date filters (format: YYYY-MM-DD)updated>orupdated<- last updated datePlain text for full-text search
Query Examples:
status:open tags:bug priority:high
tags:mobile created>2024-01-01
subject:"cannot login" priority:urgent
password resetPermissions
🔒 This MCP server is READ-ONLY - it has zero write permissions to Zendesk.
✅ What it CAN do:
Search and read support tickets
Retrieve ticket details and comments
Search knowledge base articles
Analyze feature feedback
Query tickets by tags, status, priority, dates
❌ What it CANNOT do:
Create tickets
Update or modify tickets
Add comments to tickets
Change ticket status
Modify tags, priority, or assignments
Create or edit help articles
Delete anything
This read-only design makes it safe to use with shared API tokens for analysis and reporting purposes.
API Rate Limits
Zendesk enforces API rate limits:
Professional plans: 700 requests per minute
Team plans: 400 requests per minute
The server doesn't implement rate limiting internally, so be mindful when making large queries.
Troubleshooting
"Error: Missing required environment variables"
Make sure all three environment variables are set in your MCP config:
ZENDESK_SUBDOMAINZENDESK_EMAILZENDESK_API_TOKEN
"Zendesk API error (401)"
Check that your email and API token are correct
Verify the API token hasn't been revoked in Zendesk
Ensure you're using the correct authentication format
"Zendesk API error (404)"
Verify your subdomain is correct
Check that the ticket/article ID exists
Server not appearing in Cursor
Make sure you've restarted Cursor completely after adding the config
Check that the path in
mcp.jsonis correct (if using local installation)Verify the JSON syntax in your config file is valid
Development
Building
npm run buildWatch Mode
npm run watchRunning Locally
npm run devMake sure to set the environment variables:
export ZENDESK_SUBDOMAIN=your-company
export ZENDESK_EMAIL=your-email@company.com
export ZENDESK_API_TOKEN=your-api-token
npm run devContributing
Contributions are welcome! Please feel free to submit a Pull Request.
Fork the repository
Create your feature branch (
git checkout -b feature/amazing-feature)Commit your changes (
git commit -m 'Add some amazing feature')Push to the branch (
git push origin feature/amazing-feature)Open a Pull Request
License
This project is licensed under the MIT License - see the LICENSE file for details.
Security
⚠️ Never commit your API tokens to version control!
Your MCP configuration file should remain local to your machine and not be shared or committed to git.
Acknowledgments
Built with the Model Context Protocol SDK by Anthropic.
Related Projects
Support
If you encounter any issues or have questions:
Available Tools
6 toolsget_articleB
Get full content of a specific Help Center article by ID
Inputs: article_id (required).
get_ticketA
Get full details of a specific ticket by ID, including all comments and metadata
Inputs: ticket_id (required), include_comments.
get_tickets_by_tagB
Get all tickets with a specific tag
Inputs: tag (required), page, per_page.
search_articlesA
Search Zendesk Help Center articles (knowledge base).
Examples:
"collections feature" - Search for articles about collections
"route planning guide" - Find articles about route planning
"label:feature_name" - Search by label
Inputs: query (required), page, per_page.
search_feature_feedbackB
Search for all tickets and articles related to a specific feature. This is a convenience tool that searches for feature-related content including: - Bug reports - Feature requests - User feedback - Support questions
Example: "collections" will find all tickets and articles mentioning collections
Inputs: feature_name (required), days_back, include_solved.
search_ticketsB
Search Zendesk support tickets with advanced query syntax.
Examples:
"status:open tags:collections" - Find open tickets tagged with "collections"
"subject:bug priority:high" - Find high priority bug tickets
"tags:feature_request created>2024-01-01" - Find feature requests created after Jan 1, 2024
"collections route" - Full-text search for "collections route"
Query syntax supports:
status: (new, open, pending, hold, solved, closed)
priority: (low, normal, high, urgent)
tags: (tag names)
created: (date comparisons like >2024-01-01, <2024-12-31)
subject: (search in subject)
Full text search without prefix
Inputs: query (required), page, per_page.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Most tools have distinct purposes: search_tickets (query-based search), get_ticket (by ID), search_articles (KB search), get_article (by ID). However, search_feature_feedback and get_tickets_by_tag overlap with search_tickets, as they are essentially specialized searches. search_feature_feedback is broad and could be redundant, while get_tickets_by_tag could be achieved with search_tickets using a tag: query. Minor ambiguity exists but descriptions clarify usage.
All tool names follow a consistent verb_noun pattern: search_tickets, get_ticket, search_articles, get_article, search_feature_feedback, get_tickets_by_tag. The pattern is predictable and aids in understanding tool functionality.
With 6 tools, the count is well within the typical range for a focused MCP server. Each tool addresses a specific need, though some (like search_feature_feedback and get_tickets_by_tag) could be seen as convenience wrappers that overlap with search_tickets, slightly inflating the count.
The server covers search and retrieval for tickets and articles, but lacks write operations such as creating, updating, or deleting tickets and articles. For a Zendesk support tool, common actions like adding comments or updating ticket status are missing, limiting agent workflows.
Maintenance
Related MCP Connectors
Connect Claude, ChatGPT or any AI assistant to Zendesk tickets, CSAT, macros and Help Center.
Connect your team's living knowledge base — docs, data, issues, CRM — to Claude and ChatGPT.
Connect Claude, Cursor, or ChatGPT to your business data. Ask questions, get answers.
Connect your AI to all your data - 200+ sources, intelligently filtered, compliance-ready.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to search tickets, manage tags, create tickets, inspect automations, and more in Zendesk.MIT
- AlicenseAqualityDmaintenanceConnects AI assistants to your Zendesk account with 14 curated tools for managing tickets, users, organizations, and help center articles, running locally with no third-party services.14MIT
- 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 AI assistants to retrieve and manage support tickets and comments, analyze tickets and draft responses via built-in prompts, and search Help Center articles as a knowledge base, with per-operator OAuth so each user acts under their own Zendesk permissions.-