10 minTime to key
NoNo-human path
2Human gates
5/10Onboarding score
CAPTCHAEmail verification
Fastest path to a key
- Start a free trial at freshworks.com (work email, company name). This creates <subdomain>.freshdesk.com (or .freshservice.com)
- Email verificationVerify email / activate account via link
- CAPTCHAProfile settings > View API key (may require completing a captcha)
- Call REST v2 with HTTP Basic auth: API key as username, 'X' as password, against https://<subdomain>.freshdesk.com/api/v2/
- MCP: point the client at https://<subdomain>.freshdesk.com/mcp with the API key in the Authorization header (Growth plan or higher)
- Working API key
Biggest gap
Freshdesk MCP auth is a full-power personal API key in a header, and action quotas are small (100/month on Growth during EAP)
Worth copying
The MCP lives on the customer's own subdomain, so tenant routing is implicit with no extra config
Sources (5) · checked 2026-10-11
- https://support.freshdesk.com/support/solutions/articles/50000012670
- https://support.freshservice.com/en/support/solutions/articles/50000012678-model-context-protocol-mcp-integration-in-freshservice-eap-
- https://www.freshworks.com/llms.txt
- https://developers.freshworks.com/
- https://www.eesel.ai/blog/freshworks-mcp-gateway-explained
34Readiness score / 100
L1 Agent-readableBeats 43% of 1,846 companies
Access10/20
Context11/20
Interfaces8/32
Onboarding3/19
Trust2/9
llms.txt · root
Biggest gains
- +12 Remote MCP server for the product. Host a remote MCP server (e.g. mcp.<domain>/mcp, Streamable HTTP) for your core actions.
- +10 Agents get the real page, not a bot wall. Serve the homepage to AI user-agents (Claude-User, ChatGPT-User) without a challenge or 403.
- +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
All 20 checks
- FAILAgents get the real page, not a bot wall10
- PASSrobots.txt lets user-triggered agents in6
- PASSContent is server-rendered4
- PASSllms.txt exists8
- FAILllms-full.txt exists3
- FAILDocs available as markdown6
- PASSSitemap2
- PASSStructured metadata1
- PASSPublic developer docs4
- FAILMachine-readable API spec8
- FAILRemote MCP server for the product12
- FAILDocs MCP or searchable docs4
- PASSSDKs and a CLI4
- FAILOAuth discovery metadata5
- FAILAgents can self-register OAuth clients6
- FAILSelf-serve API keys5
- PASSFree tier or test mode3
- FAILAgent manifests4
- PASSsecurity.txt2
- FAILPublic status page3
Your fix pack: 12 changes, up to +66 points
Each change is ready to paste, filled in for freshworks.com, with a command to check it worked. Or hand the whole list to your coding agent.
Add the badge to your README
[](https://agentsready.dev/c/freshworks.com)