Freshworks MCP

Freshworks builds the Freshdesk support desk, the Freshservice IT service desk, and a CRM line, and its MCP server puts those workspaces behind the Model Context Protocol so an AI client can read and act on them. Support and IT work is mostly retrieval followed by a small write, and that is the shape the server fits: find the ticket, read the thread, check the requester's history, then reply or change a field. What is exposed follows the product. On the support desk side an agent works with tickets and their conversations, contacts and companies, agents and groups, and the knowledge base articles used to answer repeat questions. On the service desk side it reaches ITSM objects: requesters, assets and the configuration database, service catalog items, onboarding and offboarding requests, problems and changes, and workspaces. Writes cover creating a ticket, adding a public reply or a private note, and changing status, priority, assignment, or custom fields. It suits support and IT teams that want triage assistance grounded in their own queue rather than generic advice. Access follows the connected account, so an agent inherits the permissions of the user or API key it authenticates with, which is how teams keep it out of tickets and workspaces it has no business touching.