By Ira Bodnar, Ryze AI · Updated · Sources checked November 14, 2026
Quick answer
The main way to connect OpenClaw to Zoho CRM is the Ryze AI connector. Sign in to Zoho from the Zoho CRM card in Ryze AI and approve CRM access, then save https://connector.get-ryze.ai/mcp in OpenClaw as a streamable-http server with auth set to oauth, using the CLI, Settings > MCP in the Control UI or openclaw.json. Sign in once and OpenClaw can list 4 Zoho CRM tools: two that read, one that writes and one that deletes.
- In Ryze AI open Integrations, find the Zoho CRM card, click Connect and sign in to Zoho
- Save the Ryze AI server in OpenClaw with openclaw mcp set, the Control UI or openclaw.json
- Run openclaw mcp login ryze and click Allow connection
- Ask about your leads, deals or contacts
OpenClaw to Zoho CRM at a glance
| Fact | Detail |
|---|---|
| Main way to connect | The Ryze AI connector, saved in OpenClaw as one remote MCP server named ryze |
| Server address | https://connector.get-ryze.ai/mcp, with transport set to streamable-http |
| Sign-in | Zoho OAuth once in Ryze AI, then OAuth to Ryze AI from OpenClaw with openclaw mcp login ryze, or Sign in under Settings > MCP for an administrator. A Ryze AI API key in a bearer header is the other route |
| Zoho CRM tools | 4: zoho__read, zoho__query, zoho__write and zoho__delete |
| Can it change Zoho CRM | Yes, through the write and delete tools. OpenClaw's docs describe no per-call prompt for its built-in runtime, so limit the tools yourself (see the approvals note below) |
| Other data in the same chat | Tools for the other platforms you connected to the same Ryze AI workspace come through the same server address |
| OpenClaw plan needed | None to buy. OpenClaw is MIT licensed and self-hosted, and its docs say it has no paid tier |
| Ryze AI price | Paid Ads is $89 per month with a 7-day free trial. Adding the connector is free |
| Zoho's own option for OpenClaw | Four pre-built Zoho CRM MCP servers and the Zoho MCP console. No Zoho page opened names OpenClaw, and the pairing was not run |
| Zoho access of the default connection | 5 scopes: ZohoCRM.modules.ALL, ZohoCRM.settings.ALL, ZohoCRM.users.READ, ZohoCRM.org.READ and ZohoCRM.coql.READ |
| Last checked | Zoho CRM sources on November 14, 2026 and OpenClaw sources on November 15, 2026. No Zoho CRM call and no step inside OpenClaw was run |
Before you start
- OpenClaw. It is an open-source project under the MIT license that you host yourself. You need a running Gateway and one of three things: the openclaw command on the Gateway machine, administrator access to the Control UI, or write access to the Gateway's openclaw.json.
- A Zoho login that can approve the access. Ryze AI asks for access to CRM modules, settings, users and organization details. Any Zoho data center works, including US, EU, India and Australia. Connect with a login whose reach in Zoho CRM you are comfortable sharing, because the access follows that user's CRM role.
- A Ryze AI workspace on a plan or free trial. Paid Ads is $89 per month with a 7-day free trial; SEO Starter is $129 per month with a 3-day free trial and Agency is $279 per month. Adding the connector is free, but the Zoho CRM tools need an active plan or trial.
- A note on testing. Ryze AI has no help-center page for OpenClaw, no Zoho CRM organization was connected for this guide and the OpenClaw steps were not run. They follow OpenClaw's own documentation for remote servers that use OAuth, as read on November 15, 2026.
How to connect OpenClaw to Zoho CRM
The first two steps happen in Ryze AI and Zoho, the next three in OpenClaw, and the last is your first prompt. The connector URL is the same for every user.
Connect Zoho CRM in Ryze AI
Create a Ryze AI account or sign in, open Integrations, use the CRM filter to find the Zoho CRM card and click Connect.
Sign in to Zoho and approve the access
Sign in to Zoho on the data center where your CRM organization lives and approve access to CRM modules, settings, users and organization details. When the card shows Connected, click View to see the organization name. No API key is pasted.
Save the Ryze AI server in OpenClaw
Stop the Gateway with openclaw gateway stop, because OpenClaw 2026.10.10 (November 3, 2026) holds back CLI changes to MCP settings while a Gateway runs. Then run: openclaw mcp set ryze '{"url":"https://connector.get-ryze.ai/mcp","transport":"streamable-http","auth":"oauth"}'. The same entry can go under mcp.servers in ~/.openclaw/openclaw.json, or be added with Add server under Settings > MCP in the Control UI while the Gateway runs.
openclaw gateway stop openclaw mcp set ryze '{"url":"https://connector.get-ryze.ai/mcp","transport":"streamable-http","auth":"oauth"}' openclaw mcp login ryzeSign in to Ryze AI from OpenClaw
Run: openclaw mcp login ryze. A browser opens on the Ryze AI page. Sign in if asked, choose the workspace that holds Zoho CRM and click Allow connection, then start the Gateway again. An administrator can instead click Sign in for the ryze server under Settings > MCP.
Finish the sign-in on another machine if needed
If the browser is not on the machine that runs OpenClaw, approve the sign-in there and hand the code it returns to openclaw mcp login with the --code option.
Ask your first question
Once credentials exist, OpenClaw adds the server to the agent runtime. If you saved the connector before Zoho CRM was connected in Ryze AI, remove the entry and save it again so the tool list refreshes. Then ask: Run a COQL query that counts Leads created this month, grouped by Lead Source.
The Ryze AI help center page for Zoho CRM covers the Zoho CRM side of the connection. OpenClaw does not have its own Ryze AI help page; the Ryze AI developers page covers the MCP URL for other clients.
Sources: OpenClaw MCP documentation, OpenClaw MCP transports, Ryze AI Zoho CRM guide. OpenClaw pages checked November 15, 2026.
CLI, Control UI, openclaw.json and API key
OpenClaw CLI
set writes the server definition and login runs the OAuth flow; the credentials stay on the Gateway host. Start the Gateway again afterwards. To see what is saved, openclaw mcp show ryze, list and status print it, and they keep working while the Gateway runs.
openclaw gateway stop
openclaw mcp set ryze '{"url":"https://connector.get-ryze.ai/mcp","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login ryzeControl UI: Settings > MCP
Open the MCP page of the Control UI (/settings/mcp, with /mcp as an alias), choose Add server under Configured servers, name it ryze, pick Streamable HTTP and paste the URL. OpenClaw's docs put the OAuth settings in the scoped config editor on that page, so set auth: "oauth" there and click Sign in. Adding a server needs administrator access. Inside a chat, + > Plugins > Add MCP server saves a server too.
openclaw.json
Edit ~/.openclaw/openclaw.json, which is JSON5, so comments and trailing commas are allowed. The Gateway watches the file and applies the change. Then sign in with openclaw mcp login ryze on a stopped Gateway, or use Sign in under Settings > MCP.
{
mcp: {
servers: {
ryze: {
url: "https://connector.get-ryze.ai/mcp",
transport: "streamable-http",
auth: "oauth",
},
},
},
}A Ryze AI API key instead of OAuth
If you want a Ryze AI API key in place of the browser sign-in, leave out auth: "oauth" and send the key as a bearer header. OpenClaw ignores static Authorization headers while auth: "oauth" is on. Keep the key in an environment variable: a ${RYZE_API_KEY} reference does not trigger the literal-value warning of openclaw doctor when the variable is set.
ryze: {
url: "https://connector.get-ryze.ai/mcp",
transport: "streamable-http",
headers: { Authorization: "Bearer ${RYZE_API_KEY}" },
}A remote entry takes the transport streamable-http or sse, and OpenClaw reads an entry with no transport as sse, so set streamable-http for this address. A request times out after 60 seconds by default, and listing the tools at session start gets 10 seconds when requestTimeoutMs is not set.
OpenClaw and MCP: the facts in one table
| Topic | What OpenClaw's documentation says |
|---|---|
| Where a server is added | Settings > MCP > Add server in the Control UI, + > Plugins > Add MCP server in a chat, openclaw mcp add or set in a terminal, or mcp.servers in ~/.openclaw/openclaw.json |
| Config file | ~/.openclaw/openclaw.json in JSON5, applied by the Gateway when the file changes |
| Transports | stdio for local commands, plus SSE and Streamable HTTP for addresses |
| Sign-in | auth: "oauth" on an HTTP entry, then openclaw mcp login with the Gateway stopped, or Sign in under Settings > MCP for an administrator |
| Whose account | One shared credential that the operator manages by default. Per-requester sign-in needs oauth.identity set to per-requester and gateway.publicOrigin set to an HTTPS origin |
| Approval | MCP tools follow OpenClaw's tool profiles and tool policy. Per-call prompts are documented for Codex runs only |
| Tool names | The agent sees <server>__<tool>, so a Ryze AI tool such as zoho__query can carry the server name as a prefix. Run openclaw mcp doctor ryze --probe to see the exact names |
| Plan | No paid tier; MIT licensed and self-hosted |
| Admin controls | Adding a server from a chat and signing in from Settings need administrator access. enabled: false keeps an entry and hides its tools |
Sources: OpenClaw MCP documentation, OpenClaw config extensions, OpenClaw MCP registry commands. Checked November 15, 2026.
Other clients
The same URL works in other MCP clients. Zoho CRM is connected once in Ryze AI, so nothing changes on the Zoho side.
Claude Code
Claude Code registers the same URL with one claude mcp add command. How to connect Claude Code to Zoho CRM.
Codex
Codex takes the connector URL through its own MCP settings. How to connect Codex to Zoho CRM.
Claude and ChatGPT
Both add https://connector.get-ryze.ai/mcp as a custom connector. In ChatGPT it is an app under Settings > Apps. If the connector was added before Zoho CRM was connected in Ryze AI, remove and re-add it so the tool list refreshes. How to connect Claude to Zoho CRM.
Zoho CRM access and scopes
Four things decide what OpenClaw can reach in your Zoho CRM organization.
- Which login
- The access follows the Zoho user who connects. Use a login whose CRM reach you want your agent to have.
- Which organization
- One connection is one Zoho CRM organization. Several organizations can sit in one Ryze AI workspace: click View on the Zoho CRM card and choose Add one more account. One is the primary and is used unless you name another, and the tools accept an optional connection_id.
- One shared sign-in
- By default OpenClaw's OAuth credential is shared and operator-managed, so everyone who talks to that agent works through the one Ryze AI sign-in behind it. Per-requester sign-in needs gateway.publicOrigin set to an HTTPS origin.
- What stands in front of a change
- No prompt is documented for each call in OpenClaw's built-in runtime. The controls are your tool policy and a toolFilter, described under the tools table below.
Access behind each action
What the Zoho CRM tools can do depends on the scopes granted during the Zoho sign-in. The table lists what Ryze AI documents for the connection.
| Action in Ryze AI | Zoho CRM access |
|---|---|
| Read and edit records in CRM modules | Default Zoho CRM connection |
| Run COQL queries, up to 2,000 rows per call | Default Zoho CRM connection |
| Read fields, modules, users and organization details | Default Zoho CRM connection |
| Create, update and upsert records, up to 100 per call | Default connection, through the write tool |
| Delete records when asked | Default connection, through the separate delete tool |
| Changing modules, fields, layouts or workflow rules | Not documented for the Ryze AI tools. The write tool covers records only |
The 5 Zoho scopes of the default connection
Ryze AI requests five Zoho scopes. Zoho writes each one as service, scope name and operation, so ZohoCRM.modules.ALL means every operation on modules. The table gives what Zoho's scope reference says each scope covers and what the four Ryze AI tools use it for. The Zoho consent screen is the source of truth.
| Scope | What Zoho says it covers | With Ryze AI |
|---|---|---|
| ZohoCRM.modules.ALL | Create, read, update and delete records in every module: Leads, Contacts, Accounts, Deals, Tasks, Calls, Products, Quotes, Invoices, custom modules and the others Zoho lists | Reading records with zoho__read and zoho__query, and changing them with zoho__write and zoho__delete |
| ZohoCRM.settings.ALL | Every settings area, such as fields, layouts, custom views, related lists, roles, profiles, tags and territories. Field metadata and the list of modules are read with it | Reading field and module metadata through zoho__read. The write tool is documented for records only, so do not plan on settings changes |
| ZohoCRM.users.READ | Reading user data. No change to users | Reading the user list, for example to put names to owner IDs |
| ZohoCRM.org.READ | Reading organization data. No change to the organization | Reading organization details with zoho__read |
| ZohoCRM.coql.READ | Running COQL queries. Zoho pairs it with a modules scope, and reading field metadata needs a settings fields scope | Running zoho__query |
Not on the list: the bulk scopes behind Zoho's Bulk Read and Bulk Write APIs, the notification scopes, and write access to users or the organization (users.ALL, org.ALL). This comes from comparing the five scopes with Zoho's scope page; the Zoho consent screen itself was not seen for this guide. Scopes are the ceiling, and the Zoho CRM role of the person who connects still applies under them. Zoho answers NO_PERMISSION (HTTP 403) when that user cannot read a module.
Source: Zoho scopes, Zoho OAuth overview, Ryze AI Zoho CRM guide. Checked November 14, 2026.
Removing access
To cut OpenClaw off, stop the Gateway and run openclaw mcp logout ryze to delete the saved credentials, or openclaw mcp unset ryze to remove the entry. Setting enabled: false on the entry hides its tools and keeps the entry. Zoho's OAuth documentation says a user can revoke a client's delegated access at any time. The Ryze AI documentation used for this guide gives no disconnect step on the Zoho CRM card, so this guide does not describe one.
What OpenClaw can do in Zoho CRM
The Ryze AI connector exposes 4 Zoho CRM tools: two read, one writes and one deletes. Writes and deletes are separate tools, so a filter can treat them differently. The list comes from Ryze AI's integration manifest and has not yet been seen live in a connected workspace.
| Tool | Type | What it does |
|---|---|---|
| zoho__read | Read | Sends a GET request to any Zoho CRM API resource, such as module records, a single record, module settings, fields or users. |
| zoho__query | Read | Runs a COQL query (SQL-like select over CRM modules), up to 2,000 rows per call. |
| zoho__write | Write | Creates, updates or upserts Zoho CRM records, up to 100 records per call. |
| zoho__delete | Delete | Deletes records singly or in bulk. Deleted records go to the Zoho CRM recycle bin. |
Some limits apply to every client, OpenClaw included. Zoho rejects list calls that do not name the fields to return, page-based paging stops at 2,000 records, and a 200 write response can still hold per-record errors that need checking. The connection covers Zoho CRM only.
Approvals and keeping the agent read-only
OpenClaw's docs describe prompts before each MCP call for Codex runs only. In the built-in runtime, MCP tools follow the usual tool profiles and tool policy: the coding and messaging profiles include them, the minimal profile hides them, and tools.deny with bundle-mcp switches them all off. Inside a chat, + > Plugins > Tool access lets you turn off single tools for that session. The Ryze AI chat has its own Tool approvals setting that starts on Skip all approvals and can be switched to Approve write & delete or Manual approve, and scheduled tasks there run without an approval step. In Claude the write and delete tools can be set to Needs approval. None of that applies inside OpenClaw.
To keep the agent from changing Zoho CRM, hide the write and delete tools with a toolFilter on the entry. Names are exact or simple * globs. Run openclaw mcp doctor ryze --probe first to see the names OpenClaw reports.
ryze: {
url: "https://connector.get-ryze.ai/mcp",
transport: "streamable-http",
auth: "oauth",
toolFilter: {
exclude: ["*zoho__write", "*zoho__delete"],
},
}This entry hides the two tools that change Zoho CRM, so only the two read tools stay. The pattern hides these two names only; tools for other connected platforms stay visible.
Limits in numbers
| Limit | What is documented |
|---|---|
| API credits (Zoho) | Per organization, for a rolling 24 hours. Free: 5,000. Standard/Starter: 50,000 plus 250 per user license, up to 100,000. Professional: 50,000 plus 500 per user, up to 3,000,000. Enterprise/Zoho One: 50,000 plus 1,000 per user, up to 5,000,000. Ultimate/CRM Plus: 50,000 plus 2,000 per user, no maximum. Add-on credits come on top. Source: Zoho API limits page. |
| Credits per call (Zoho) | 1 for most calls. COQL: 1 for a LIMIT of 1 to 200, 2 for 201 to 1,000, 3 for 1,001 to 2,000. Insert, update or upsert: 1 per 10 records. Mass delete: 1 per 100 records. Convert Lead: 5. Source: Zoho API limits page. |
| Concurrency (Zoho) | Calls active at once, per organization and app: Free 5, Standard 10, Professional 15, Enterprise 20, Ultimate 25. Heavy calls such as bulk writes and query APIs share a sub-limit of 10 in every edition. No per-minute cap. Source: Zoho API limits page. |
| When a limit is hit (Zoho) | HTTP 429, code TOO_MANY_REQUESTS. Past half the day's credits, responses carry X-API-CREDITS-REMAINING. A super admin can buy more from the API Dashboard. Source: Zoho status codes page. |
| COQL rows | LIMIT defaults to 200 and tops out at 2,000 per query. LIMIT and OFFSET reach at most 100,000 records for one set of criteria. Source: Zoho COQL overview. |
| COQL query shape | Up to 500 selected fields, 25 where criteria, 10 sort fields, 4 group-by fields, 5 aggregates and 100 values in an IN list. Joins through lookups are capped. Select is the only statement. Source: Zoho COQL limitations. |
| Listing records | 200 per page. The fields parameter is required, with at most 50 field API names. Plain paging stops at 2,000 records; a page token, valid 24 hours, goes to 100,000. Source: Zoho get records page. |
| Writes | 100 records per insert, update or upsert call. Partial failure returns HTTP 207 with a result per record. Inserts and upserts run the module's workflows, approvals and blueprints unless the trigger key is sent empty. Source: Zoho insert and upsert pages. |
| Deletes | 100 records per call. Workflow rules run on delete by default. The recycle bin keeps records for 60 days. Source: Zoho delete records page and recycle bin help page. |
| Search | 2,000 records at most, 200 per page, 10 criteria. A just-saved record may not be found yet; Zoho points to COQL for no delay. Source: Zoho search records page. |
| Access tokens | One hour each, renewed with a refresh token that lasts until the user revokes it. Source: Zoho token validity page. |
| OpenClaw request time | 60 seconds per MCP request by default, and 10 seconds to list tools at session start when requestTimeoutMs is not set. Source: OpenClaw config extensions page. |
Sources: Zoho API limits, Zoho status codes, Zoho COQL overview, Zoho COQL limitations, Zoho get records, Zoho insert records, Zoho delete records, Zoho search records, Zoho token validity, Zoho recycle bin, OpenClaw config extensions. Checked November 14, 2026 and November 15, 2026.
First 3 prompts to run
1. Leads by source this month
Run a COQL query that counts Leads created this month, grouped by Lead Source. Then list the three sources with the most leads and show how many of those leads are still unconverted.
Tools used: zoho__query
What comes back: A table of lead sources with a count for each, plus a short list for the top three. The counts come from your own organization. Nothing is changed.
2. Open deals past their closing date
Query the Deals module for open deals with amount, stage, owner and closing date. Show them sorted by closing date, and flag any deal whose closing date has already passed.
Tools used: zoho__query, zoho__read for a single deal
What comes back: A sorted deal list with the past-due deals marked, and a note about any field Zoho would not return. Nothing is changed.
3. Find duplicate-looking contacts
Find Contacts with the same email address in two or more records and list them with their IDs and owners. Do not change anything. After I confirm, update the owner on the older duplicate of each pair.
Tools used: zoho__query, then zoho__write after confirmation
What comes back: A list of contact pairs with IDs and owners. After you confirm, a summary of the updates, with any per-record errors reported.
Each answer comes from your own organization, so this page describes what comes back instead of showing sample numbers. Name the fields you want in a prompt, because Zoho rejects list calls that do not name them.
Asking for COQL
COQL is Zoho's SQL-like query language. Zoho documents joins through lookup fields, aggregates and where clauses, and a LIMIT of up to 2,000 rows per query. Ask your agent to use COQL for counts and filters and to read single records for detail.
10 jobs to hand to OpenClaw
Ten jobs to give an OpenClaw agent in Zoho CRM, with the tool each one calls. None was run for this guide, since no Zoho CRM organization was connected. A Yes means a Ryze AI tool covers the job and the five scopes of the connection cover the call according to Zoho's documentation. The one No is a job the Ryze AI tools do not do.
| Job | Ask OpenClaw | Tool | Works on the default connection |
|---|---|---|---|
| Lead sources | Count the Leads created this month, grouped by Lead Source. | zoho__query | Yes |
| Deal pipeline | List open Deals with amount, stage, owner and closing date, earliest closing date first. | zoho__query | Yes |
| Deals with account data | Show each open deal with two fields from the account it is linked to, in one COQL query. | zoho__query | Yes. Zoho caps the joins in one query |
| Totals by stage | Add up the Amount of open Deals for each Stage. | zoho__query | Yes |
| Field names | List the fields of the Leads module with their API names before writing a query. | zoho__read | Yes |
| Owner names | List the CRM users so owner IDs in my results can be read as names. | zoho__read | Yes |
| Add leads | Create these leads from my list and report the result for each one. | zoho__write | Yes, up to 100 per call, unless you filtered the tool out |
| Merge a contact list | Upsert these contacts so existing ones are updated and new ones are created. | zoho__write | Yes. Zoho matches Contacts on Email by default |
| Remove test records | Delete the three test leads I name in this message. | zoho__delete | Yes, unless you filtered the tool out. They stay in the recycle bin for 60 days |
| New custom field | Add a picklist field to the Deals module. | None | No. The write tool covers records only; Zoho's Module Customization server creates fields |
7 ways to connect OpenClaw to Zoho CRM
There are seven ways to give an OpenClaw agent access to Zoho CRM. This guide treats the first, the Ryze AI connector, as the main way: it is a hosted address, so you run no extra process, create no Zoho app of your own and paste no token. You approve Zoho once and save one address. The other six were read on their vendors' pages on November 14, 2026 and are listed with what each one needs. None of them was run inside OpenClaw.
| Way | Runs where | Setup in OpenClaw | What it reaches in Zoho CRM | Price |
|---|---|---|---|---|
| Ryze AI connector (the main way) | Hosted by Ryze AI. One address for every user, also used by Claude Code, ChatGPT and Cursor | openclaw mcp set, the Control UI or openclaw.json, then openclaw mcp login ryze | Records in every module: reads, COQL up to 2,000 rows, writes up to 100 per call, deletes to the recycle bin. Several organizations per workspace. 4 tools | Tools need a Ryze AI plan or trial; Paid Ads is $89 a month and starts with a 7-day free trial. Adding the connector costs nothing |
| Zoho CRM's four pre-built MCP servers | Hosted by Zoho. Found in Zoho CRM under Setup > Developer Hub > MCP for AI Agents | Zoho has setup pages for Cursor, Claude Desktop, VS Code and Windsurf only. Its docs say the servers work with any AI tool that supports MCP, so the OpenClaw entry is a remote server you save yourself. The pairing was not run | Data Insights (reads, COQL), Data Operations (record create, read, update, delete), Module Customization (modules, fields, layouts), Workflow & Process Automation (rules and tasks). Bounded by your CRM role | No price in the docs. Calls use API credits |
| Zoho MCP console, a server you build | Hosted by Zoho | Add Zoho CRM tools in the console, then copy the MCP URL from the Connect section. Zoho's guide has steps for Claude, ChatGPT, Cursor, Windsurf and VS Code, plus a generic section for custom MCP clients. The URL holds an API key and Zoho says to treat it like a password | The tools you pick, out of 1,319 for Zoho CRM among 76 services. Zoho suggests about 100 per server and 300 at most, and agents act within the user's own permissions | $0 for now, per Zoho, with notice before any pricing |
| Composio | Hosted | Remote MCP address https://connect.composio.dev/mcp, saved as a remote server in OpenClaw. Composio's Zoho pages link to an OpenClaw framework page, so OpenClaw is a named client there. Its Zoho steps were not run | 113 tools: records, COQL, search, notes, tags, attachments, workflow rules, custom fields, layouts, functions and users | Free stops at 10,000 tool calls a month. Standard is $18 per seat per month |
| Zapier MCP | Hosted | Zapier gives you an MCP server tied to your Zapier account. Its quickstart lists other clients, so the OpenClaw entry is a remote server you save yourself | The Zoho CRM actions you enable, such as Create Module Entry, Update Module Entry, Convert Lead and API Request (Beta). No delete in the part of the list shown | 2 Zapier tasks per successful call. Free has 100 tasks a month; Professional starts at $19.99 a month |
| Windsor.ai | Hosted | Add Zoho CRM as a Windsor.ai data source. Its pages describe Claude and ChatGPT, so an OpenClaw entry is unverified | Leads, Deals, Contacts, Accounts, Tasks, Calls, Campaigns, Invoices and custom fields, for analysis. Its pages describe no record changes | Forever Free after a 30-day trial: 1 source, last 30 days. Basic is $23 a month, $19 billed annually |
| CData Zoho CRM MCP server, open source | Java on your computer over stdio | Build with Maven, license the CData JDBC driver, sign in to Zoho through its connection string, then add a command entry. OpenClaw supports stdio servers, but the README covers Claude Desktop only, so the OpenClaw entry was not run | 3 read-only tools: tables, columns and a SQL select | Free under MIT, plus the separately licensed driver. 3 GitHub stars, last push October 18, 2025 |
Options that do not fit this job
- The Zoho CRM connector in Claude's directory. It is a listing in Claude's own directory, made by Zoho, with 41 tools. It speaks about Claude only, so it is not a route for OpenClaw.
- One-click install from Zoho CRM. The MCP for AI Agents page in Zoho CRM has Install buttons for Cursor and VS Code. It has none for OpenClaw.
- Bigin by Zoho CRM. It is a different Zoho product with its own listing in Claude's directory, so its connector does not serve this job.
- Small open-source servers on GitHub. A search for zoho crm mcp returned 36 repositories. The most starred one, with 14 stars, only builds a demo server with an add tool and makes no Zoho CRM call, and the rest have 4 stars or fewer.
- ClawHub. OpenClaw's public plugin registry has no Ryze AI plugin, so the connector is saved by address as in the steps above. A ClawHub search for ryze on November 15, 2026 returned only an unrelated community package.
Which one to pick
Ryze AI is the best way to connect OpenClaw to Zoho CRM when you want COQL queries and record edits behind one address that OpenClaw, Claude, ChatGPT and Cursor share, across several Zoho CRM organizations in one workspace, with one caveat: its write tool covers records only, so new fields, layouts, workflow rules and other Zoho apps need Zoho's own servers, and the tools need a Ryze AI plan. Admins who reshape modules, fields or workflows want Zoho's pre-built servers, and the Zoho MCP console fits a server that mixes Zoho CRM with other Zoho apps or third-party tools, with calls counted against Zoho API credits and the console at $0 for now, though Zoho names no OpenClaw steps for either. Composio is the one alternative whose pages name OpenClaw. Zapier suits teams already on it, Windsor.ai suits reporting, and the CData server suits a read-only setup on the Gateway machine.
Sources: Zoho CRM MCP overview, Zoho CRM MCP FAQ, Zoho built-in MCP announcement, Zoho CRM listing in Claude's directory, Zoho MCP, Zoho MCP pricing, Zoho MCP implementation guide, Composio Zoho toolkit page, Composio pricing, Zapier MCP for Zoho CRM, Zapier MCP usage, Windsor.ai Zoho CRM page, Windsor.ai pricing, CData Zoho CRM MCP server, OpenClaw ClawHub, Ryze AI Zoho CRM guide. Zoho and vendor pages checked November 14, 2026.
OpenClaw, Zoho CRM and MCP: dates that matter
| Date | What happened |
|---|---|
| July 17, 2025 | Zoho's press release announced its own MCP server, with more than 15 Zoho tools in early access and general availability expected towards the end of 2025. |
| March 9, 2026 | Zoho published its launch post for Zoho MCP, last updated March 10, 2026. |
| March 31, 2026 | OpenClaw 2026.3.31 added remote HTTP and SSE servers by URL under mcp.servers, with auth headers and an optional streamable-http transport. |
| April 6, 2026 | Zoho announced built-in MCP support in Zoho CRM, the pre-built servers, rolling out in phases across its data centers. |
| August 31, 2026 | OpenClaw 2026.8.1, also called OpenClaw 2.0, added servers from the chat composer and per-requester OAuth for shared MCP servers. |
| September 23, 2026 | OpenClaw 2026.9.6 let administrators sign in to MCP connectors from Settings. |
| October 2026 | Zoho MCP's changelog shows its latest Zoho CRM release: 95 tools added and 85 removed, for the US, EU, IN, AU, JP, CA and SA data centers. |
| November 3, 2026 | OpenClaw 2026.10.10 began protecting MCP configuration while the Gateway runs. The commands openclaw mcp set and login now need the Gateway stopped. |
| November 14, 2026 | Zoho's tool manual lists 1,319 Zoho CRM tools, Zoho's docs describe four pre-built servers, and the Zoho MCP pricing page says $0. |
Sources: Zoho press release, July 17, 2025, Zoho MCP launch post, Zoho built-in MCP announcement, Zoho MCP changelog, Zoho CRM MCP overview, OpenClaw releases, OpenClaw 2026.3.31 changelog, OpenClaw 2026.10.10 release notes. Checked November 15, 2026 and November 14, 2026.
How this guide was tested
No call to Zoho CRM and no step inside OpenClaw was run for this guide, so the record is short. The pages behind it were opened on the dates below.
| What was checked | Result |
|---|---|
| Zoho CRM sources (November 14, 2026) | Zoho's API v8 pages for limits, scopes, COQL, records and status codes, its MCP pages for the pre-built servers and the console, and the vendor pages in the ways table were opened and compared with the Ryze AI facts. |
| OpenClaw sources (November 15, 2026) | OpenClaw's MCP, transports, registry, configuration and release pages were opened. The CLI commands, config keys and limits on this page come from them. |
| The Zoho CRM tool list | Not seen live. The four tool names come from Ryze AI's integration manifest, because no workspace has Zoho CRM connected. |
| Calls to Zoho CRM | None. No Zoho CRM test account was connected, so no tool was called and no Zoho response is quoted on this page. |
Not run for this page: every step inside OpenClaw. No Gateway was installed or started, no server was saved and no sign-in was attempted. The OpenClaw steps follow its documentation and changelog as read on November 15, 2026, and the Zoho limits and error codes follow Zoho's documentation from November 14, 2026. The write and delete tools were not run, because they change Zoho CRM.
OpenClaw and Zoho CRM errors and fixes
Error codes and messages from the documentation
These come from documentation, not from a run. The Zoho codes are listed on Zoho's API v8 pages and the OpenClaw message in OpenClaw's own docs. None was seen on a live connection for this guide.
| Message or code | What it means | What to do |
|---|---|---|
| authentication refused (401) | OpenClaw's docs say this appears in the startup log and catalog diagnostic when a Streamable HTTP server answers initialization with HTTP 401, which is how a server asks for a sign-in. | Run openclaw mcp login ryze with the Gateway stopped, or click Sign in under Settings > MCP. |
| REQUIRED_PARAM_MISSING (HTTP 400): One of the expected parameters is missing. | Zoho documents this for a list call without the fields parameter. | Name the field API names you want, or ask for a COQL query instead. |
| LIMIT_EXCEEDED (HTTP 400): Fields limit exceeded. | More than 50 field API names in the fields parameter. | Ask for 50 fields or fewer. |
| DISCRETE_PAGINATION_LIMIT_EXCEEDED (HTTP 400): You can only get the first 2000 records without using page_token param. | Paging past 2,000 records with the page parameter. | Page with the page token, which expires after 24 hours, or narrow the COQL where clause. |
| NO_PERMISSION (HTTP 403): Permission denied to read records | The connected Zoho user cannot read that module. | Ask a Zoho admin for the access, or connect with a login that has it. |
| TOO_MANY_REQUESTS (HTTP 429) | The organization's API credits for the 24 hours ran out, or too many calls ran at once. | Wait for the credit window to roll over, or ask for fewer and narrower queries. |
| LIMIT_REACHED (HTTP 400): Maximum response iteration limit reached | A search matched more than 2,000 records. | Use a COQL query with a narrower where clause. |
Other problems
- The Zoho CRM tools do not appear in OpenClaw
- Until shared credentials exist, OpenClaw leaves the server out of the agent runtime instead of failing the turn. Run openclaw mcp login ryze with the Gateway stopped, then check with openclaw mcp status or openclaw mcp doctor ryze --probe. If you saved the connector before Zoho CRM was connected in Ryze AI, remove the entry and save it again.
- The tool list is empty or times out
- The tool list at session start gets 10 seconds when requestTimeoutMs is not set. Raise requestTimeoutMs on the entry, and confirm transport is streamable-http, because OpenClaw reads a missing transport as sse.
- The sign-in page opens on the wrong machine
- Approve it in the browser, then give the code it returns to openclaw mcp login ryze with --code.
- The API key is ignored
- Static Authorization headers are ignored while auth: "oauth" is on. Remove auth for the key route, or remove the header and use OAuth.
- An openclaw mcp command holds back
- Since OpenClaw 2026.10.10 (November 3, 2026), commands that change saved servers, and login, need the Gateway stopped. Stop it, run the command and start it again, or edit openclaw.json, or use Settings > MCP.
- A write says success but a record did not change
- Zoho documents HTTP 207 for a batch where some records fail, and Ryze AI notes that even a 200 response can hold per-record errors. Ask the agent to report the result for every record it wrote.
- The wrong Zoho CRM organization answers
- Each connection is one organization. Click View on the Zoho CRM card, check which one is primary, and name the other organization in your prompt.
- The login worked but the data center is wrong
- Any data center works, but each one holds only the data of users registered there. Sign in to the Zoho region where your CRM organization lives.
- Results stop at 2,000 records
- Page-based paging ends at 2,000 records. Beyond that Zoho needs a page token, which expires after 24 hours. Ask the agent to page with the token, or to narrow the COQL where clause.
- Calls fail after heavy use
- Zoho limits API credits and concurrent calls per organization and answers HTTP 429 when either runs out. Wait for the credit window to roll over or ask for fewer, narrower queries.
- The tools reply that a subscription is required
- The Zoho CRM tools need an active Ryze AI plan or free trial. Start the trial, then retry.
Terms on this page
- MCP
- The Model Context Protocol, an open standard for connecting AI applications to outside systems. OpenClaw, Claude and ChatGPT support it.
- Gateway
- The OpenClaw process that runs your agents and keeps their settings, MCP servers and saved sign-ins.
- openclaw.json
- The JSON5 settings file at ~/.openclaw/openclaw.json. MCP servers live under mcp.servers.
- COQL
- CRM Object Query Language, Zoho CRM's SQL-like select language. It uses module and field API names and can join modules through lookup fields.
- API credit
- The unit Zoho CRM counts API use in. Most calls cost 1 credit and each edition has an allowance for a rolling 24-hour window.
- Scope
- A permission an app asks for at sign-in, written as service.scope.operation, for example ZohoCRM.modules.ALL.
- Recycle bin
- Where deleted Zoho CRM records go. They can be restored for 60 days and are then permanently deleted.
Source for MCP: modelcontextprotocol.io. Checked November 15, 2026.
Frequently asked questions
How do I connect OpenClaw to Zoho CRM?
The main way is the Ryze AI connector. Connect Zoho CRM in Ryze AI under Integrations by signing in to Zoho and approving CRM access. Then save https://connector.get-ryze.ai/mcp in OpenClaw as a streamable-http server with auth set to oauth, using openclaw mcp set, Settings > MCP or openclaw.json, and sign in with openclaw mcp login ryze.
Is there a Zoho CRM MCP server for OpenClaw?
Yes. The Ryze AI connector is one: its address is https://connector.get-ryze.ai/mcp and it has 4 Zoho CRM tools. Zoho also publishes four pre-built Zoho CRM MCP servers and the Zoho MCP console, though no Zoho page opened names OpenClaw as a client.
What is the Zoho CRM MCP server URL for OpenClaw?
For the Ryze AI connector the address is https://connector.get-ryze.ai/mcp, the same for every user. Zoho's own servers give you a URL from Zoho CRM under Setup > Developer Hub > MCP for AI Agents, or from the Connect section of the Zoho MCP console, where it holds an API key to guard like a password.
Does Zoho have an official MCP server?
Yes. Zoho CRM has four pre-built MCP servers (Data Insights, Data Operations, Module Customization and Workflow & Process Automation), announced on April 6, 2026, and Zoho MCP is a separate service for building your own server. Zoho also has a Zoho CRM connector in Claude's directory with 41 tools.
Does Zoho's own MCP server work with OpenClaw?
No Zoho page opened on November 14, 2026 names OpenClaw. Zoho's docs say the pre-built servers work with any AI tool that supports MCP, and OpenClaw supports remote MCP servers by URL, but the pairing was not run.
Can OpenClaw edit my Zoho CRM records?
Yes. Through Ryze AI, an OpenClaw agent can create, update and upsert records with the write tool, up to 100 per call. The tool covers records only, so it does not add fields, change layouts or edit workflow rules.
Can OpenClaw delete Zoho CRM records?
Only through the separate zoho__delete tool, when you ask for it. Deleted records go to the Zoho CRM recycle bin, which keeps them for 60 days. A toolFilter with an exclude list on the ryze entry hides the delete tool from the agent.
Does OpenClaw ask before it changes Zoho CRM?
OpenClaw's docs describe per-call prompts for Codex runs only. In the built-in runtime, MCP tools follow tool profiles and policy. To require a pause before changes, hide the write and delete tools with a toolFilter and enable them only when you want a change made.
Which OpenClaw plan do I need?
None. OpenClaw is MIT licensed and self-hosted, and its docs say it has no paid tier. The model provider your agent uses has its own costs, which are outside this guide.
Which Zoho permissions do I need to connect?
A Zoho login that can approve access to CRM modules, settings, users and organization details. The access follows that user's CRM role, so Zoho answers NO_PERMISSION (HTTP 403) when the user cannot read a module. Any Zoho data center works.
Can I connect more than one Zoho CRM organization?
Yes. Several organizations can be connected to one workspace under View > Add one more account on the Zoho CRM card. One is the primary and is used unless you name another, and the tools accept an optional connection_id.
Why do the Zoho CRM tools not show up in OpenClaw?
Until shared credentials exist, OpenClaw leaves the server out of the agent runtime. Run openclaw mcp login ryze with the Gateway stopped. If you connected Zoho CRM in Ryze AI after saving the server, remove the ryze entry and save it again so the tool list refreshes.
How many records can a Zoho CRM query return?
A COQL query returns at most 2,000 rows per call, and LIMIT with OFFSET reaches at most 100,000 records for one set of criteria. Listing records pages 200 at a time and stops at 2,000 without a page token.
How much does it cost to connect OpenClaw to Zoho CRM?
Adding the connector costs nothing, but the Zoho CRM tools need an active Ryze AI plan or free trial. Paid Ads is $89 per month with a 7-day free trial, SEO Starter is $129 per month with a 3-day free trial and Agency is $279 per month. Annual billing takes 30% off the first year.
How do I disconnect Zoho CRM from OpenClaw?
Stop the Gateway and run openclaw mcp logout ryze to delete the saved credentials, or openclaw mcp unset ryze to remove the entry. Setting enabled: false on the entry keeps it but hides its tools.