Skip to main content
Connect Freshdesk when a question needs the live state of your helpdesk: who a ticket is assigned to right now, what a customer’s company record says, or which knowledge base article covers an issue that keeps coming up. The Rippit agent reads Freshdesk through Freshworks’ MCP server and cites what it finds in its answer. To analyze every ticket in Rippit as a table, use the Freshdesk data integration.

What the agent gets

  • Tickets: search and filter tickets, read a ticket, and read its replies and notes.
  • Contacts and companies: search, autocomplete, and read records.
  • Agents and groups: who works in your helpdesk and how they are organized.
  • Knowledge base: solution categories, folders, and articles.

Setup

Freshworks’ MCP server takes an API key only. There is no Freshdesk sign-in option.
  1. Find your Freshdesk subdomain: acme in acme.freshdesk.com. Your MCP server URL is https://acme.freshdesk.com/mcp. Freshworks does not support custom domains for MCP, so use the freshdesk.com address even if your helpdesk has its own domain.
  2. In Freshdesk, open your profile picture, then Profile settings, then View API key, and copy the key.
  3. In Rippit, go to Connections → MCP Servers, choose Freshdesk, paste the URL and the API key, and click Connect Freshdesk. Rippit accepts only a freshdesk.com host ending in /mcp.
Freshdesk lists its tools without checking the key, so a mistyped key still connects. The agent’s first tool call then fails with an authorization error. If that happens, reconnect with the correct key. Freshworks’ own guide is at Model Context Protocol (MCP) integration in Freshdesk.

Identity, scope, and plan limits

The key acts as the Freshdesk agent it belongs to, so the agent sees what that Freshdesk agent can see. The connection is organization-wide: everyone using the Rippit agent reads with that key. Use a key whose access you are comfortable sharing that far. For who can use the connection, see Who can use a connection. The MCP server works on Freshdesk Standalone 2021 and Freshdesk Unified Omni 2026. Freshworks meters it separately from the REST API: every successful tool call is one MCP action, counted against an allowance shared by your whole Freshdesk account. Other MCP clients connected to the same Freshdesk account draw from the same allowance. Freshworks sells add-on action packs.

Tools

You choose which tools the agent can use under Tool permissions on the server’s page, one at a time or a whole group at once. See Setting one up. Freshdesk marks its read tools as read-only, and those start enabled. Tool permissions on the server’s page lists every tool your connection has. Tools that change Freshdesk start off. They include replyTicket, which emails the customer, createTicketBulkUpdate, and tools that create or update tickets, notes, contacts, companies, agents, groups, and knowledge base articles. start_conversation only issues an ID that other tools accept optionally, and it also starts off. Turn a tool on in Tool permissions only if you want the agent to take that action.