Zendesk MCP (Michaelrice)

MCPAI代理

提供方 michaelrice

AI代理 stdio · 本地进程 无需鉴权 社区 / 第三方 Claude
查看接入方式

A Model Context Protocol server that exposes Zendesk ticket read and write tools to Claude Code and other MCP clients. Search, list, and fetch tickets, comments, and attachments. Create new tickets and update existing fields including group, custom status, and tags. Post public replies and internal notes. Set ticket status and assign agents. Browse and apply views and macros. Look up users, groups, organizations, and custom statuses. Read and write time-tracking entries. Format a ticket as a Markdown issue draft for handoff to GitLab, GitHub, or Jira. Optional Help Center knowledge base resource and optional Git-Zen integration for linked GitLab issues, MRs, and commits.

一句话选型结论

按资料字段整理

Zendesk MCP (Michaelrice) 属于AI代理类 MCP 服务器,stdio · 本地进程,无需鉴权,可直接接入 Claude,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

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

能力标签

支持客户端

适用场景

zendeskmcpmodel-context-protocolclaudeanthropicsupporthelpdeskticketing

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
uvx zendesk-mcp

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Python,再按安装命令拉取依赖。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

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

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude,换客户端不用重新研究配置。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Zendesk MCP (Michaelrice)当前 未标注 stdio · 本地进程 本地部署 有 2026-05-18
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方michaelrice上游标注的维护方 michaelrice
分类AI代理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Python本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-18上游最后核验时间

详细介绍

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

zendesk-mcp

A Model Context Protocol server that exposes Zendesk ticket read and write tools to Claude Code and other MCP clients.

What it does

  • Search, list (paginated), and fetch Zendesk tickets, comments, and attachments
  • Create new tickets and update existing ticket fields (including group, custom status, and tags)
  • Post public replies and internal notes
  • Set ticket status and assign tickets to agents
  • Browse and apply views and macros
  • Look up users, groups, organizations, and custom statuses
  • Read and write time-tracking entries
  • Format a ticket as a Markdown issue draft for handoff to a tracker (GitLab, GitHub, Jira)
  • Two MCP prompts (analyze-ticket, draft-ticket-response) for ticket analysis and response drafting
  • (Optional) Expose Zendesk Help Center articles as an MCP resource
  • (Optional) Read linked GitLab issues / MRs / commits via the Git-Zen Zendesk app

Prerequisites

  • Python 3.10 or newer
  • A Zendesk OAuth client. A Zendesk admin can create one at:
    https://.zendesk.com/admin/apps-integrations/apis/zendesk-api/oauth_clients
    Set the redirect URL to http://localhost:8787/callback and request scopes read write.

Install

Install into a project-local virtualenv. Using a venv keeps zendesk-mcp and its dependencies isolated from your system Python and from other projects, and is the recommended path for everything below.

From a clone of this repository:```bash
python3 -m venv .venv
.venv/bin/pip install --upgrade pip
.venv/bin/pip install -e .


For development (also installs pytest):```bash
.venv/bin/pip install -e ".[dev]"

> Throughout this README, commands use the venv's binaries via .venv/bin/.... You can instead source .venv/bin/activate once per shell and drop the prefix — the result is the same.

OAuth setup

Run the interactive setup using the venv's Python:```bash
.venv/bin/python -m zendesk_mcp setup


You will be prompted for:

1. Your Zendesk subdomain (e.g. `acme` for `acme.zendesk.com`)
2. The OAuth client ID created by your admin
3. The OAuth client secret
4. (Optional) A Git-Zen integration field ID — see Optional: Git-Zen integration
5. (Optional) Whether to enable the Help Center knowledge base resource — see Optional: Help Center knowledge base

The setup opens a browser for the OAuth authorization step, then writes a token to `~/.config/zendesk-mcp/config.json` (mode `0600`).

If you have no browser, the URL is printed to the terminal — open it on any device, click **Allow**, and paste the resulting redirect URL back into the prompt.

### Token expiry and refresh

Zendesk access tokens expire. OAuth clients created on or after 2026-04-30 get a
30-minute default lifetime; older clients issue non-expiring tokens unless an expiry is
requested. Setup requests a 24-hour access token and a 90-day refresh token so the
behaviour is the same either way, and the server renews the access token automatically —
before it expires, and again if Zendesk rejects a token mid-request.

To make that possible, the config file also stores `refresh_token`, `expires_at`,
`client_id`, and `client_secret` alongside the access token. Keep the file at mode `0600`;
it is the same trust level as the access token itself. If your OAuth client returns no
refresh token, setup says so and the token is used as-is.

Re-run `.venv/bin/python -m zendesk_mcp setup` when:

- the refresh token expires (90 days with no use), or
- you revoke the OAuth grant in Zendesk.

