# Freshdesk [Health: Active]

**Category:** 🎧 Support & Service Management  
**Repository:** https://github.com/WYRE-AI/freshdesk-mcp  
**GitHub Stars:** 0  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/freshdesk

## Description
MCP server for Freshdesk — tickets, contacts, companies, agents, groups, and knowledge base.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "freshdesk": {
    "command": "npx",
    "args": ["-y","github:WYRE-AI/freshdesk-mcp"],
    "env": {
      "FRESHDESK_DOMAIN": "",
      "FRESHDESK_API_KEY": "",
      "MCP_TRANSPORT": "",
      "MCP_HTTP_PORT": "",
      "AUTH_MODE": "",
      "LOG_LEVEL": ""
    }
  }
}
```

**Requires environment variables:** `FRESHDESK_DOMAIN`, `FRESHDESK_API_KEY`, `MCP_TRANSPORT`, `MCP_HTTP_PORT`, `AUTH_MODE`, `LOG_LEVEL` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the Freshdesk MCP server does

The Freshdesk MCP server connects an MCP-compatible AI assistant to the Freshdesk customer support platform. It covers operational records such as tickets, contacts, companies, agents, and groups, along with solutions content, SLA policies, business hours, and canned responses.

The server supports both read and write workflows. Assistants can search, list, and retrieve records, then create or update supported resources. Ticket workflows include replies, notes, conversation access, and conversation updates. The available operations depend on the domain selected through the server’s navigation flow.

## How it works

The Freshdesk MCP server starts with a small top-level tool set: navigation, back navigation, and status. Calling `freshdesk_navigate` with a domain exposes the tools for that area; `freshdesk_back` returns to the top level. This keeps domain-specific operations out of the active tool list until they are needed.

Authentication uses HTTP Basic Auth with a Freshdesk API key. The account is identified by its subdomain, such as `acme` for `acme.freshdesk.com`. `freshdesk_status` checks connectivity by calling the Freshdesk `agents/me` endpoint.

The server can run over stdio for local use or Streamable HTTP for remote, Docker, and gateway deployments. With the WYRE MCP Gateway, credentials arrive in request headers and each request is handled statelessly. The server can also expose its tool list before credentials are available.

## Setup and configuration

For a local Claude Code setup, register the server with `FRESHDESK_DOMAIN` and `FRESHDESK_API_KEY`, using the repository’s `npx` command. The API key is obtained from Freshdesk Profile Settings. Node.js 18 or newer is required.

Configuration variables include:

- `FRESHDESK_DOMAIN`: Freshdesk account subdomain.
- `FRESHDESK_API_KEY`: Freshdesk API key.
- `MCP_TRANSPORT`: `stdio` or `http`; defaults to `stdio`.
- `MCP_HTTP_PORT`: HTTP port; defaults to `8080`.
- `AUTH_MODE`: `env` or `gateway`; defaults to `env`.
- `LOG_LEVEL`: `debug`, `info`, `warn`, or `error`; defaults to `info`.

Docker deployment is supported through the included Compose configuration. The documented image build uses a BuildKit npmrc secret to install the private SDK dependency without baking the credential into an image layer.

## Tools and capabilities

Supported domains and representative operations are:

- Tickets: search, list, retrieve, create, update, reply, notes, and conversations.
- Contacts: search, list, retrieve, create, update, autocomplete, invitations, and account actions.
- Companies, agents, and groups: list, retrieve, create, update, and supported deletion operations.
- Solutions: manage categories, folders, and articles.
- SLA and business settings: manage SLA policies, inspect business hours, and read canned-response folders and responses.

Deletion tools are marked as irreversible and require confirmation. High-impact reversible actions, such as selected contact operations, also require confirmation. Read-only tools do not display these warnings.

## Limitations and notes

The available tools are intentionally not all visible at startup; assistants must navigate into a domain first. Freshdesk access depends on a valid account subdomain and API key, and gateway deployments require the gateway to provide the expected credential headers. The project wraps the published `@wyre-technology/node-freshdesk` SDK, so supported behavior follows the capabilities exposed by that integration.

_Full upstream README: https://allmcps.com/mcp/freshdesk/readme_