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.
A server that integrates with the Freshdesk support desk API, exposing tools across tickets, ticket conversations and summaries, agents, contacts and companies.
- 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
A Freshdesk API key and your Freshdesk domain (e.g. yourcompany.freshdesk.com), set as FRESHDESK_API_KEY and FRESHDESK_DOMAIN. The uv package manager; run it as uvx freshdesk-mcp.
One command plus a key — uvx freshdesk-mcp, then supply credentials