In either case the tools return `Zendesk authorization failed: ... Re-run: zendesk-mcp setup`
rather than failing opaquely.

## Register with Claude Code

Register the MCP server using the venv's Python by absolute path. Claude Code launches the server in a fresh shell that does **not** inherit your activated venv, so the absolute path is required — pointing at a bare `python` here will fail to import `zendesk_mcp`.```bash
ZENDESK_MCP_DIR="$(pwd)"   # run this from the repo root, after install
claude mcp add --scope user zendesk -- "$ZENDESK_MCP_DIR/.venv/bin/python" -m zendesk_mcp

Or just inline the absolute path you want:```bash
claude mcp add --scope user zendesk -- /absolute/path/to/zendesk-mcp/.venv/bin/python -m zendesk_mcp


Then add the read tools to `permissions.allow` in `~/.claude/settings.json` to avoid per-call prompts:```json
{
  "permissions": {
    "allow": [
      "mcp__zendesk__zendesk_get_ticket",
      "mcp__zendesk__zendesk_get_tickets",
      "mcp__zendesk__zendesk_get_comments",
      "mcp__zendesk__zendesk_list_attachments",
      "mcp__zendesk__zendesk_download_attachment",
      "mcp__zendesk__zendesk_search_tickets",
      "mcp__zendesk__zendesk_ticket_to_gitlab_context",
      "mcp__zendesk__zendesk_list_views",
      "mcp__zendesk__zendesk_get_view",
      "mcp__zendesk__zendesk_get_view_tickets",
      "mcp__zendesk__zendesk_list_macros",
      "mcp__zendesk__zendesk_preview_macro",
      "mcp__zendesk__zendesk_search_users",
      "mcp__zendesk__zendesk_get_groups",
      "mcp__zendesk__zendesk_get_group_users",
      "mcp__zendesk__zendesk_get_organization",
      "mcp__zendesk__zendesk_list_custom_statuses"
    ]
  }
}

Write tools (zendesk_post_comment, zendesk_post_internal_note, zendesk_set_ticket_status, zendesk_assign_ticket, zendesk_create_ticket, zendesk_update_ticket, zendesk_log_time, zendesk_add_tag, zendesk_remove_tag, zendesk_apply_macro) are intentionally not in the default allow-list — Claude will prompt you per call.

Restricting tools

Every tool is enabled by default. To narrow what a deployment can do, for example where
ticket text is written by customers and the agent should not be able to reply to them, set
either of these in ~/.config/zendesk-mcp/config.json or in the server's environment. Values
from both are combined.

Config key Environment variable Effect
"read_only": true ZENDESK_MCP_READ_ONLY=true Registers no write tools (comments, notes, status, assignment, create/update, tags, macros, time logging)
"disabled_tools": ["zendesk_post_comment"] ZENDESK_MCP_DISABLED_TOOLS=zendesk_post_comment,zendesk_apply_macro Does not register the named tools

A disabled tool is never registered, so the model cannot see or call it. Names that match no
tool are reported on stderr.

Tools

Tickets

