This page brings together answers to the most commonly asked questions about Zoho MCP, covering everything from general concepts and connection troubleshooting through to security, authorisation, and pricing.
No. While Zoho MCP is designed primarily around the Zoho application suite, it also supports third-party services including TrainerCentral, SDPonDemand, and EndpointCentral. Additional third-party integrations such as GitLab and Bitbucket are being added on an ongoing basis.
Zoho MCP is not itself an AI model. It is a platform that enables you to create MCP servers with tools drawn from MCP-ready services. When an MCP client connects to one of these servers, the client's own AI uses the available tools to execute operations autonomously across the configured services.
There is no imposed limit on the number of MCP servers you can create within the Zoho MCP service.
Zoho MCP itself does not restrict the number of tools you can add to a server. However, some MCP clients impose their own limits — Cursor, for example, supports a maximum of 40 tools. To avoid AI hallucinations and ensure reliable workflow completion, it is advisable to limit a single server to around 300 tools, and ideally closer to 100 for best performance.
MCP clients have size constraints that affect how many tools they can process at once. If your use case requires a large number of tools across multiple services, splitting them across separate, purpose-built MCP servers helps maintain performance and reduces the risk of the AI client becoming overwhelmed.
No. Zoho MCP is designed for all users who want to leverage AI agents to accelerate their business processes, regardless of their technical background. No coding proficiency is required to create and configure MCP servers through the platform.
There are several possible reasons. The MCP client you are using may not support external MCP servers, or it may have reached its limit for the number of servers or tools it can handle. Your subscription plan may also restrict server connections. Other common causes include copying the MCP URL incorrectly, or the server being disabled or not yet authorised.
Any MCP client that supports standard MCP server connections will work with Zoho MCP. Popular clients confirmed to work include Claude, ChatGPT, Windsurf, Cursor, and VS Code.
Automatic server configuration is a capability built into Cursor and VS Code. Other MCP clients have not yet implemented this feature. This is a limitation of those individual clients, not of the Zoho MCP service itself.
Yes, provided each service involved has exposed the required capabilities as MCP tools. Any MCP-server-ready service can be combined in this way, allowing you to create cross-service workflows that span data retrieval, processing, and communication channels.
No. APIs accessed through Zoho MCP follow each service's existing default limits. There are no separate MCP-specific rate limits. As of now, Zoho MCP is free to use, and users will be informed in advance if pricing is introduced in future.
Only the Super Admin of the organisation can configure Authorization via Connection. Once set up, the Super Admin can share the relevant tokens with trusted members of the organisation.
Authorization via Connection is primarily intended for third-party services. For tools from the Zoho suite, Authorization on Demand is used by default. That said, both authorisation types can be applied across either category depending on your organisation's requirements.
Yes. Access is strictly governed by the specific MCP Tools you configure on a server. Each tool defines a precise set of permitted actions, so an MCP client can only do what the configured tools explicitly allow.
Client access is tightly controlled by the action scopes defined in the configured tools. Well-established LLMs such as Claude will not update records incorrectly unless given a poorly formed or ambiguous prompt. Careful prompt design and appropriate tool scoping together ensure that write access remains safe and predictable.
No. Your MCP URL should be treated with the same level of confidentiality as a password. Sharing it gives the recipient the ability to connect to your MCP server and invoke its tools. If you believe your MCP URL has been compromised, regenerate the API key immediately to invalidate the existing URL.