The following FAQs address common questions and clarifications.

Info: For an overview of MCP integration, including setup and configuration steps, see the MCP integration article. 

TABLE OF CONTENTS

Understand MCP

What is the Model Context Protocol (MCP)? 

The Model Context Protocol (MCP) is an open standard that enables AI assistants, such as Claude and Microsoft Copilot, to connect directly to Freshdesk. Through MCP, these assistants can perform actions on your behalf, such as creating tickets, updating contacts, or retrieving conversation history, without leaving the AI client.

Which Freshdesk products support MCP? 

MCP is supported only in Freshdesk and Freshdesk Unified Omni 2026.

Which AI clients are supported? 

You can use any AI client that supports the MCP standard. Connect your preferred MCP-compatible client to Freshdesk using the MCP server URL and the API key provided in your Freshdesk administrator settings.

Setup and configuration

How does authentication work for MCP? 

Freshdesk MCP uses API key authentication. Each user manually connects their AI client using their individual Freshdesk API key and the MCP server URL. You can find your API key in your Freshdesk profile settings.

Can I control which tools or actions are available through MCP? 

Currently, tool-level access management is not available. All supported MCP tools are available by default to any user who connects using a valid API key.

Is Freshdesk available as a native connector in AI clients like Claude or Gemini? 

Not yet. Freshdesk is not currently listed as a native connector in AI client marketplaces. To connect an AI client to Freshdesk via MCP, you must manually enter the MCP server URL and authenticate using your API key.

Security and access control

Who can use MCP to interact with Freshdesk? 

Any user with a valid Freshdesk API key can connect an AI client to MCP. The actions available through MCP strictly match the permissions granted by the user's Freshdesk role. MCP does not grant additional permissions.

Can an AI agent access data that a user isn't permitted to see? 

No. MCP calls execute within the context of the authenticated user's API key. All Freshdesk role-based access controls and data scoping rules apply identically to MCP requests.

Capabilities and limitations

What actions can an AI agent take through MCP? 

Available actions include creating, updating, and retrieving tickets; searching contacts and companies; and fetching conversation history. For a complete list of tools, see list of available tools.

Does MCP work in real time? 

Yes. MCP calls execute in real time against your live Freshdesk data.

What happens if an AI agent sends an unsupported or invalid request? 

The MCP server returns a structured error to the AI client. The client then handles the error gracefully and informs the user.

Billing and pricing

How does the pricing model work for MCP? 

Starting September 1, 2026, MCP usage is measured in Actions. An action is a successful tool invocation. Note that complex requests requiring multiple tools might consume multiple actions. Any call to an MCP server counts as one action, regardless of whether it reads or writes data, and regardless of which AI client made the call.

Will unused MCP actions roll over to the following billing cycle? 

No. MCP action allowances are tied to your current billing cycle and do not roll over.

Will I receive notifications before reaching my action limit? 

Yes. You will receive notification alerts as you approach your usage limit, starting when you reach 50% to 60% of your allowance.

How will Early Access Program (EAP) participants transition to the new pricing model? 

If you participated in the EAP (which had no pricing), your account will automatically transition to the new pricing model on September 1, 2026. No action is required on your part, and this pricing change will not affect your existing MCP setup or connections.