10 minTime to key
NoNo-human path
3Human gates
6/10Onboarding score
Email verificationMandatory 2FAPhone OTP
Fastest path to a key
- Phone OTPSign up for a Zoho account (email or Google/Microsoft/LinkedIn sign-in). Verify email; Indian signups typically also verify a mobile OTP
- Pick the right data center (accounts.zoho.com / .in / .eu etc.). Every API host is DC-specific
- API: go to api-console.zoho.com > Add Client > Self Client (or Server-based for redirect flow)
- Generate a grant code with explicit scopes (e.g. ZohoCRM.modules.ALL), valid 3-10 minutes
- POST to accounts.zoho.<dc>/oauth/v2/token to exchange for refresh_token + access_token (access token lasts 1h; refresh is long-lived)
- MCP alternative: sign up at zoho.com/mcp > Create MCP Server > select Zoho/third-party apps and tools > authorize each app connection via OAuth > copy the server URL (https://<name>-<orgid>.zohomcp.com/mcp/<key>/message)
- Working API key
Biggest gap
No CLI/device flow to mint API tokens, and the data-center-specific hosts (zoho.com vs zoho.in) are a common agent failure point
Worth copying
A user-composed MCP server: pick exactly which apps/tools an agent gets, so least privilege is set at server-creation time
Sources (7) · checked 2026-10-11
- https://www.zoho.com/llms.txt
- https://www.zoho.com/mcp/llms.txt
- https://www.zoho.com/mcp/index.md
- https://www.zoho.com/mcp/pricing.md
- https://help.zoho.com/portal/en/kb/creator/zoho-creator-academy/feature-in-focus/mcp/articles/connect-your-zoho-mcp-server-to-a-genai-assistant
- https://help.zoho.com/portal/en/kb/projects/settings-in-zoho-projects/portal-configuration/articles/zoho-projects-mcp
- https://tldv.io/fr/blog/zoho-mcp/
50Readiness score / 100
L2 Agent-documentedBeats 67% of 1,846 companies
Access20/20
Context17/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.
- +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
- +6 Agents can self-register OAuth clients. Support dynamic client registration (RFC 7591) or client ID metadata documents so MCP clients connect in one click.
All 20 checks
- PASSAgents 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
- PASSDocs 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: 10 changes, up to +50 points
Each change is ready to paste, filled in for zoho.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/zoho.com)