Zoho CRM MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZOHO_REGION | No | One of com, eu, in, com.au, jp | com |
| ZOHO_TIMEOUT | No | HTTP timeout in seconds | 30 |
| ZOHO_CLIENT_ID | Yes | OAuth2 client id | |
| ZOHO_CLIENT_SECRET | Yes | OAuth2 client secret | |
| ZOHO_REFRESH_TOKEN | Yes | OAuth2 refresh token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_recordsA | List records from a Zoho CRM module. Args:
module: API name of the module (e.g. |
| get_recordC | Fetch a single record by id from the given module. |
| create_recordC | Create one or more records in the given module. |
| update_recordC | Update a single record with a partial payload. |
| delete_recordC | Delete a single record by id. |
| search_recordsB | Search records by Exactly one of the four search parameters must be supplied. |
| list_modulesA | List every available module in the connected Zoho CRM org. |
| get_moduleC | Fetch metadata for a single module. |
| list_usersB | List users visible to the authenticated principal. Args:
type: Zoho user filter, e.g. |
| coql_queryC | Run a COQL |
| list_related_recordsB | List records from a related list of a parent record. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct operation (e.g., query vs. create vs. search vs. list), with no overlap. Even similar tools like list_records and search_records have clearly different parameters and purposes.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., create_record, list_modules, coql_query). The acronym 'coql' is the only minor deviation but still readable.
11 tools cover CRUD, listing, search, related records, users, and metadata. This is well-scoped for a CRM server—enough functionality without being overwhelming.
Full CRUD and search operations are present. Minor gaps include no bulk operations or advanced CRM workflows (e.g., lead conversion), but the core record management lifecycle is well covered.