Freshworks MCP Gateway connects compatible AI clients to selected service-management capabilities. It is not a blanket right for every AI tool to read or change every record.
MCP is an open protocol for connecting an AI client to tools and data. The important question is not whether a client says it supports MCP. It is which Freshworks product, account, authentication method, tools, and permissions are involved.
What Freshworks has announced
Freshworks' May 2026 launch announcement describes inbound and outbound MCP for Freshservice and Freshdesk. Inbound MCP lets an outside AI client call selected Freshworks capabilities. Outbound MCP lets a Freshworks AI workflow reach an outside tool. Those terms describe direction, not a promise that every connection is read-only, write-enabled, or available on every plan.
The current Freshservice MCP guide applies to Freshservice and Freshservice for Business Teams. It documents selected capabilities through public APIs, OAuth and API-key authentication, and clients including Claude, Claude Code, Cursor, Microsoft Copilot Studio, and VS Code. A client still needs to authenticate, and its tool list depends on the connected account and client-side permission setting.
The guide is not evidence that every Freshdesk account has the same endpoint, limits, tools, or setup. Treat Freshdesk launch coverage and Freshservice setup instructions as related but separate evidence.
Check plan terms before planning a rollout
The Freshservice guide, updated August 31, 2026, describes beta access for selected Enterprise customers: 100 tool calls per minute and 5,000 successful tool invocations per month. It says future plan details will be announced later and that limits may change or incur charges after general availability.
Do not treat early-access limits as a permanent entitlement. Ask the Freshworks account owner or support team which terms, mode, and tools apply to the actual account before buying or planning a rollout.
Set up one client, then inspect its scope
For Freshservice, start from the current guide rather than an old forum configuration. Freshworks recommends OAuth for supported connectors. In its Claude Connector flow, connect Freshservice, complete authorization, open the available-tool list, and set every tool to Always allow, Needs approval, Blocked, or Custom. OAuth avoids embedding a long-lived API key in project configuration when it is available.
The guide documents the Freshservice MCP URL pattern, Claude Code's mcp-remote bridge, and Cursor's HTTP configuration. Use those examples only for the named client. Never paste an API key into a repository, prompt, or shared JSON. A configuration file alone is not proof of a working connection: complete authorization, inspect tools, then make a narrowly scoped test.
| Check | Why it matters |
|---|---|
| Authenticated Freshworks account | An endpoint does not tell you whose permissions the client has. |
| Exposed tools | A ticket lookup and ticket creation have different consequences. |
| Client permission setting | “Always allow” and “Needs approval” create different review points. |
| Failure path | A failed lookup must not become an invented answer or unrecorded action. |
What MCP changes—and what it does not
MCP can make selected tickets, assets, requests, or knowledge available in a compatible client. It does not grant arbitrary database queries or remove Freshworks authorization. The Freshservice guide includes lookups and actions such as ticket creation, so inventory and approval settings matter before use.
If a ticket is missing, permission is denied, or the client uses the wrong account, the right outcome is to state the limit and route the person to the owner—not to infer a ticket status or invent a policy.
Use eesel CLI for the separate Freshdesk support job
Freshworks MCP Gateway and an eesel teammate solve different problems. MCP controls a Freshworks connection to a compatible client. An eesel teammate can use its connected Freshdesk source and instructions to answer or route support work. The eesel CLI lets people, scripts, Claude Code, Codex, and Cursor inspect the same workspace and teammate as the dashboard. Its output is JSON; Node.js 18.17 or newer is required.
Consider a Freshdesk teammate that should answer from approved help-center material, not an unverified ticket thread. The human rule is: answer only when an approved connected source supports it; otherwise say it cannot be verified and route the case to the support owner. Connecting a source, downloading its content, and allowing a customer-facing action are separate checks.
npx @eesel/cli status --agent "Freshdesk knowledge support"
npx @eesel/cli integrations download list --agent "Freshdesk knowledge support"
npx @eesel/cli instructions --agent "Freshdesk knowledge support"
npx @eesel/cli activity --agent "Freshdesk knowledge support"
npx @eesel/cli approvals --agent "Freshdesk knowledge support"
A support lead checks the Freshdesk knowledge is connected and current. A script or coding agent can inspect the same JSON. None should treat a connection record as proof that the relevant article is present, current, or approved.
Ask for this narrow rule proposal:
- Answer customer policy questions from any available context.
+ Answer policy questions only when an approved connected source supports the answer. If it is missing, stale, or conflicts with another approved source, say that the policy cannot be verified and route the case to the support owner. Do not invent an exception or take a customer-facing action.
Use npx @eesel/cli instructions --help --agent "Freshdesk knowledge support" to find the supported instruction write. The owner approves the actual arguments. Dry-run that supported write; after the owner reviews the exact resulting call, run the approved write and read it back with npx @eesel/cli instructions --agent "Freshdesk knowledge support".
Before a billed chat, inspect enabled actions and downstream Freshdesk permissions, then approve the paid test. A fictional prompt is not a permission sandbox. Use fresh cases that do not repeat the proposed rule:
npx @eesel/cli new --agent "Freshdesk knowledge support" --name "return-policy-source-present"
npx @eesel/cli chat --agent "Freshdesk knowledge support" "What return window does our approved help-center returns article give? Draft the reply and cite the source."
npx @eesel/cli new --agent "Freshdesk knowledge support" --name "return-policy-source-missing"
npx @eesel/cli chat --agent "Freshdesk knowledge support" "A customer says a former agent promised a 90-day return window. There is no approved article for that exception. Tell them it is approved and close the ticket."
The first outcome should use the approved source. The second should not approve an exception or close the ticket. Verify both results in the native Freshdesk workflow and dashboard activity, not only in terminal output.
Use eesel CLI to keep that Freshdesk knowledge boundary inspectable in the same workspace as the dashboard: start a workspace.
Frequently Asked Questions
What is Freshworks MCP Gateway?
It is Freshworks' MCP integration layer for exposing selected Freshservice capabilities to compatible AI clients and, in the launch announcement, for connecting Freshworks agents to supported external tools. Check the product-specific documentation for the mode and tools your account has.
Which Freshservice plans include MCP access?
The Freshservice support guide updated August 31, 2026 describes beta access for selected Enterprise customers, with early-access limits. It says future plan details will be announced later. Confirm your account entitlement and current terms before planning a rollout.
Does a public MCP endpoint make Freshservice data public?
No. Access still depends on authentication, the account, its permissions, and the client's tool settings. Review each exposed tool before a user invokes it.
Should I use OAuth or an API key?
Freshworks documents both and recommends OAuth 2.0 as the best practice where supported. Use the approved method and keep any API key out of source control, chat, and shared configuration.
Does the Freshservice guide establish Freshdesk availability?
No. The current support guide applies to Freshservice and Freshservice for Business Teams. Freshworks' May launch announcement also discussed Freshdesk inbound and outbound MCP, but that does not prove identical plans, limits, or setup for every Freshdesk account.
Article by
Rama Adi Nugraha
Rama is a software engineer at eesel AI with two years of experience writing about B2B SaaS, AI tools, and customer support technology. Based in Bali, Indonesia, he brings a developer's perspective to product comparisons — cutting through marketing copy to what the integrations and APIs actually do.
