get_ticket_fields is the tool that makes the rest usable: Freshservice instances are heavily customised, and reading the field definitions first means a ticket gets written in the shape your instance expects rather than rejected. The change tools go all the way to close_change, so this is not a read-only view of the queue.
A server over the Freshservice API covering the ticket and change queues. Both sides carry read and write tools, and both accept a query string, so finding the records a question is about is a filter rather than a list-and-scan.
- Tickets created, updated and deleted, with subject, description, source, priority, status and requester email
- Tickets listed with pagination, fetched one at a time by id, or filtered by a query
- The ticket field definitions your instance actually uses
- Change requests created with requester, impact, risk and change type, then updated, closed or deleted
- Changes listed, filtered by query, and fetched by id
- The tasks attached to a change, and notes added to a change record
A Freshservice instance and API access to it — every tool is a call against your own Freshservice endpoints, so what it can reach is what that access allows.
One command plus a key — npx -y @smithery/cli install @effytech/freshservice_mcp --client claude, then supply credentials