create_ticketLABSCO SUMMARY
The whole support desk, ticket to company record.
It reaches past tickets into the objects around them — agents, contacts and companies — so an assistant can answer 'who is this requester and what have they raised before' without leaving the tool. get_ticket_fields is the quiet enabler: reading the field definitions first means a created ticket carries the priority, status and custom fields your instance actually expects.
What it is
A server that integrates with the Freshdesk support desk API, exposing tools across tickets, ticket conversations and summaries, agents, contacts and companies.
What you get
- Tickets end to end: create_ticket with subject, description, source, priority and status, update_ticket, delete_ticket, get_ticket, get_tickets with pagination, and search_tickets by query
- get_ticket_fields returns the fields your Freshdesk defines, so a create or update uses valid values rather than guesses
- Conversations and replies: get_ticket_conversation reads the thread, create_ticket_reply sends an outgoing reply (with optional cc_emails on top of the requester), create_ticket_note adds an internal note, and update_ticket_conversation edits one
- Ticket summaries handled separately — view_ticket_summary, update_ticket_summary and delete_ticket_summary
- Agents managed: get_agents, view_agent, create_agent, update_agent and search_agents
- Contacts and companies: list_contacts, get_contact, search_contacts and update_contact, plus list_companies, view_company, search_companies, find_company_by_name and list_company_fields
Requirements
A Freshdesk API key and your Freshdesk domain (<YOUR_COMPANY>.freshdesk.com), set as FRESHDESK_API_KEY and FRESHDESK_DOMAIN. The uv package manager; run it as uvx freshdesk-mcp.
Setup effort
One command plus a key — uvx freshdesk-mcp, then supply credentials
USE CASES
Logging and routing a new ticket
Read the ticket fields to get valid priority and status codes, create the ticket with the requester's details, and confirm it landed.
Working an open ticket
Read the conversation so far, send a reply to the requester, and drop an internal note for the next agent.
Finding tickets that need attention
Search tickets by criteria, page through the matches, and open the ones that matter to act on them.
Looking up who raised it
Find the contact and their company, check the company's record, and see the agent assigned so you know who owns the case.
28 tools
Listed in project docs. Your client may show a different list.
update_ticketdelete_ticketsearch_ticketsget_ticket_fieldsget_ticketsget_ticketget_ticket_conversationcreate_ticket_replycreate_ticket_noteupdate_ticket_conversationview_ticket_summaryupdate_ticket_summarydelete_ticket_summaryget_agentsview_agentcreate_agentupdate_agentsearch_agentslist_contactsget_contactsearch_contactsupdate_contactlist_companiesview_companysearch_companiesfind_company_by_namelist_company_fieldsBEFORE YOU INSTALL
What to know first
Tools you get
28 tools named in the project's documentation.
Requires
- uvx on PATH
- FRESHDESK_API_KEY in your environment
- FRESHDESK_DOMAIN in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
uvx freshdesk-mcpMCP Clients
Claude Desktop
{
"mcpServers": {
"freshdesk-mcp": {
"command": "uvx",
"args": [
"freshdesk-mcp"
],
"env": {
"FRESHDESK_API_KEY": "<YOUR_FRESHDESK_API_KEY>",
"FRESHDESK_DOMAIN": "<YOUR_FRESHDESK_DOMAIN>"
}
}
}
}