Helpdesk Mender Mcp

io.github.headlessherm-creatorPublished by GitHub account headlessherm-creatorv0.1.0Updated Oct 30, 2026

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

Overview

AI-generated overview

Local MCP server that lets an assistant create tickets, reply, add private notes and change status in Zendesk, Freshdesk and Help Scout through one shared…

What you can do
  • Create tickets or conversations on Freshdesk, Zendesk or Help Scout with platform-specific fields
  • Add public replies visible to the customer
  • Add private internal notes (Freshdesk and Help Scout; on Zendesk use a non-public reply)
  • Change ticket or conversation status using each platform's own status values
  • List tickets or conversations for a platform
When to use it
Useful when an assistant should handle support tickets across one or more of Zendesk, Freshdesk and Help Scout without writing separate integrations for each vendor's auth scheme and field names.
Requirements
Node.js v18 or later and a local clone of the repository installed with npm; the client is pointed at the server's entry script. Credentials are supplied as environment variables: FRESHDESK_DOMAIN and FRESHDESK_API_KEY, ZENDESK_SUBDOMAIN, ZENDESK_EMAIL and ZENDESK_API_TOKEN, or HELPSCOUT_APP_ID and HELPSCOUT_APP_SECRET; only the variables for the platforms in use are needed. Network access to the helpdesk APIs is required.
Before you install
The server makes real network calls to the helpdesk vendors with the credentials you provide, so ticket data leaves your machine. All five tools write: they create tickets, post customer-visible replies, add notes and change status, which can notify customers or alter support queues. Store FRESHDESK_API_KEY, ZENDESK_API_TOKEN and HELPSCOUT_APP_SECRET carefully. Freshdesk API access requires a paid plan, since the free plan has a zero calls-per-minute limit.

Installation

In SourceWeft

  1. Open Helpdesk Mender Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

Source: README.md at commit 4ae0d19

Tools

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).

Parametersticketrequiredplatformrequired

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.

ParametersbodytextplatformrequiredticketIdconversationId

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).

ParametersbodytextplatformrequiredticketIdconversationId

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'.

ParametersstatusrequiredplatformrequiredticketIdconversationId

list_tickets

List tickets/conversations for a platform.

ParametersplatformrequiredmailboxId

Version history

1
  1. v0.1.0LatestOct 22, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts