Freshdesk MCP server
Read support history and make targeted ticket updates with Arc0’s Freshdesk tools. Customer replies send email immediately; internal notes use a separate action. Connect through Arc0 to use the actions your identity is allowed to call.
Working with Freshdesk
Use freshdesk.search_tickets for a field-filtered support queue or freshdesk.list_tickets for a bounded browse. Search excludes archived tickets and can lag recent changes. freshdesk.get_ticket reads one ticket’s current fields; its optional embedded conversations contain only the ten oldest entries, which may omit the latest reply.
For the actual conversation, use freshdesk.list_conversations and follow each page. That is especially important before replying or resolving a request. freshdesk.reply_to_ticket emails the requester and CCs immediately, with no recall. freshdesk.add_private_note is the separate path for an internal handoff. Neither is a reason to assume an uncertain response can be repeated safely.
freshdesk.create_ticket opens work for an existing requester, and freshdesk.update_ticket changes status or priority. Account settings can send customer notifications for those operations. freshdesk.list_contacts supports an exact-email lookup, while freshdesk.get_contact checks a known ID; both return structural data rather than personal profiles. freshdesk.delete_ticket soft-deletes a ticket. Inspect its returned state instead of assuming deletion makes it immediately unreadable.
Official MCP reference: Freshdesk documentation.
Agent workflows for Freshdesk.
Build a support queue
Use freshdesk.search_tickets or freshdesk.list_tickets to locate tickets, then freshdesk.get_ticket for current fields.
Read later conversation entries
Use freshdesk.list_conversations and follow pages beyond the ticket’s limited embedded history.
Send a reviewed response
Use freshdesk.reply_to_ticket only when the email is ready for the requester and CCs.
Leave an internal handoff
Use freshdesk.add_private_note for team context and freshdesk.update_ticket for an agreed status or priority change.
11 Freshdesk actions, graded by risk.
These actions come from the Arc0 registry. Your identity, provider permissions and Arc0 policies determine which actions can run.
read
6Look things up, subject to your permissions.
- freshdesk.list_conversationsList conversations
Use when inspecting replies and notes beyond the ten oldest embedded entries. Read bounded pages through next_page to reach later writes; null ends pagination. When not: use get_ticket for ticket fields. An absent reply does not prove non-delivery.
- freshdesk.search_ticketsSearch tickets
Use when filtering tickets by field expressions; pass an unquoted query. Fixed 30/page, at most 10 pages; indexing lags and archived tickets are excluded. When not: use get_ticket for immediate readback or list_tickets for browsing.
- freshdesk.list_ticketsList tickets
Use when browsing a bounded ticket page, optionally by requester. Defaults to tickets created within 30 days; updated_since reaches older tickets. When not: use search_tickets for field expressions or get_ticket for a known ID.
- freshdesk.get_ticketGet ticket
Use when you need one ticket by ID. include_conversations returns only the ten oldest and uses extra quota. When not: use list_conversations to inspect later replies or notes; this embedded excerpt cannot confirm a recent write.
- freshdesk.list_contactsList contacts
Use when finding contact IDs and account status, optionally by exact email; person fields are omitted. When not: use get_contact when the ID is known. Avoid broad enumeration when a subject filter suffices.
- freshdesk.get_contactGet contact
Use when you know an exact contact ID and need structural account details; no person fields are returned. When not: use list_contacts for an exact-email lookup.
write
4Create and change things. Allow, or ask the user first.
- freshdesk.create_ticketCreate ticket
Use when you need a ticket for an existing requester; creation may email the customer depending on settings. Required custom fields may cause 400. When not: use update_ticket for an existing ticket. Read back before retrying an unknown outcome.
- freshdesk.reply_to_ticketReply to ticket
Use when you intend to email the requester and ticket CCs immediately; there is no recall. When not: use add_private_note for internal notes. On an unknown outcome, inspect all list_conversations pages before considering a retry; absence is not proof of non-delivery.
- freshdesk.add_private_noteAdd private note
Use when you need an internal ticket note; always private. When not: use reply_to_ticket for customer email. On an unknown outcome, inspect all list_conversations pages before considering a retry; do not resend while unresolved.
- freshdesk.update_ticketUpdate ticket
Use when changing status or priority: 2 open, 3 pending, 4 resolved, 5 closed. Resolving/closing may email the customer; required fields may cause 400. When not: use add_private_note for commentary. Read back before retrying an unknown outcome.
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- freshdesk.delete_ticketDelete ticket
Use when you intend to soft-delete one ticket, including test cleanup. When not: use update_ticket to close it instead. A deleted ticket may remain readable with deleted:true. Read back before retrying an unknown outcome.
Control access to Freshdesk.
Connect the intended Freshdesk account, authorize your AI client and set policies for its tools.
Provider permissions and Arc0 policy both apply. Allow reads, require approval for selected writes, or deny destructive actions. The audit log records execution decisions.
Configure policies and approvalsExample policy choices
- Read actions: allow where authorized
- freshdesk.create_ticket: require approval
- freshdesk.delete_ticket: deny
Arc0 MCP endpoint: https://api.arc0.ai/mcp
How Freshdesk connects.
Connect Freshdesk using API key. OAuth grants the provider scopes shown during consent; API keys and other credentials retain the permissions configured at the provider. Arc0 stores credentials in its encrypted vault and does not pass them to the model. Disconnect to remove access through Arc0; revoke a key at the provider to invalidate it there. Token refresh and provider-side revocation depend on the authentication lane and provider.
The connection serves authorized calls through Arc0 MCP and REST. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Freshdesk with your AI client.
Sign in to Arc0 and connect Freshdesk in My apps. Then authorize your AI client separately. It only receives tools and accounts allowed for that identity.
Freshdesk with Claude
Claude Desktop + Claude Code
- In Claude Desktop, add Arc0 through the remote MCP settings and use OAuth. Follow the generic remote-client steps if your account’s interface differs.
- For Claude Code, run the command below. Open /mcp, select Arc0, and authenticate in your browser. Select your workspace and review access.
- Check the connection with claude mcp get arc0.
claude mcp add --transport http --scope user arc0 https://api.arc0.ai/mcpFull MCP setup and troubleshootingFreshdesk with ChatGPT
ChatGPT on the web
- Open Plugins in ChatGPT, select the plus button, then Add custom MCP server.
- Name it Arc0, enter the server URL below, and choose OAuth. Use dynamic client registration if asked; no Arc0 API key is needed.
- Review the notice and select Create as a plugin. Complete Arc0 sign-in, workspace selection and consent, then install and select the plugin in your conversation. Labels and access vary by account; managed workspaces may require administrator approval.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingFreshdesk with OpenAI Codex
Codex app + CLI
- Run the registration command below. The app and CLI share ~/.codex/config.toml.
- Complete browser OAuth, choose your Arc0 workspace, and review access. If authentication does not start, run codex mcp login arc0.
- Check codex mcp list, then open a new Codex chat. Inspect an existing arc0 entry before changing it.
codex mcp add arc0 --url https://api.arc0.ai/mcpFull MCP setup and troubleshootingFreshdesk with Cursor
Remote MCP setup
- Add Arc0 in your client’s remote MCP settings using the server URL below.
- Choose OAuth, sign in to Arc0, select the intended workspace and review access.
- Confirm the server is connected and start with an allowed read. These are generic remote-MCP steps; consult your client’s settings for its current interface.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingFreshdesk with VS Code
Remote MCP setup
- Add a remote HTTP MCP server named Arc0 using the URL below.
- Use OAuth and finish Arc0 sign-in, workspace selection and consent.
- Confirm discovery succeeds before requesting a read. These are generic remote-MCP steps; client UI and availability may differ.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingFreshdesk with Any MCP client
Streamable HTTP
- Use a client that supports remote MCP over Streamable HTTP. Add the server URL below and choose OAuth.
- For a client without OAuth, use a self-bound API key with execute permission in the X-API-Key header. Store it in secret storage or an environment variable, outside source control. Never send both an API key and an OAuth bearer token.
- Use the MCP clients guide for the SDK transport example and Embedded identity for business-managed end users.
https://api.arc0.ai/mcpFull MCP setup and troubleshootingAfter setup, ask your agent to find an allowed read action, load its schema, and execute it on the intended account. Check Activity for the receipt. A connected MCP client alone does not confirm a successful provider call.
More crm apps.
Freshdesk and Arc0, answered.
Is there an official Freshdesk MCP server, and how does Arc0 differ?
Freshworks documents developer MCP tools for building apps. That does not establish an official Freshdesk ticket-operation server; check Freshdesk’s docs for its current offerings. Arc0 directly exposes the support API operations listed here.
Which permissions does Arc0 need for Freshdesk?
Basic authentication uses the personal API key as username and X as the dummy password, not your account password. There are no OAuth scopes. Permissions follow the agent’s role on the configured Freshdesk subdomain.
Does this work with Claude, ChatGPT, Codex and Cursor?
Yes, through Arc0 MCP when your Claude, ChatGPT, Codex, or Cursor client supports remote MCP and your account permits it. Connect the app in Arc0 and configure your client using the Arc0 setup guide. App permissions still apply.
How are credentials stored, refreshed and revoked?
Arc0 stores the API credential encrypted without refresh. Disconnect removes local access. Reset the key in Freshdesk to invalidate provider-side access for other callers.
What happens with rate limits or errors?
Freshdesk limits API calls, and including extra ticket data can consume additional quota. Arc0 reports throttling, required-field errors, and permission failures. Inspect every relevant conversation page after an uncertain reply; absence alone does not prove non-delivery.
What is the availability of these Freshdesk tools?
These tools are available. Connect the app in Arc0 and authorize your AI client. The action list describes the current implementation.
Plug Freshdesk into your agent.
Freshdesk MCP server: 11 actions including list conversations, search tickets, list tickets. Connect through Arc0.
Free to build · MCP + REST · Audit log on every plan
Freshdesk and its logo are trademarks of their respective owners. Arc0 is not affiliated with or endorsed by Freshdesk.