An MCP server implementation that integrates with Freshdesk, enabling AI models to interact with Freshdesk modules and perform various support
An MCP server implementation that integrates with Freshdesk, enabling AI models to interact with Freshdesk modules and perform various support operations. The freshdesk mcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Everything the assistant can do here goes through one of these:
create_ticket — Create new support ticketsInputs — - subject (string, required): Ticket subjectupdate_ticket — Update existing ticketsdelete_ticket — Delete a ticketsearch_tickets — Search for tickets based on criteriaget_ticket_fields — Get all ticket fieldsget_tickets — Get all ticketsget_ticket — Get a single ticketget_ticket_conversation — Get conversation for a ticketcreate_ticket_reply — Reply to a ticketcreate_ticket_note — Add a note to a ticketupdate_ticket_conversation — Update a conversationYou will need 3 environment variables: FRESHDESK_API_KEY, FRESHDESK_DOMAIN, YOUR_FRESHDESK_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
uvx installed (pip install uv or brew install uv)This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Freshdesk MCP's toolset — create_ticket, Inputs, update_ticket and 11 more — is a fair guide to whether it matches your workflow. It is maintained by effytech; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| create_ticket | Create new support tickets |
| Inputs | - subject (string, required): Ticket subject |
| update_ticket | Update existing tickets |
| delete_ticket | Delete a ticket |
| search_tickets | Search for tickets based on criteria |
| get_ticket_fields | Get all ticket fields |
| get_tickets | Get all tickets |
| get_ticket | Get a single ticket |
| get_ticket_conversation | Get conversation for a ticket |
| create_ticket_reply | Reply to a ticket |
| create_ticket_note | Add a note to a ticket |
| update_ticket_conversation | Update a conversation |
| view_ticket_summary | Get the summary of a ticket |
| update_ticket_summary | Update the summary of a ticket |
{
"mcpServers": {
"freshdesk": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"FRESHDESK_API_KEY": "your-value",
"FRESHDESK_DOMAIN": "your-value",
"YOUR_FRESHDESK_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
uvx installed (pip install uv or brew install uv)| Variable | Description | Required |
|---|---|---|
| FRESHDESK_API_KEY | Credential the server authenticates with. | Yes |
| FRESHDESK_DOMAIN | Configuration value read at startup. | Optional |
| YOUR_FRESHDESK_API_KEY | Credential the server authenticates with. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.