Component Model
| Component | Role | Examples |
|---|---|---|
| MCP Client | Where the user inputs prompts; sends requests to MCP Server | Claude, ChatGPT, Cursor, Windsurf, VS Code Copilot, CrewAI |
| Zoho MCP Server | Translates MCP requests into Zoho API calls; manages authentication, tool registry, lifecycle | zohomcp.com infrastructure |
| Tools | Specific, permissioned actions registered on the server | SearchRecords, sendEmail, CreateInvoice, GetRecords |
| Services | Target applications whose APIs the MCP Server calls | Zoho CRM, Zoho Mail, Zoho Books, third-party apps |
| Connections | OAuth tokens (on-demand or org-shared) authorizing actions | Per-user or Super Admin–shared |
Data Flow (Four-Step Lifecycle)
[1] User Prompt in MCP Client
↓
[2] Agent gathers context (JSON structure with module, instructions)
↓
[3] MCP Server selects right tool, calls target API (e.g., POST /crm/v2/Leads)
↓
[4] API returns result (success/failure JSON) → MCP Client displays to user
[1] User Prompt in MCP Client
↓
[2] Agent gathers context (JSON structure with module, instructions)
↓
[3] MCP Server selects right tool, calls target API (e.g., POST /crm/v2/Leads)
↓
[4] API returns result (success/failure JSON) → MCP Client displays to user
Source: Zoho MCP product page
Design Principles
- Schema-first: Self-describing APIs with clear input/output contracts
- Unified interface: Consistent patterns across all Zoho apps
- Drop-in compatibility: Works with any agent framework out of the box
- Permission-scoped: All agent actions operate under the authenticated user's role and permissions
- Autonomous-capable: Works for interactive prompts and fully autonomous scheduled agents