Tools that return ticket records include channel, the channel the ticket arrived on (Zendesk's via.channel: web, email, api, ...), or null when Zendesk does not say. zendesk_get_ticket also returns custom_fields as a list of {id, value} pairs; a field that is not set on the ticket has a null value.

Tool What it does
zendesk_search_tickets Search tickets by status, priority, type, assignee, requester, tags, or keyword. Each result includes channel
zendesk_get_tickets List tickets with pagination and sorting (page, per_page, sort_by, sort_order). Each ticket includes channel
zendesk_get_ticket Get one ticket's metadata, including channel and custom_fields
zendesk_create_ticket Create a new ticket (subject, description, optional priority/type/assignee_id/requester_id/tags/custom_fields)
zendesk_update_ticket Update one or more fields on an existing ticket (status, priority, subject, type, assignee_id, requester_id, group_id, custom_status_id, tags, custom_fields, due_at)
zendesk_get_comments Get the conversation thread on a ticket
zendesk_list_attachments List attachments on a ticket
zendesk_download_attachment Download an attachment to a local cache directory. The URL must be on your Zendesk host, and dest_dir must be inside the cache or a directory listed in attachment_allowed_dest_dirs in the config
zendesk_ticket_to_gitlab_context Format a ticket and its conversation as a Markdown issue draft
zendesk_post_comment Post a public reply on a ticket
zendesk_post_internal_note Post an agent-only internal note on a ticket
zendesk_set_ticket_status Set ticket status (new, open, pending, hold, solved, closed)
zendesk_assign_ticket Assign a ticket to an agent by email or me

Tags

Tool What it does
zendesk_add_tag Add a tag to a ticket (idempotent)
zendesk_remove_tag Remove a tag from a ticket (idempotent)

Views & Macros

Tool What it does
zendesk_list_views List all active views
zendesk_get_view Get a view's filter conditions and execution settings
zendesk_get_view_tickets Fetch tickets currently matching a view. Each ticket includes channel
zendesk_list_macros List active macros with their actions
zendesk_preview_macro Preview what changes a macro would make
zendesk_apply_macro Apply a macro to a ticket (applies field changes and posts any comment)

Users, Groups & Organizations

Tool What it does
zendesk_search_users Find users by name or email
zendesk_get_groups List all active groups
zendesk_get_group_users List the members of a group
zendesk_get_organization Fetch an organization including custom fields
zendesk_list_custom_statuses List all custom ticket statuses and their IDs

Time tracking

Tool What it does
zendesk_get_time_tracking Read time-tracking entries for a ticket
zendesk_log_time Log a time entry against a ticket

Git-Zen integration

Tool What it does
zendesk_get_git_zen_links (Git-Zen only) Get linked GitLab issues / MRs / commits for a ticket

Prompts

The server exposes two MCP prompts that some clients (e.g. Claude Desktop) surface as slash commands:

Prompt Argument What it does
analyze-ticket ticket_id Asks the model to fetch the ticket and produce a summary, status/timeline, and key interaction points
draft-ticket-response ticket_id Asks the model to fetch the ticket and draft a customer-facing response (with a confirmation step before posting)

Optional: Git-Zen integration

If your Zendesk instance uses the Git-Zen app, the zendesk_get_git_zen_links tool can read its custom-field payload. Find your instance's Git-Zen custom field ID under Admin → Tickets → Fields (it is a numeric ID), then either set it during .venv/bin/python -m zendesk_mcp setup or edit ~/.config/zendesk-mcp/config.json to add:```json
{
"git_zen_field_id": 12345678901234
}


Without this configured, `zendesk_get_git_zen_links` returns a "not configured" message.

## Optional: Help Center knowledge base

If your Zendesk instance has a published Help Center, you can expose its sections and articles as the `zendesk://knowledge-base` MCP resource. The resource returns a single JSON document covering all sections and articles, cached for one hour.

This is opt-in. Enable it by either answering "y" to the prompt during `.venv/bin/python -m zendesk_mcp setup`, or by adding the following to `~/.config/zendesk-mcp/config.json`:```json
{
  "knowledge_base_enabled": true
}

When the flag is absent or false, the resource is not registered, keeping the server's resource list empty for instances without a Help Center.

Optional: downloading attachments outside the cache

zendesk_download_attachment writes files to ~/.cache/zendesk-mcp/attachments// by default (configurable via attachment_cache_dir). The dest_dir argument can redirect a download elsewhere, but because attachment contents are controlled by whoever wrote the ticket, the tool only accepts a dest_dir inside the cache or inside a directory you have explicitly allowed. Add the directories you want to permit to ~/.config/zendesk-mcp/config.json:```json
{
"attachment_allowed_dest_dirs": ["/home/me/work/support_bundles"]
}


Paths are resolved before the check, so `..` segments and symlinks cannot escape an allowed directory. Any `dest_dir` outside the allowed set is refused before the download starts.

The download URL itself must be an `https` URL on `.zendesk.com` for your configured subdomain; the tool refuses anything else so the OAuth token is never sent to another host. Archives are limited to 10,000 entries and 256 MiB unpacked, and tar members that are not regular files or directories are skipped.

## Development```bash
python3 -m venv .venv
.venv/bin/pip install -e ".[dev]"
.venv/bin/pytest

Tests run on Python 3.10, 3.11, and 3.12 in CI (see .github/workflows/test.yml).

Releasing

Bump the version in pyproject.toml, mcpb/pyproject.toml (both the version and
the zendesk-mcp== pin), mcpb/manifest.json, and server.json (both fields),
then push a v* tag. That triggers .github/workflows/release.yml, which publishes
to PyPI, packs the MCPB bundle, publishes server.json to the MCP Registry, and
cuts the GitHub release.

Check the versions agree before tagging — the release fails fast otherwise:bash python3 .github/scripts/check_versions.py 0.1.5

License

Apache-2.0

常见问题

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

在客户端按下面的安装命令接入:uvx zendesk-mcp。装完在客户端配置里引用同一个包或端点。

Zendesk MCP (Michaelrice) 怎么在 Claude 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Zendesk MCP (Michaelrice) 收费吗?

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

Zendesk MCP (Michaelrice) 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Zendesk MCP (Michaelrice) 支持哪些客户端?

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

Zendesk MCP (Michaelrice) 能提供哪些能力?

资料显示能力标签包括 Python、Claude、AI代理。具体工具清单以官方文档为准。

Zendesk MCP (Michaelrice) 需要什么运行环境?

运行时为 Python;属于本地进程,需要在本机装好运行环境。

Zendesk MCP (Michaelrice) 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

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

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