Freshdesk MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Freshdesk MCP Server Get details of ticket 12345"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Freshdesk MCP Server
A Model Context Protocol (MCP) server that fetches Freshdesk ticket details and provides them as context for LLM interactions.
Features
get_ticket - Fetch complete ticket details from a Freshdesk URL or ticket ID
Ticket metadata (subject, status, priority, type, tags)
Requester and assignee information
All conversations (replies and private notes)
Attachments list
Time entries
Satisfaction ratings
Custom fields
search_tickets - Search tickets by text query
Filter by status (open, pending, resolved, closed)
Filter by priority (low, medium, high, urgent)
Configurable result limit
get_agent_tickets - Get tickets assigned to a specific agent
Search by agent name (supports partial matching)
Filter by status
Configurable result limit
Related MCP server: Freshdesk MCP Server
Installation
Using npx (Recommended)
No installation required. Add directly to your config:
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"freshdesk": {
"command": "npx",
"args": ["-y", "github:nikhilchintawar/freshdesk-mcp"],
"env": {
"FRESHDESK_API_KEY": "your-api-key",
"FRESHDESK_DOMAIN": "yourcompany"
}
}
}
}Claude Code (~/.claude/settings.json):
{
"mcpServers": {
"freshdesk": {
"command": "npx",
"args": ["-y", "github:nikhilchintawar/freshdesk-mcp"],
"env": {
"FRESHDESK_API_KEY": "your-api-key",
"FRESHDESK_DOMAIN": "yourcompany"
}
}
}
}Manual Installation
# Clone the repository
git clone https://github.com/nikhilchintawar/freshdesk-mcp.git
cd freshdesk-mcp
# Install dependencies
npm installThen add to your config:
{
"mcpServers": {
"freshdesk": {
"command": "node",
"args": ["/absolute/path/to/freshdesk-mcp/build/index.js"],
"env": {
"FRESHDESK_API_KEY": "your-api-key",
"FRESHDESK_DOMAIN": "yourcompany"
}
}
}
}Configuration
Config File Locations
Claude Desktop (macOS):
~/Library/Application Support/Claude/claude_desktop_config.jsonClaude Desktop (Windows):
%APPDATA%\Claude\claude_desktop_config.jsonClaude Code:
~/.claude/settings.json
Environment Variables
Variable | Description | Required |
| Your Freshdesk API key | Yes |
| Your Freshdesk subdomain (e.g., | Yes |
Usage Examples
Once configured, you can use natural language to interact with Freshdesk:
"Get the details of ticket https://mycompany.freshdesk.com/a/tickets/12345"
"Search for tickets about 'login issue'"
"Show me all open tickets assigned to John"
"Find high priority tickets related to billing"
Getting Your Freshdesk API Key
Log in to your Freshdesk account
Click on your profile icon → Profile Settings
Your API key is displayed on the right side of the page
Development
# Watch mode for development
npm run dev
# Build for production
npm run build
# Test with MCP Inspector
FRESHDESK_API_KEY=your-key FRESHDESK_DOMAIN=your-domain \
npx @modelcontextprotocol/inspector node build/index.jsLicense
MIT
Available Tools
3 toolsget_agent_ticketsB
Get tickets assigned to a specific Freshdesk agent by name. Supports partial name matching.
Inputs: agent_name (required), limit, status.
get_ticketA
Fetch complete ticket details from Freshdesk including conversations, attachments, time entries, and satisfaction ratings. Accepts a ticket URL or ID.
Inputs: ticket (required).
search_ticketsB
Search Freshdesk tickets by text query. Can filter by status and priority.
Inputs: query (required), limit, status, priority.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool targets a distinct operation: fetching by agent, fetching by ID/URL, and searching by text query. There is no overlap in purpose.
All tool names follow a consistent verb_noun pattern using snake_case (get_agent_tickets, get_ticket, search_tickets).
Three tools is on the low side but still within the typical 3-15 range and each tool serves a clear read-focused purpose for the domain.
Only read operations are covered; missing create, update, and delete functionalities that are essential for managing tickets in a CRM system.
Maintenance
Related MCP Connectors
Search tickets, people, organizations and KB articles in Deskpro, and create tickets and replies.
Read tickets, contacts, companies, agents and groups; create, update and reply to tickets.
Ask questions about your support tickets, chats, agents and AI answer quality, with cited tickets.
Manage tickets, run agents and workflows, query tables, and search workspace knowledge.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with Zendesk ticket data for customer support analysis and insights. It supports searching tickets by tags or keywords, retrieving ticket details, and analyzing agent performance and service trends.-
- AlicenseBqualityCmaintenanceEnables AI agents to interact with Freshdesk, supporting ticket management, customer and company operations, agent lookup, and knowledge base search through natural language.19MIT
- AlicenseNot gradedqualityBmaintenanceEnables ticket and contact management via Freshdesk API v2, including listing, searching, and retrieving support tickets and customer contacts.146 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to securely list, retrieve, and search Freshdesk support tickets through typed read-only MCP tools. It supports API-key authentication, rate-limit handling, safe logging, and an offline fictional demo mode.-