Helpdesk Mender Mcp

io.github.headlessherm-creator由 GitHub 账号 headlessherm-creator 发布v0.1.0更新于 Oct 30, 2026

Local MCP server: Zendesk + Freshdesk + Help Scout write tools, one vocabulary.

已验证STDIO仅桌面沟通与协作商业与电商

概览

AI 生成的概览

本地 MCP 服务器,让助手用同一套工具在 Zendesk、Freshdesk 和 Help Scout 中创建工单、回复、添加内部备注和修改状态。

可以做什么
  • 在 Freshdesk、Zendesk 或 Help Scout 上创建工单或会话,字段按各平台要求填写
  • 添加客户可见的公开回复
  • 添加仅内部可见的私密备注(Freshdesk 与 Help Scout;Zendesk 需改用非公开回复)
  • 按各平台自身的状态取值修改工单或会话状态
  • 列出某个平台的工单或会话
适用场景
适合需要让助手在 Zendesk、Freshdesk、Help Scout 中的一个或多个平台上处理客服工单,而不想为各家不同的认证方式和字段名分别编写集成的场景。
运行要求
需要 Node.js v18 或更高版本,并在本地克隆仓库后用 npm 安装;客户端需指向服务器的入口脚本。凭据通过环境变量提供:FRESHDESK_DOMAIN 与 FRESHDESK_API_KEY,ZENDESK_SUBDOMAIN、ZENDESK_EMAIL 与 ZENDESK_API_TOKEN,或 HELPSCOUT_APP_ID 与 HELPSCOUT_APP_SECRET;只需设置所用平台对应的变量。需要能访问各客服平台的 API。
安装前请注意
服务器会使用你提供的凭据向客服平台发起真实网络请求,工单数据会离开本机。五个工具都会写入:创建工单、发布客户可见的回复、添加备注和修改状态,可能通知客户或改变客服队列。请妥善保管 FRESHDESK_API_KEY、ZENDESK_API_TOKEN 和 HELPSCOUT_APP_SECRET。Freshdesk 免费版 API 调用上限为零,API 访问需付费套餐。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Helpdesk Mender Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

Helpdesk Mender MCP — Zendesk, Freshdesk & Help Scout Write Tools for AI Agents

A free, local MCP server that creates tickets, adds replies and notes, and changes ticket status in Zendesk, Freshdesk, and Help Scout — one consistent tool vocabulary across all three, so you don't hand-roll three different helpdesk integrations.

If you're building an AI support workflow and keep rewriting the same ticket-creation/reply logic for Zendesk's Basic/OAuth auth, Freshdesk's API-key auth, and Help Scout's OAuth2 client-credentials flow, this is the MCP server for that exact problem.

The problem this solves

Zendesk, Freshdesk, and Help Scout all have solid write-capable ticketing APIs, but each uses a different auth scheme, different field names, and a different notion of what a "ticket" even is (Help Scout calls it a "conversation"). There is no free, open-source tool that normalizes all three behind one set of calls. This is that tool.

Tools

  • create_ticket — create a new ticket/conversation.
  • add_reply — add a public reply, visible to the customer.
  • add_note — add a private, internal-only note (Freshdesk and Help Scout; Zendesk has no separate note endpoint — use add_reply with a non-public comment on that platform directly).
  • update_status — change ticket/conversation status.
  • list_tickets — list tickets/conversations.

Setup

1. Install Node.js (v18+): https://nodejs.org

2. Clone and install:

bash
git clone https://github.com/headlessherm-creator/helpdesk-mender-mcp.gitcd helpdesk-mender-mcpnpm install

3. Get API credentials for the platform(s) you use:

  • Freshdesk: Get your API key from Profile Settings. Important: Freshdesk's free plan has a 0 calls/minute API rate limit — API access requires a paid plan (Growth or above). See Freshdesk's API docs.
  • Zendesk: Create an API token under Admin Center → Apps and integrations → APIs → Zendesk API, or use OAuth. See Zendesk's API docs.
  • Help Scout: Create an OAuth2 app under Your Profile → My Apps, using the Client Credentials flow. Note: Help Scout's client-credentials tokens expire after 48 hours and have no refresh token — this server automatically re-requests a new token when the cached one expires, so you don't need to handle that yourself. See Help Scout's auth docs.

4. Set environment variables:

bash
export FRESHDESK_DOMAIN=yourcompanyexport FRESHDESK_API_KEY=your_api_keyexport ZENDESK_SUBDOMAIN=yourcompanyexport [email protected]export ZENDESK_API_TOKEN=your_api_tokenexport HELPSCOUT_APP_ID=your_app_idexport HELPSCOUT_APP_SECRET=your_app_secret

You only need to set the variables for the platform(s) you're using.

5. Point your MCP client at it:

json
{  "mcpServers": {    "helpdesk-mender": {      "command": "node",      "args": ["/path/to/helpdesk-mender-mcp/src/index.js"],      "env": {        "FRESHDESK_DOMAIN": "yourcompany",        "FRESHDESK_API_KEY": "your_api_key"      }    }  }}

Setup docs for common clients:

Security note

This server makes real network calls to Zendesk's, Freshdesk's, and Help Scout's APIs using the credentials you provide — unlike a fully local tool, your data does leave your machine, going directly to the helpdesk vendor you're already using. No third party, telemetry, or logging is involved.

Keywords

Zendesk MCP server, Freshdesk MCP server, Help Scout MCP server, helpdesk MCP server, support ticket automation MCP, customer support AI agent, ticketing system MCP, Claude MCP support tools.

Related tools

Same local-first philosophy, different problems:

License

MIT

来源:README.md,提交 4ae0d19

工具

5

create_ticket

Create a new ticket/conversation. Freshdesk: subject, description, email. Zendesk: subject, comment (string or {body}), requesterEmail. Help Scout: subject, customerEmail, customerFirstName, customerLastName, mailboxId, text (Help Scout calls this a 'conversation', not a ticket).

输入参数ticket必填platform必填

add_reply

Add a public reply (visible to the customer) to an existing ticket/conversation. Freshdesk: ticketId, body. Zendesk: ticketId, body (adds as a public comment). Help Scout: conversationId, text.

输入参数bodytextplatform必填ticketIdconversationId

add_note

Add a private, internal-only note (not visible to the customer). Freshdesk: ticketId, body. Zendesk: use add_reply with isPublic=false instead (Zendesk has no separate note endpoint). Help Scout: conversationId, text (uses isPublic=false).

输入参数bodytextplatform必填ticketIdconversationId

update_status

Change a ticket/conversation's status. Freshdesk status codes: 2=Open, 3=Pending, 4=Resolved, 5=Closed. Zendesk: 'new', 'open', 'pending', 'hold', 'solved', 'closed'. Help Scout: 'active', 'pending', 'closed', 'spam'.

输入参数status必填platform必填ticketIdconversationId

list_tickets

List tickets/conversations for a platform.

输入参数platform必填mailboxId

版本历史

1
  1. v0.1.0最新Oct 22, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分