> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rippit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Freshservice MCP server

> Let the Rippit agent read Freshservice tickets, assets, service catalog items, and knowledge base articles alongside everything in Rippit.

Connect Freshservice when a question reaches into your service desk: which open tickets mention a failing laptop model, what asset a requester has assigned, which service catalog item covers an access request, or what the knowledge base says about a recurring issue. The Rippit agent reads Freshservice through Freshworks' MCP server and cites what it finds in its answer.

## What the agent gets

* Tickets: list tickets, filter them by status, priority, dates, and custom fields, and read a ticket.
* Assets: assets, asset types and their fields, products, and vendors.
* Service catalog: categories, items, and item search.
* Knowledge base: solution categories, folders, and articles, with article search.
* People and organization: requesters, agents, agent groups, departments, locations, and workspaces.
* Onboarding and offboarding requests, and custom object records.

## Setup

1. Find your Freshservice subdomain: `acme` in `acme.freshservice.com`. Your MCP server URL is `https://acme.freshservice.com/mcp`. Freshworks does not support custom domains for MCP, so use the `freshservice.com` address even if your service desk has its own domain.
2. In Rippit, go to Connections → MCP Servers, choose Freshservice, and paste the URL. Rippit accepts only a `freshservice.com` host ending in `/mcp`.
3. Pick one of two ways to connect, then click **Connect Freshservice**:
   * **My Freshservice account**: sign in to Freshservice. Rippit registers itself as an OAuth client automatically, so there is no client ID or client secret to create.
   * **Freshservice API key**: in Freshservice, open your profile picture, then **Profile settings**, and copy your API key. Freshservice lists its tools without checking the key, so a mistyped key still connects and the agent's first tool call fails with an authorization error. If that happens, reconnect with the correct key.

Freshworks' own guide is at [Model Context Protocol (MCP) integration in Freshservice](https://support.freshservice.com/support/solutions/articles/50000012678-model-context-protocol-mcp-integration-in-freshservice).

## Identity, scope, and plan limits

Both options act as a Freshservice agent: the one who signed in, or the one the API key belongs to. The Rippit agent sees what that Freshservice agent can see.

A **My Freshservice account** connection is yours alone. An API-key connection is organization-wide, so everyone using the Rippit agent reads with that key. Connect with a key whose access you are comfortable sharing that far.

For who can use the connection, see [Who can use a connection](https://docs.rippit.com/agentic-chat/overview.md#who-can-use-a-connection).

Freshworks meters the MCP server separately from the REST API: every successful tool call is one MCP action, counted against an allowance shared by your whole Freshservice account.

| Freshservice plan | Actions per minute | Included actions per year |
| - | - | - |
| Growth | 25 | 1,200 |
| Pro | 50 | 6,000 |
| Enterprise | 100 | 12,000 |

Other MCP clients connected to the same Freshservice 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](https://docs.rippit.com/agentic-chat/overview.md#setting-one-up).

Freshservice marks its read tools as read-only, and those start enabled. Tool permissions on the server's page lists every tool your connection has.

| Tool | What it does |
| - | - |
| `fetchTickets` / `fetchTicketFilter` / `fetchTicket` | List tickets, filter them by status, priority, dates, and custom fields, and read a ticket |
| `fetchTicketFormFields` | Read the built-in and custom ticket fields |
| `fetchAssets` / `fetchAsset` / `fetchAssetTypes` / `fetchAssetTypeFields` | List and read assets, asset types, and their fields |
| `fetchServiceCatalogCategories` / `fetchServiceCatalogItems` / `fetchServiceCatalogItem` / `fetchServiceCatalogItemSearch` | Browse, read, and search service catalog items |
| `fetchSolutionCategories` / `fetchSolutionCategory` / `fetchSolutionFolders` / `fetchSolutionFolder` / `fetchSolutionArticles` / `fetchSolutionArticle` / `fetchSolutionArticleSearch` | Browse, read, and search knowledge base articles |
| `fetchRequesters` / `fetchRequester` / `fetchAgents` / `fetchAgent` / `fetchGroups` | List and read requesters, agents, and agent groups |
| `fetchDepartments` / `fetchLocations` / `fetchProducts` / `fetchVendors` / `fetchWorkspaces` | List departments, locations, products, vendors, and workspaces |
| `fetchOnboardingRequests` / `fetchOnboardingRequestForm` / `fetchOffboardingRequests` / `fetchOffboardingRequestForm` / `fetchOffboardingRequestTickets` | Read onboarding and offboarding requests and their forms |
| `fetchObjectRecords` | Read records of a custom object |

Tools that change Freshservice start off. They include `replyTicket`, which emails the requester, `placeRequestServiceCatalogItem`, onboarding and offboarding request creation, and tools that create or update tickets, notes, assets, 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.