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 分