# Zoho MCP > Expert guidance on Zoho MCP — Zoho's service for building Model Context Protocol (MCP) servers that expose 300+ Zoho and third-party apps as tools to AI clients like Claude, ChatGPT, Cursor, Windsurf, and VS Code. Use this skill whenever the user mentions Zoho MCP, the Zoho MCP Console, creating/configuring an MCP server on Zoho, adding Zoho tools (CRM, Mail, etc.) to an AI agent, connecting Zoho to Claude/ChatGPT/Cursor, Zoho MCP authorization (on-demand vs. connections), the MCP URL/API key, collaborators, logs, or troubleshooting why a Zoho MCP server won't connect or a tool won't run — even if they don't say the word "MCP" explicitly. Pay special attention to the platform's limitations, which are covered in detail here. - Skill: `princeofchum/zoho-mcp` (Agent Skill, multi-file: 12 files) - Install (CLI): `npx skillmds@latest add princeofchum/zoho-mcp` - Raw SKILL.md: https://api.skillmd.com/api/skills/princeofchum/zoho-mcp/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: PrinceofChum (https://skillmd.com/u/princeofchum) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/princeofchum/zoho-mcp --- # Zoho MCP ## What this skill is for **Zoho MCP** is Zoho's service for building your own **Model Context Protocol (MCP) servers**. MCP is an open protocol (developed by Anthropic) that standardizes how AI agents connect to external tools, data, and services. A Zoho MCP server exposes **300+ Zoho and third-party applications as tools**; you connect it to an MCP client (Claude, ChatGPT, Cursor, Windsurf, VS Code, or any MCP-compatible tool), give the client a natural-language prompt, and it chains the right tool calls to complete a workflow autonomously. Use this skill to help users create and configure Zoho MCP servers, add tools, authorize services, connect clients, monitor logs, and — importantly — understand the platform's **limitations** and troubleshoot failures. The authoritative source is https://help.zoho.com/portal/en/kb/mcp; the console is at **mcp.zoho.in** (match the endpoint to the account's data center — `.com`, `.eu`, `.in`, etc.). Support: **support@zohomcp.com**. ## The mental model (read this first) The single most important thing to convey: **Zoho MCP is not AI.** It does not reason. It is the *server* layer — it exposes tools and provides context. The intelligence lives entirely in the **MCP client** (the LLM). So: - A Zoho MCP server = a bundle of **tools** (individual API operations) + the authorization to run them, reachable at a secret **MCP URL**. - The **client** (Claude, etc.) reads the prompt, discovers the available tools, and decides which to call. Zoho MCP just executes them. - **You can only do what the tools expose.** If Zoho Mail offers `sendEmail` but has no "download attachment" tool, that operation is simply impossible — no amount of prompting fixes it. Set expectations here first. How a request flows: **prompt → the client matches context to configured tools → tools execute across the services autonomously.** ## The core workflow Guide users through this sequence. Each stage has a reference file with the specifics — read the relevant one when the user is in that stage. 1. **Create an MCP server** in the Zoho MCP Console (or start from a pre-configured server template). See [references/setup-and-clients.md](references/setup-and-clients.md). 2. **Add tools** — search Zoho or third-party services, select the operations you need. **Keep it to ~300 tools** (see Limitations). Same reference. 3. **Authorize the services** — Authorization on Demand (per user, default for Zoho) or Authorization via Connections (org-wide, required for third-party). See [references/authorization.md](references/authorization.md). 4. **Connect an MCP client** — copy the MCP URL from the Connect section and add it in Claude / ChatGPT / Cursor / Windsurf / VS Code / a custom client. See [references/setup-and-clients.md](references/setup-and-clients.md). 5. **Prompt and run** — give the client a natural-language instruction; it chains tool calls. Monitor results in **Logs** (30-day retention). ## Decision guidance **Picking an authorization method** is the decision users most often get wrong: - Solo user, or each person uses their own Zoho login → **Authorization on Demand** (default, account-centric). - A team sharing one org's access → **Authorization via Connections** (a Super Admin shares OAuth tokens). *Only a Super Admin can set this up.* - Any **third-party** service (GitLab, BitBucket, etc.) → **must** use Authorization via Connections; on-demand isn't available for those. **Start from a usecase.** When a user describes a goal, the fastest path is to find a matching worked recipe in [references/usecases.md](references/usecases.md) (174 recipes across 58 services) and use its ordered steps as the exact list of tools to add. This beats guessing tool names. **Scoping tools:** more tools ≠ better. Past a few hundred, the client starts to hallucinate and pick wrong tools. Add only the operations the workflow needs. Also warn that some clients cap tools hard — **Cursor allows only ~40**. **Security:** the MCP URL contains a secret API key — treat it exactly like a password. Never share it or paste it publicly. If it leaks, use **Regenerate API Key** in the console to invalidate the old URL. ## Limitations (cover these — the user asked specifically) These are the real constraints. Surface the relevant ones proactively rather than letting users discover them by failure: - **Not AI / bounded by exposed tools.** Zoho MCP can only perform operations that a service exposes as a tool. Missing capability = impossible task. - **~300 tools per server (recommended cap).** No hard platform limit, but exceeding it degrades client accuracy and causes hallucination. - **Client-side tool caps.** The client, not Zoho, may limit tools — e.g. **Cursor ~40 tools max**. "Won't connect" is often this. - **Auto-config only for some clients.** One-click setup exists for Cursor and VS Code; others (Claude, ChatGPT, Windsurf) need manual config. This is a client limitation, not Zoho's. - **Third-party auth is connection-only.** Third-party services cannot use Authorization on Demand. - **Authorization via Connections is Super-Admin-only** to set up. - **Logs retained 30 days**, then deleted automatically. - **Server deletion is permanent and irreversible.** Disabling is reversible; deleting is not. - **Org deletion** requires removing all collaborators first and is Super-Admin only. - **Common failure causes:** tool not configured on the server; prompt too vague for the client to extract context; the client's own limitations or lack of MCP support; wrong/miscopied MCP URL; server disabled or unauthorized; subscription restrictions. No limit is imposed on the **number of servers** you can create. ## Reference files Read as needed — each is self-contained: - [references/setup-and-clients.md](references/setup-and-clients.md) — create a server, add/delete tools, and connect every supported client (Claude, ChatGPT, Cursor, Windsurf, VS Code, custom) with exact steps. - [references/authorization.md](references/authorization.md) — the two authorization models, switching/revoking, third-party connections, and collaborator roles (Admin vs. User) and management. - [references/tools-and-services.md](references/tools-and-services.md) — what tools are, tool naming conventions, MCP-ready services, and the tool manual. - [references/zoho-services.md](references/zoho-services.md) — the complete catalog of all **46 Zoho services (9,069 tools)** with per-tool definitions in a queryable data file. Use this to answer "does Zoho X have a tool for Y?" - [references/third-party-services.md](references/third-party-services.md) — the **8 beyond-Zoho services (836 tools)** (CloudSpend, MDM, SDP on Demand, Vani, EndpointCentral, Log360Cloud, Site24x7, Qntrl), queryable catalog included. - [references/usecases.md](references/usecases.md) — **174 worked workflow recipes across 58 services**, each with ordered steps and the exact tools they use. This is the best starting point when a user describes a goal: find a matching recipe and use its steps as the tool-selection blueprint. - [references/limitations-and-troubleshooting.md](references/limitations-and-troubleshooting.md) — the full FAQ, failure scenarios, support policy, and Zoho MCP vs. APIs. - [references/glossary.md](references/glossary.md) — every MCP term (client, server, tool, transport, agent mode, JSON-RPC, etc.) defined. ## Caveats - Zoho MCP is evolving quickly (services are "consistently added"; new clients gain support). Verify current console UI and the live service list against the docs, and tell users when something may have changed. - This skill is reference knowledge — it can't access a user's Zoho account or build servers for them; it explains how to do it themselves.