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

23 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.CreatePrivateNote

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

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.ListTickets

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

Freshdesk.MergeTickets

Merge duplicate tickets into one.

Freshdesk.ReplyToTicket

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

Freshdesk.SaveCompany

Create a new company account or update an existing one.

Freshdesk.SaveContact

Create a new contact or update an existing one.

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 urgent tickets from Acme, read their history, and route each one to the right support group." Arcade picks the right Freshdesk actions without guessing ticket, contact, or group IDs.

Up to 100x fewer tokens

Freshdesk list and search requests return matching ticket, contact, company, or article records, while full ticket history is fetched only when the agent needs it, avoiding unnecessary context from the whole queue.

Complete the workflow end to end

Find the customer, inspect the ticket history, search the knowledge base, draft a reply, and route or merge the ticket 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.
  • Hide Freshdesk.CreatePrivateNote from agents outside your internal-support roles, so customer-facing agents cannot expose internal assessments or escalation details through ticket notes.
  • Restrict Freshdesk.SaveCompany to agents with the organization-admin role your IDP assigns, so unapproved automation cannot overwrite company ownership, domain, or account records.
  • Deny Freshdesk.SaveContact to agents without your customer-data role, preventing unauthorized changes to a contact's identity, email address, or company association.
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.
  • Require human approval before Freshdesk.CreatePrivateNote runs on a ticket marked escalated or under legal review, so an agent cannot add unverified internal claims to a sensitive case.
  • Block Freshdesk.SaveCompany when an update changes a company's domain, owner, or account identity without matching records in your CRM, so automation cannot attach support history to the wrong organization.
  • Require approval before Freshdesk.SaveContact creates or changes a contact, so an agent cannot silently redirect customer communications or replace a verified email address.
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.
  • Redact requester email addresses, phone numbers, and ticket descriptions from Freshdesk.ListTickets results before they reach the model, leaving queue metadata for routing without exposing customer messages.

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. With a configured Freshdesk credential, the agent can search tickets and customers, read ticket history, manage records, and respond to requesters.

Freshdesk's own MCP server is not required for this integration; Arcade provides the MCP endpoint for these Freshdesk actions. Arcade adds credential brokering, approval policies, redaction, tool controls, and one connection for supported clients.

Arcade agents can search and read tickets, contacts, companies, and knowledge base articles; inspect a requester's combined context; create tickets; add private notes; send public replies; update routing and status; merge duplicate tickets; and create or update contacts and companies. They can also list agents and groups for routing.

Freshdesk uses a shared API key or secret configured once for the integration. That credential determines which Freshdesk reads and writes are available, so configure it with the narrowest Freshdesk access that supports your workflow.

No. This integration uses one shared Freshdesk credential configured once rather than asking each user to connect a separate account. Arcade brokers the credential to make calls, and the model never receives it.

Yes. Contextual Access policies can require human approval before consequential Freshdesk actions such as sending a public reply, changing ticket routing or status, merging tickets, 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 refreshes access while the configured Freshdesk credential remains valid. If the key is revoked, rotated, or can no longer be used, Freshdesk calls stop until the credential is reconnected or updated.

Freshdesk's API rate limits and account-level restrictions still apply to calls made through Arcade. The available integration details do not define a separate Arcade quota or a Freshdesk numeric limit.

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