Sign in Book a demo
Back to Tools
Customer Support API Key
Build Your Agent View Freshdesk Documentation
freshdesk logo

Freshdesk MCP Tools for AI Agents

Let an agent search tickets, read customer history, find answers, route issues, add private notes, and reply to customers in Freshdesk.

Available Tools

19 tools available in this integration

Freshdesk.AddPrivateNote

Add an internal private note to a ticket that the requester cannot see.

Freshdesk.CreateOrUpdateCompany

Create a new company account or update an existing one.

Freshdesk.CreateOrUpdateContact

Create a new contact or update an existing one.

Freshdesk.CreateTicket

Open a ticket on a customer's behalf.

Freshdesk.GetArticle

Read a single knowledge base article's full content by id.

Freshdesk.GetCompany

Read a single company's details by id.

Freshdesk.GetContact

Read a single contact's details by id.

Freshdesk.GetCustomerOverview

Assemble one requester's full context — their contact record, their company, and their

Freshdesk.GetTicket

Read a ticket together with its full public-reply and private-note history.

Freshdesk.ListAgents

List the helpdesk's agents, optionally filtered to one email, for routing tickets.

Freshdesk.ListGroups

List the helpdesk's groups for routing tickets to a team.

Freshdesk.MergeTickets

Merge duplicate tickets into one.

Freshdesk.ReplyToTicket

Post a public reply on a ticket that the requester can see.

Freshdesk.SearchArticles

Search the knowledge base for published solution articles matching a term.

Freshdesk.SearchCompanies

Find companies by name.

Freshdesk.SearchContacts

Find contacts by name, exact email, or company.

Freshdesk.SearchTickets

Find tickets in the queue by status, priority, requester, agent, group, tag,

Freshdesk.UpdateTicket

Change a ticket's status, priority, assignee, or group.

Freshdesk.WhoAmI

Return the authenticated Freshdesk agent's profile.

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "find the customer's open tickets, check the knowledge base, and draft a reply." Arcade helps it use the right Freshdesk tools without guessing ticket, contact, or article IDs.

Up to 100x fewer tokens

Freshdesk searches return ticket, contact, company, and article details needed for triage, while full ticket histories and article content are fetched only when needed. The agent avoids loading every conversation into context.

Complete the workflow end to end

Find the customer, search their tickets, read the relevant history, find a knowledge base answer, and draft or send a reply through one toolkit designed around the complete support task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing Freshdesk

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For Freshdesk, you can implement some of these policies:

Access when tools are listed for a user
  • Hide Freshdesk.MergeTickets from agents without the roles your IDP marks as support leads, so duplicate tickets cannot be consolidated without oversight.
  • Restrict Freshdesk.ReplyToTicket to agents authorized to contact customers, so an unapproved agent cannot send an external response.
  • Deny Freshdesk.UpdateTicket to agents outside your support-operations roles, so they cannot reassign tickets or change their priority and status.
Pre-execution before each tool call
  • Require human approval before Freshdesk.CreateTicket runs, so an agent cannot open customer-facing tickets with unreviewed claims or requests.
  • Block Freshdesk.ReplyToTicket when the reply contains credentials, payment data, or unredacted customer records, so private information cannot be published to the requester.
  • Require human approval before Freshdesk.MergeTickets runs, so an agent cannot combine tickets and alter their support history without review.
Post-execution after the tool returns
  • Redact Freshdesk.GetTicket results to remove customer phone numbers, email addresses, and message bodies before they reach the model.
  • Strip private contact and company fields from Freshdesk.GetCustomerOverview results, so the model receives routing context without unnecessary personal data.
  • Redact personal phone numbers, email addresses, and other direct-contact fields from Freshdesk.GetContact results before the model sees them.

How to use Freshdesk with your agent

Pick your MCP client below and follow the setup to connect Freshdesk to your agent. The walkthrough covers authentication and your first support workflow.

Your questions, answered

A Freshdesk MCP server exposes Freshdesk support capabilities as structured tools that an AI agent can call through the Model Context Protocol. Agents can search tickets and articles, read ticket histories, route work, add notes, reply to customers, and update ticket records.

Freshdesk does not provide the first-party MCP server used here. Arcade provides the runtime around Freshdesk access, including credential brokering, approval workflows, response redaction, access controls, and one connection for supported clients.

Arcade agents can search, read, create, update, merge, route, and reply to tickets; add private notes; search and read knowledge base articles; look up customer, company, and agent details; and create or update contacts and companies. They cannot perform Freshdesk actions outside this coverage, such as managing billing or configuring every helpdesk setting.

Freshdesk access uses a shared API key or secret configured once. The credential must have permission for the Freshdesk records and actions your workflow uses, including reading tickets and contacts, creating or updating records, adding notes, replying publicly, changing ticket assignments or status, and merging tickets.

No. Freshdesk uses one shared API key or secret configured once rather than a separate account connection for each user. Arcade brokers the credential, and agents do not receive it directly.

Yes. Contextual Access policies can require human approval before consequential Freshdesk actions such as sending a public reply, merging tickets, changing ticket state or assignment, or creating records. The call proceeds only after the policy's conditions are satisfied.

Arcade proxies Freshdesk API calls and does not persist your content as part of normal tool execution. The Freshdesk credential is brokered and stored encrypted at rest, and the model never receives it.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade can keep using the Freshdesk credential while it remains valid. If the key or secret is revoked, rotated, expires, or can no longer be used, calls stop until the credential is reconfigured.

Freshdesk's API rate limits and account-level restrictions still apply to calls made through Arcade. The exact limits depend on your Freshdesk account and endpoint; the toolkit does not remove those limits.

Ready to actually ship your agent?

Connect your agent to Freshdesk with a shared API key, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the Freshdesk Quickstart