CRMConnector
Zoho CRM
Search, read, create, update and delete records on any Zoho CRM module, and add notes, from Claude or ChatGPT through Tulina's MCP server, in your Zoho region.
Official site: crm.zoho.com
What it can do
1 read/3 write
- 01Read
List the CRM's modules
- 02Write
List, read, search, create, update and delete records on any module
- 03Write
Read and add notes tied to a record
- 04Write
Run with a read-only access level set by an organisation admin
Access runs through credentials held in the vault rather than a shared password, and can be revoked without touching code. A CRM token is close to a master key for how a company talks about its customers, so it is worth deciding who reaches it and what they can do once they do.
Does Zoho CRM have an MCP server?
Yes. Zoho offers MCP servers for its CRM, set up from a Server Registry, with OAuth sign-in, in which the agent has your permissions and nothing beyond them. They are split by job: one is read-only for pipeline insights and forecasts, one creates, updates and deletes records, one changes modules and layouts, and one sets up workflow rules and blueprints. Tulina reaches the same CRM through its own MCP server, on the same link that carries the rest of your stack, covering records and notes.
How do you connect Zoho CRM to Claude and ChatGPT?
Through Tulina's own MCP server, in three steps:
- In the Zoho API console, create a Self Client, generate a grant token with the ZohoCRM scopes and exchange it for a refresh token.
- Paste the client id, client secret and refresh token into Tulina's Zoho connector, and pick your Zoho region: com, eu, in, au, jp or ca. They are stored in the vault and never shown to the model.
- Add
https://mcp.tulina.ai/mcpto Claude or ChatGPT and sign in with your Tulina account. The MCP page has the same link.
Several Zoho organisations can be connected as named accounts, and a request names the one it is for.
Tulina vs Zoho's official CRM MCP servers
Both reach the same CRM. They differ in how much of Zoho each one covers.
| Zoho's CRM MCP servers | Tulina | |
|---|---|---|
| Sign-in | OAuth, with your own permissions | A self-client credential held in Tulina's vault, set for a person or for the organisation |
| Read-only use | A Data Insights server that never touches a record | A read access level, set by an organisation admin, that asks Zoho for read scopes only |
| Records | Create, update and delete | List, get, search, create, update and delete on any module |
| Notes | Not itemised on the page | List a record's notes, add one |
| Fields, layouts and workflows | Separate servers for modules, workflow rules and blueprints | Not available |
| In the same conversation | Zoho | Zoho plus your inbox, calendar, Zoho Desk and the other connected tools |
If Zoho CRM is the only system the model needs, or you want it to change modules, layouts or workflows, Zoho's own servers are the better choice. Tulina earns its place when a CRM record is one step in a longer piece of work.
What you can ask it
"Find the contact whose email is a@b.com and tell me their open deals." The agent searches Contacts with the criteria (Email:equals:a@b.com), then searches the Deals module for deals tied to them. Searches are paginated, so a broad one returns a page at a time.
"Create a lead for Jane Doe at Acme from this email thread." The agent creates the record in the Leads module with the fields you give it, and hands back its id.
"Add a note to the Acme deal saying the quote went out Thursday." The agent looks up the deal, then adds a note with a title and a body. Listing the record's existing notes comes first when you want to avoid repeating one.
Processes can chain these steps without a prompt each time. Zoho CRM sits beside Zoho Desk for support tickets and Zoho Analytics for reporting, and next to other CRMs such as HubSpot and Pipedrive when contacts move between systems.
What the Zoho CRM connector can't do
- It reads and writes records and notes. Changing modules, fields, layouts, workflow rules or blueprints is out of its reach.
- Notes can be listed and added. Editing or deleting one is not available.
- Deleting a record is irreversible, so a workspace that should only read is set to the read access level.
- Zoho accounts live in one data center. The region is chosen when connecting, and a credential only works against the region it was made in.
- Records are addressed by module name, such as Contacts, Leads, Deals or Accounts, and the list of modules comes from the CRM itself.
- A page of search results is limited by
per_page, so a large export is paged through rather than fetched at once.
Why through Tulina
The connection was never the hard part.
Most systems now publish their own way for a model to reach them, and that is good: it is what Tulina connects to. The hard part is deciding who may use it, what it is allowed to return, and what the model knows before it asks.
The keys stay in one place
YouTeamOrganisation
Connect Zoho CRM once. The credential is encrypted in a vault, never held in clear, and never pasted into a chat or a workflow file. A person uses their own key where they have one, their team's where they do not, the organisation's after that, so nobody is blocked and nobody holds more access than they need. Revoke it once and everything running on it stops.
What leaves is filtered before it leaves
fields droppedmasked or hashedpseudonymised
Roles decide who can reach Zoho CRM at all. Beyond that, a policy on the connector itself decides what comes back. The data is minimised at the source rather than after it has already reached a model.
Every call is on the record
whatwhowhen
Runs are logged for the organisation. That is what makes an automated action reviewable after the fact, and it is what a security review asks for first.
The run starts knowing your company
namingkey accountsdecisions
A direct connection gives a model access. It does not tell it how your company names things, which accounts matter, or what was decided last quarter. Tulina carries that across every tool, so the same request against Zoho CRM returns something usable instead of something generic.
Processes that run on Zoho CRM
None published yet.