Zoho MCP lets AI assistants connect to Zoho products and read or change data. That is powerful, and it raises an obvious question for anyone responsible for a Zoho organisation: how do you control who can set it up, and what they can connect? This article explains what Zoho says is possible today, how to restrict named users, and what you can do in the meantime. The position described is as at 21 October 2026, and Zoho says it is still developing these controls.
Administrators are asking how to restrict Zoho MCP across their customer or staff base. At present, anyone with a Zoho account can create an MCP server, connect it to a Zoho product they have access to, and then link it to an AI assistant such as Claude. For a Super Admin this is hard to manage and audit. The ideal would be for the Super Admin to own Zoho MCP, verify the organisation's domain, block anyone from that domain from setting up MCP themselves, route their requests to the administrator, and let the administrator decide which connectors and tools each person gets.
| Point | Position |
|---|---|
| Central controls for Super Admins | Not available. The MCP Console does not offer organisation-level controls for managing MCP access. |
| Future direction | Zoho acknowledges the need for stronger user-level and organisation-level controls and says it is working towards improved controllability of MCP user permissions. It has given no dates. |
| Restricting specific users | Available now, but not in the Console. Zoho can restrict MCP access for named users in your organisation from its side. |
This section is our own advice, not Zoho's. Until organisation-level controls arrive, control the risk from several angles at once.
| Control | What it does |
|---|---|
| Limit what each person can reach in Zoho | An MCP connection acts with the access of the user who set it up, so tight roles and profiles limit the damage. In Zoho CRM, the newer MCP permissions separate reading data from taking actions. See Give Users the Right Access with the New Zoho MCP and Zia Permissions. Zoho has been rolling these out in stages, so check they are available to you. |
| Control the AI assistant side | Business plans of AI assistants often let an administrator decide whether people can add custom connectors at all. Using that setting stops staff linking their own MCP server to your AI tool. See our guides for ChatGPT and Claude. |
| Run an approved route | Set up one or two MCP servers yourself, with only the tools needed, and tell staff those are the supported way. People are less likely to improvise when a safe option exists. |
| Write a short policy | Say who may connect AI to Zoho, which data is off limits, and that it must be agreed first. Combine it with a requirement to record how AI was used, as in our AI diligence statement guide. |
| Audit by asking | Because there is no central list of MCP servers, run a periodic check with your team: who has connected AI to Zoho, to which products, and for what. Review it when people leave or change role. |
| Use field-level controls where they exist | Zoho CRM's AI Governance settings control what field data AI features can read, but they do not reach MCP connections, so do not rely on them here. |
An AI assistant connected to Zoho can read and change records quickly and at scale, so a single badly scoped connection can do real damage, or leak data, before anyone notices. Without central controls, management depends on good habits. That is why we recommend starting every connection read-only, and keeping a record of who has set up what.