01 · Records and state owned
Standard and custom module records, related records, module and field schemas, custom modules and fields, page layouts, workflow rules, workflow task actions, and automation configuration.
Zoho
Zoho CRM
Zoho CRM is included for four composable hosted MCP servers that separately expose read-only analytics, record operations, CRM schema customization, and workflow-rule administration to supported AI clients.
CRM, revenue & customerSystem of recordExtensible SaaS
Concrete capability record
Data, retrieval, actions, identity, and operating limits
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
02 · Data you can retrieve
Data Insights queries records with COQL and returns module/field metadata without mutation; the other servers also read records, related data, schemas, layouts, and workflow configuration needed for their operations.
03 · Actions and write paths
Data Operations supports record CRUD, bulk changes, and related-record updates; Module Customization can create modules/fields and change or activate layouts; Workflow & Process Automation can create, update, and reorder rules and task actions.
04 · Authentication and permissions
The first tool invocation starts a Zoho OAuth flow. Every action is limited to the authenticated user's CRM role and organization; switching users or orgs requires disconnecting and re-authenticating the server.
05 · Monitoring, approval, and recovery
Install only the server families required for the persona, rely on Zoho user permissions and the audit trail, and treat Data Operations, Module Customization, and Workflow Automation as distinct change domains. MCP calls consume the same API credits as standard API calls.
06 · Limits and caveats
Four pre-built servers rather than one universal catalog; calls consume existing API credits; sessions are bound to the authenticated user and organization; using multiple servers broadens record, schema, and automation authority; public docs do not state plan, region, rate, or retention details.
First-party access
Documented surfaces
COQL structured query ↗Zoho CRM Object Query Language provides read-only SELECT-style, cross-module queries and aggregates. Field, criteria, page-size, API-credit, and total-retrieval limits apply.Source: COQL OverviewMCP / agent surface ↗Verified first-party provider MCPAPI ↗Developer accessDeveloper docs ↗SDKs and platform guidanceEvents / extensions ↗Webhooks, apps, or extensionsProduct ↗Native platform experience
Agent access
MCP support
Official MCP serverFour Zoho-hosted composable CRM MCP servers for insights, records, schema, and automationCurrent documented service
Support: Official MCP server
Read scope: COQL record query, filtering/grouping/pagination, module lists and field schemas through Data Insights; supporting reads of related records, layouts, and workflow configurations through the other selected servers.
Write scope: Record CRUD and bulk/related changes; custom module and field creation; layout update/activation/deactivation; and workflow rule or task creation, update, and ordering. Write authority depends on which server is installed and the Zoho CRM user role.
Authentication: Interactive Zoho OAuth initiated on first tool use; disconnect and re-authenticate to change the active Zoho user or CRM organization.
Approval boundary: Zoho documents OAuth, user permissions, server selection, and auditability but not universal per-action confirmation. BYO-UI should confirm record deletion/bulk changes, module or field creation, layout activation, and workflow-rule changes; Data Insights can remain read-only.
Protocol does not erase product boundaries.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
Access-maturity dimensions
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility4
Portability3
Observability3
Documentation4
Proposed customer-shaped experiences
What customers could create on top.
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Zoho ships them.
Single-platform patterns
- SMB CRM, workflow, and customer-operations cockpit
- Account journey room
- Pipeline-quality debugger
- Customer expansion cockpit
Multi-platform compositions
- Zoho CRM + marketing or intent platform: account journey room
- Zoho CRM + conversation or support system + analytics or warehouse: cross-system decision workspace
Evidence and dates
First-party references, with publisher and review dates separated
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
7 recorded sources
MCP technical overviewRepresentative source
https://www.zoho.com/crm/developer/docs/mcp/overview.html ↗Zoho CRM MCP tools, permissions, sessions, and limits
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
Zoho CRM MCP tools, permissions, sessions, and limits reviewed from live first-party material on 2026-07-22.
APISource inventory
https://www.zoho.com/crm/developer/docs/api/v7/ ↗First-party API reference or API overview recorded for this platform.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Developer docsSource inventory
https://www.zoho.com/crm/developer/ ↗First-party developer documentation or platform overview.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Developer docsSource inventory
https://www.zoho.com/crm/developer/docs/api/v8/COQL-Overview.html ↗Reverified the named access facet exactly as bounded by the reviewed first-party record.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 12, 2026
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
HomepageSource inventory
https://www.zoho.com/crm/ ↗First-party product homepage used to confirm product identity and current positioning.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
MCP / agent-role validationSource inventory
https://www.zoho.com/crm/developer/mcp.html ↗server composition, OAuth, user permissions, audit trail, and supported-client positioning
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 22, 2026
Four-server composition, OAuth, permissions, audit, and client positioning reviewed 2026-07-22
Webhooks / extensionsSource inventory
https://www.zoho.com/crm/developer/docs/api/v7/notifications/enable.html ↗First-party webhook, event, SDK, embedded-app, or extension documentation.
- Publisher updated
- Not stated by publisher
- BYO-UI reviewed
- Jul 10, 2026
Inventory source: structurally normalized; content was not individually reopened in this pass.
Verified fact
Tied to cited first-party evidence reviewed for this profile.
Source inventory
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
Editorial assessment
System role, maturity interpretation, and architectural boundary.
Proposed design
Interface patterns and compositions—not vendor product claims.