# Freshdesk [Health: Active]

**Category:** 🎧 Support & Service Management  
**Repository:** https://github.com/wyre-technology/freshdesk-mcp  
**GitHub Stars:** 0  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/freshdesk-3

## 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": ""
    }
  }
}
```

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

## Documentation

## What Freshdesk MCP server does

The Freshdesk MCP server exposes structured access to a Freshdesk customer support account through the Model Context Protocol. It covers operational support records and configuration, including tickets, contacts, companies, agents, groups, solution categories, folders, articles, SLA policies, business hours, and canned responses.

Read operations include searching, listing, retrieving, autocompleting, and checking connection status. Write operations can create or update supported records, reply to tickets, add notes, manage conversations, send contact invitations, and maintain knowledge base content. Some resources also support deletion, restoration, merging, or conversion of contacts.

## How it works

The Freshdesk MCP server uses a decision-tree tool layout. At the top level, an assistant sees `freshdesk_navigate`, `freshdesk_back`, and `freshdesk_status`. Calling `freshdesk_navigate` with a supported domain exposes that domain's tools; `freshdesk_back` returns to the top level. This approach limits the active tool list while preserving access to the available Freshdesk areas.

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

Destructive deletes are marked as irreversible and require confirmation through MCP elicitation. High-impact but reversible actions, such as selected contact operations, are also flagged and require confirmation. Read-only tools do not display these warnings.

## Setup and configuration

The documented local setup uses Claude Code with `npx` and two required environment variables:

- `FRESHDESK_DOMAIN`: the Freshdesk account subdomain.
- `FRESHDESK_API_KEY`: the API key from Freshdesk Profile Settings.

The server defaults to stdio transport. Set `MCP_TRANSPORT=http` for Streamable HTTP, and use `MCP_HTTP_PORT` to change the default port of `8080`. `AUTH_MODE` selects environment-based or gateway-based authentication, defaulting to `env`; `LOG_LEVEL` controls logging and defaults to `info`.

For gateway deployments, requests can provide the domain and API key through `x-freshdesk-domain` and `x-freshdesk-api-key` headers. Docker Compose deployment uses a `.env` file containing the Freshdesk credentials. The project requires Node.js 18 or newer.

## Tools and capabilities

After navigating to a domain, available operations include:

- Tickets: search, list, get, create, update, reply, add notes, and manage conversations.
- Contacts, companies, agents, and groups: retrieve, create, update, list, and supported lifecycle actions.
- Solutions: manage categories, folders, and articles.
- SLA and business configuration: manage SLA policies, inspect business hours, and read canned response folders and responses.
- Connectivity: verify access with `freshdesk_status`.

## Limitations and notes

The tool list is intentionally not fully visible at the top level; assistants must navigate into a domain before using its operations. Gateway authentication is request-based and stateless: credentials are supplied by the gateway and the Freshdesk client is rebuilt for each request. Irreversible and high-impact tools cannot run without confirmation. Docker builds require access to the published `@wyre-technology/node-freshdesk` package through GitHub Packages. The project is licensed under Apache 2.0.

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