Zendesk MCP Server 6f31c6b9

MCP数据服务

提供方 wlaubernds

数据服务 未标注 Token 社区 / 第三方 ClaudeCursor

Zendesk MCP Server是一个连接AI助手与Zendesk的协议服务器,支持通过自然语言查询支持工单、帮助文章和客户反馈。

一句话选型结论

按资料字段整理

Zendesk MCP Server 6f31c6b9 属于数据服务类 MCP 服务器,传输方式未标注,Token,可直接接入 Claude、Cursor,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类数据服务 传输方式未标注 鉴权Token 部署方式未标注
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 6 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

数据服务
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量6暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

AI查询JavaScript本地部署客户支持自然语言处理Zendesk集成数据分析

安装与配置

未标注 Token
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后客户端会列出约 6 个工具,随便调一个只读工具确认能返回结果。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
数据库查询

用自然语言查库、取数,不用手写 SQL。

数据同步与清洗

把多来源数据拉到一处做整理。

报表取数

按口径快速拉出统计结果。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注 6 个工具,职责相对集中,接入后不容易误操作。
  • 已适配 Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在数据服务场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zendesk MCP Server 6f31c6b9当前 6 未标注 未标注 无 2026-05-17
Memory 9d25f64e 9 未标注 未标注 无 2026-05-17
Getzep MCP 9 stdio · 本地进程 本地部署 有 2026-05-17
anything-llm 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Prisma MCP Server 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Astr Bot 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

数据服务
字段来自项目仓库与公开索引,中文说明由本站标注
提供方wlaubernds上游标注的维护方 wlaubernds
分类数据服务本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

7.2 KB
来自项目仓库与上游目录的原文,未做删改

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

Installation

Option 1: Use via npx (Recommended)

No installation required! Just configure and use:```json
{
"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```bash
npm install -g zendesk-mcp-server

Then configure:```json
{
"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```bash
git clone https://github.com/wlaubernds/zendesk-mcp-server.git
cd zendesk-mcp-server
npm install
npm run build

Then use the local path in your config:```json
{
"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

1. Log in to your Zendesk Admin Center
2. Navigate to **Apps and integrations** > **APIs** > **Zendesk API**
3. Click the **Settings** tab
4. Under **Token Access**, click **Add API token**
5. Give it a description (e.g., "MCP Server")
6. Copy the token (you'll only see it once!)
7. 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.json`
- **Claude Desktop**:
  - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
  - Windows: `%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 Search tickets with advanced query syntax (status, priority, tags, dates)
get_ticket Get full details of a specific ticket including all comments
search_articles Search help center articles
get_article Get full content of a specific article
search_feature_feedback Comprehensive analysis of feedback for a specific feature
get_tickets_by_tag Get all tickets with a specific tag

Zendesk Query Syntax

When searching tickets, you can use these filters:

  • status: - new, open, pending, hold, solved, closed
  • priority: - low, normal, high, urgent
  • tags: - ticket tags
  • subject: - search in subject line
  • created> or created< - date filters (format: YYYY-MM-DD)
  • updated> or updated< - last updated date
  • Plain 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 reset


## Permissions

🔒 **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_SUBDOMAIN`
- `ZENDESK_EMAIL`
- `ZENDESK_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.json` is correct (if using local installation)
- Verify the JSON syntax in your config file is valid

## Development

### Building```bash
npm run build

Watch Mode```bash

npm run watch


### Running Locally```bash
npm run dev

Make sure to set the environment variables:bash export ZENDESK_SUBDOMAIN=your-company export ZENDESK_EMAIL=your-email@company.com export ZENDESK_API_TOKEN=your-api-token npm run dev

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

  1. Fork the repository
  2. Create your feature branch (git checkout -b feature/amazing-feature)
  3. Commit your changes (git commit -m 'Add some amazing feature')
  4. Push to the branch (git push origin feature/amazing-feature)
  5. 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

  • Model Context Protocol
  • MCP Servers Repository

Support

If you encounter any issues or have questions:

  • 🐛 Report a bug
  • 💡 Request a feature
  • 📖 Read the docs

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Zendesk MCP Server 6f31c6b9 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Zendesk MCP Server 6f31c6b9 怎么在 Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Zendesk MCP Server 6f31c6b9 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Zendesk MCP Server 6f31c6b9 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Zendesk MCP Server 6f31c6b9 支持哪些客户端?

资料标注支持 Claude、Cursor;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Zendesk MCP Server 6f31c6b9 能提供哪些能力?

资料显示约 6 个工具;能力标签包括 JavaScript、Claude、数据分析。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。