Freshdesk

io.github.mindstonePublished by GitHub account mindstonev0.3.1Updated Oct 24, 2026

Freshdesk Support MCP server for Model Context Protocol hosts

VerifiedSTDIODesktop onlyKnowledge & MemoryBusiness & Commerce

Overview

AI-generated overview

Lets an assistant manage Freshdesk helpdesk accounts, tickets, contacts, companies, and knowledge base articles through a local MCP server.

What you can do
Provides 20 tools covering Freshdesk support workflows: connecting and listing accounts, listing, searching, creating, updating, and replying to tickets, adding public or private notes, and discovering ticket fields, agents, and groups. It also lists and searches contacts and companies, and searches or fetches knowledge base solution articles. Returned Freshdesk text is wrapped in untrusted-content envelopes so the host treats it as data.
When to use it
Useful when an assistant should work with a Freshdesk helpdesk: triaging and filtering tickets, drafting replies or internal notes, looking up customer contacts and companies, or pulling knowledge base articles for support answers.
Requirements
Runs locally over stdio via npx (npm package @mindstone/mcp-server-freshdesk) and needs Node.js 20+ and npm. A Freshdesk account subdomain and API key are entered through the configure_freshdesk tool and stored on disk under the directory given by FRESHDESK_CONFIG_PATH (default ~/.mcp/freshdesk). Optional MCP_HOST_BRIDGE_STATE (alias MINDSTONE_REBEL_BRIDGE_STATE) points to a host bridge state file. Desktop host only.
Before you install
The server stores Freshdesk API keys in accounts.json under FRESHDESK_CONFIG_PATH, so protect that directory. Several tools write to the helpdesk: creating and updating tickets, sending public replies to customers, and adding notes; remove_freshdesk_account disconnects an account. Ticket, contact, and company data is sent to the Freshdesk API.

Installation

In SourceWeft

  1. Open Freshdesk 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

@mindstone/mcp-server-freshdesk

[npm version] [License: FSL-1.1-MIT]

Freshdesk Support MCP server for Model Context Protocol hosts. Manage helpdesk tickets, search and filter support requests, reply to customers, add internal notes, and configure Freshdesk accounts — all through a standardised MCP interface.

Status

  • Version: 0.3.1 · npm
  • Auth: API key (per-account, on disk via FRESHDESK_CONFIG_PATH)
  • Tools: 20 (accounts, tickets, contacts, companies, knowledge base, discovery)
  • Surface: cloud-api
  • Machine-readable: STATUS.json

Requirements

  • Node.js 20+
  • npm

One-click install

[Add to Cursor] [Add to VS Code] [Add to VS Code Insiders]

After clicking the button, your host will prompt you to fill: FRESHDESK_CONFIG_PATH.

Manual config for Claude Desktop / Claude Code / Goose / Continue.dev (Freshdesk)
json
{  "mcpServers": {    "Freshdesk": {      "command": "npx",      "args": [        "-y",        "@mindstone/mcp-server-freshdesk"      ],      "env": {        "FRESHDESK_CONFIG_PATH": "~/.mcp/freshdesk"      }    }  }}

Quick Start

Install & build

bash
cd <path-to-repo>/connectors/freshdesknpm installnpm run build

npx (once published)

bash
npx -y @mindstone/mcp-server-freshdesk

Local

bash
node dist/index.js

Configuration

Environment variables

  • FRESHDESK_CONFIG_PATH — path to the config directory that stores account credentials (defaults to ~/.mcp/freshdesk)
  • MCP_HOST_BRIDGE_STATE — optional path to a host bridge state file used for credential management
  • MINDSTONE_REBEL_BRIDGE_STATE — backwards-compatible alias for MCP_HOST_BRIDGE_STATE

Host configuration examples

Claude Desktop / Cursor

json
{  "mcpServers": {    "Freshdesk": {      "command": "npx",      "args": ["-y", "@mindstone/mcp-server-freshdesk"],      "env": {        "FRESHDESK_CONFIG_PATH": "~/.mcp/freshdesk"      }    }  }}

Local development (no npm publish needed)

json
{  "mcpServers": {    "Freshdesk": {      "command": "node",      "args": ["<path-to-repo>/connectors/freshdesk/dist/index.js"],      "env": {        "FRESHDESK_CONFIG_PATH": "~/.mcp/freshdesk"      }    }  }}

Tools (20)

Account management

  • configure_freshdesk — Connect a Freshdesk account using subdomain and API key
  • list_freshdesk_accounts — List connected Freshdesk accounts with agent emails
  • remove_freshdesk_account — Disconnect a Freshdesk account

Tickets

  • list_freshdesk_tickets — List tickets using predefined filters
  • get_freshdesk_ticket — Get a single ticket by ID with optional conversations
  • search_freshdesk_tickets — Search tickets using Freshdesk query syntax
  • create_freshdesk_ticket — Create a new ticket
  • update_freshdesk_ticket — Update ticket fields, status, or assignee
  • reply_to_freshdesk_ticket — Add a public reply to a ticket
  • add_freshdesk_note — Add a private or public note to a ticket

Discovery

  • list_freshdesk_ticket_fields — List all ticket fields including custom fields
  • list_freshdesk_agents — List agents (support staff); use the IDs as responder_id when assigning tickets
  • list_freshdesk_groups — List groups (agent teams); use the IDs as group_id when assigning tickets

Contacts & companies

  • list_freshdesk_contacts — List contacts, optionally filtered by exact email or company ID
  • search_freshdesk_contacts — Search contacts using Freshdesk query syntax
  • get_freshdesk_contact — Get a single contact by ID
  • list_freshdesk_companies — List customer organisations
  • get_freshdesk_company — Get a single company by ID

Knowledge base

  • search_freshdesk_solutions — Search solution articles by keyword (paginated: 30 per page, page parameter, hasMore indicator)
  • get_freshdesk_solution_article — Get a full solution article by ID

Security

  • Every string returned by the Freshdesk API (names, bodies, tags, emails, phone numbers, company domains, custom-field keys/values, ticket-field metadata, …) is wrapped in <untrusted-content source="…"> envelopes so the host LLM treats it as data, not instructions. Only numeric connector metadata (IDs, statuses, priorities) is returned raw.
  • Credentials are stored in accounts.json under FRESHDESK_CONFIG_PATH with 0600 permissions (config directory 0700).
  • Vendor error bodies, raw Retry-After header text, and query-bearing URLs are never written to logs or surfaced in tool errors.
  • Invalid status/priority values and out-of-range IDs/pagination inputs are rejected before any request is made.

Licence

FSL-1.1-MIT — Functional Source License, Version 1.1, with MIT future licence. The software converts to MIT licence on 2030-04-08.

Source: connectors/freshdesk/README.md at commit 22c4611

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.1LatestSep 16, 2026

Score

40% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.