Connecting Claude to Zoho through MCP takes a few minutes. Deciding what it should be allowed to do takes longer, and it matters more. This guide covers the decisions to make before you add the connector, and how to prompt once it is connected. It is based on our own approach, and it complements Zoho's step-by-step setup rather than repeating it. For the click-by-click steps, follow Zoho MCP Quick Start Guide, which walks through creating an MCP server, adding tools, copying the MCP URL, and adding it to Claude as a custom connector.
How the connection works
- You create an MCP server in Zoho MCP and choose the tools it exposes, for example one that reads lead records or one that sends an email. A Zoho MCP server can hold up to 300 tools.
- You give Claude the server's MCP URL and complete an OAuth authorisation, which links the connector to a Zoho user.
- From then on, Claude can use only the tools you added, and only with the access of the user who authorised it.
Your Claude plan must allow custom connectors. If it is a business plan, a Claude administrator may need to enable that first.
Decide what to expose before you build
Where we differ from the Quick Start: Zoho's guide advises adding all the tools relevant to your use case, because that helps Claude complete tasks accurately. We agree for a defined use case, but we would start narrower than that: add the tools a specific job needs, and add write tools deliberately rather than by default.
| Stage |
What to expose |
Why |
| 1. Explore | Read-only tools only, such as getting records and running reports. | People learn what is useful with no risk to the data. |
| 2. Prove a job | The read tools for that job, plus the one or two write tools it needs. | Claude has the tools to finish the task, and nothing more. |
| 3. Widen | Add tools job by job, after reviewing how the last one behaved. | Each new write tool is a new way for a mistake to reach live data. |
Consider separate servers for reading and for writing, so you can connect people to the read-only one freely and keep the write one for the few who need it. Our architecture article describes the same split in Zoho's own offering, with a read-only server for analytics and a full-access server for operations.
Permissions: the connection is only as safe as the user behind it
- Claude acts with the access of whoever authorised the connector. If an administrator authorises it, Claude has administrator reach. Authorise with an ordinary user whose access matches the job.
- In Zoho CRM, newer profile permissions let you grant read access to MCP without allowing actions. See Give Users the Right Access with the New Zoho MCP and Zia Permissions. Check that they are available in your data centre, because Zoho has been rolling them out in stages.
- Field-level AI controls in Zoho CRM do not apply to MCP connections. See Introducing AI Governance. If a field must stay private, the user behind the connector should not be able to see it at all.
Test before you connect live data
- Build and test the server against a sandbox or a test organisation with realistic dummy records.
- Run the exact prompts you expect people to use, including badly worded ones.
- Check what actually changed in Zoho, not only what Claude said it changed.
- Only then point a connector at a live account, and start with the read-only stage above.
Prompting so you stay in control
| Habit |
Example |
| Say what success looks like | "List leads created this month with no activity, with owner and source, as a table." |
| Ask for a plan before any change | "Show me which records you would update and what you would change. Do not change anything yet." |
| Limit the scope | "Only the 10 oldest records first, then I will review." |
| Ask for an audit trail | "When finished, list every record you changed, with its ID and the old and new values." |
| Make it say what it could not do | "If any record could not be read or updated, tell me which and why, rather than guessing." |
What to review after it is live
- Spot-check a sample of changed records each week for the first month.
- Review who has a connector, and remove access for anyone who has left or changed role.
- Re-check the tools on the server whenever you add a use case.
- Keep the prompts that work in a shared place, so people reuse tested wording instead of inventing their own.
UK and EU data residency
If prompts and CRM data must be processed in the UK or EU, connecting through the Claude app is not the whole answer. See Model Context Protocol Architecture with Amazon Bedrock for UK/EU Data Residency for a setup that keeps model processing in your chosen region.