Log inSubmit server
Freshdesk logo

Freshdesk

Connects AI assistants to Freshdesk for ticket, customer, team, knowledge base, and SLA operations.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Freshdesk

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "freshdesk-3": {
      "command": "npx",
      "args": [
        "-y",
        "github:WYRE-AI/freshdesk-mcp"
      ],
      "env": {
        "FRESHDESK_DOMAIN": "YOUR_VALUE_HERE",
        "FRESHDESK_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

The install command didn't complete successfully in our automated test.

npx -y github:WYRE-AI/freshdesk-mcp

Run `npm install -g npm@12.2.0` to update! npm notice npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/@wyre-technology%2fnode-freshdesk - Not found npm ERR! 404 npm ERR! 404 '@wyre-technology/node-freshdesk@^1.0.0' is not in this registry. npm ERR! 404 npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, http url, or git url. npm ERR! A complete log of this run can be found in: /home/user/.npm/_logs/2026-10-19T12_51_31_528Z-debug-0.log

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 4d ago.

Overview

The Freshdesk MCP server connects AI assistants to Freshdesk through tools for tickets, contacts, companies, agents, groups, solutions, SLAs, business hours, and canned responses. It supports local stdio use and remote Streamable HTTP deployments, with API-key authentication based on the Freshdesk subdomain and key. Decision-tree navigation reveals tools by domain, keeping discovery focused. Reach for it when an agent needs to inspect or manage Freshdesk support data, with confirmations for destructive and high-impact actions.

Use cases

  • Search and update support tickets
  • Create and manage Freshdesk contacts
  • Maintain companies, agents, and groups
  • Edit knowledge base articles and folders
  • Inspect SLA policies and business hours

Key features

  • Decision-tree tool navigation
  • Ticket and conversation management
  • Contact, company, agent, and group operations
  • Knowledge base and solution management
  • SLA, business-hours, and canned-response access
  • Confirmation prompts for destructive actions

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

7/7 checks healthy over the last 45d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · github:WYRE-AI/freshdesk-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit4d agoMost recent push to the default branch.
Install checkInconclusiveInstall command did not finish in our automated test.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Freshdesk works

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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Freshdesk

Freshdesk is an MCP server that connects AI assistants to the Freshdesk customer support platform through tools for tickets, contacts, companies, agents, groups, solutions, SLA policies, business hours, and canned responses. It supports searching, reading, creating, updating, replying, and selected lifecycle operations.

Install it with `npx` through an MCP client such as Claude Code, supplying `FRESHDESK_DOMAIN` and `FRESHDESK_API_KEY` as environment variables. The documented command retrieves the server from the GitHub repository, while Docker Compose is available for HTTP deployments.

It needs the Freshdesk account subdomain and an API key. Set them as `FRESHDESK_DOMAIN` and `FRESHDESK_API_KEY`; the key is obtained from Freshdesk Profile Settings. Gateway deployments can provide the same values through `x-freshdesk-domain` and `x-freshdesk-api-key` headers.

The server supports standard stdio and Streamable HTTP transports, so compatibility depends on whether the client supports the corresponding MCP transport and configuration.

Related MCP servers

All in Support & Service Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewFreshdesk AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/freshdesk-3?style=directory)](https://allmcps.com/mcp/freshdesk-3)
HTML Embed
<a href="https://allmcps.com/mcp/freshdesk-3"><img src="https://allmcps.com/api/badge/freshdesk-3?style=directory" alt="Freshdesk on AllMCPs" /></a>