Get Started With Zoho MCP
What is MCP?
Model Context Protocol (MCP) is an open protocol that establishes the standardized manner in which applications can interact with Large Language Models (LLMs). Leveraging MCP allows you instruct the the LLM in the right context to carry out your desired workflow.
With MCP in place, you can instruct popular AI agents or even custom AI agents to interact with native or third-party applications and complete complex workflows with little to no human intervention.
What is Zoho MCP?
Zoho MCP is a robust new service from Zoho that allows you to create your own MCP servers. With Zoho MCP servers you can perform complex workflows across multiple Zoho applications or third-party services.
The biggest advantage of employing a Zoho MCP server is that it provides you with a host of 300+ Zoho and third-party MCP-ready applications that you can use to configure your required MCP tools to allow your preferred AI agent to perform the necessary operations.
Instruct your AI agent in simple natural language on the tasks you want accomplished in other Zoho or third-party MCP-ready services, and the entire workflow will be carried out from initiation to completion by the chosen AI agent powered with the proper context from the tools configured in the Zoho MCP server.
The following diagram will provide you with an overview of the functionality that Zoho MCP provides:
Along with the illustration above:
- Once the user prompts their MCP Client to execute the required operations, the MCP Client, extracts context from the entered prompt.
- Based on the extracted context, the configured tools present in the Zoho MCP server are matched, and the required actions are carried out in the respective services.
- All of these actions happen inherently without any manual intervention beyond the initial prompt.
Consider the following example: You have completed a deal with a client, and you need to onboard them. The following are the general steps that you would need to manually undertake to ensure the client is properly onboarded and handed over to the right personnel:
- Send out a welcome email, to your new client with a copy of the Master Services Agreement document.
- Generate the required invoice and email that to your client, and CC your Accounts Lead in the email.
- Send the client an onboarding link.
- Book the necessary follow-ups with the client.
- Mark the deal as Closed in your CRM, and move the module along to the next team and alert the next person of contact to handle the client's account.
Now, accomplishing all of these tasks is of utmost priority, but they also require a great deal of manual input and intervention, and these actions are distributed across various services and teams. Any unintended mishap can lead to negative consequences. This puts the entire system under tremendous strain, and the room for errors is high. However, with the Zoho MCP service, we can put in place a system that is optimized, seamless, and error-free.
For our above example, let's consider that Claude as your MCP Client, your leads are managed in Zoho CRM, the emails are going to be sent to the client using Zoho Mail, the invoice is generated using Zoho Books, and the Master Services Agreement document is retrieved from the Zoho WorkDrive and emailed to the concerned user.
Once the required configurations are performed in your Zoho MCP server and your preferred AI agent, you just have to provide a prompt, something similar to:
"Can you send an email with our standard sales completion template to the recently closed deal and attach the relevant access links of the Master Services Agreement document present in the WorkDrive. Also, attach the access link to view the invoice from Zoho Books and CC our accounts admin to this email."
The MCP Client will be able to extract the required context from this prompt, no additional code is required, and no additional input will be required.
The following video demonstrates the above example:
As detailed in the demonstration, all of the required actions occur autonomously, and the entire workflow is carried out with no manual intervention or input beyond the initial prompt.
Zoho MCP Behaviour
Zoho MCP is a service that allows you to create your required MCP server and configure tools from Zoho and third-party MCP-ready services. The defined behavior of the service is that:
- You can create MCP servers using the Zoho MCP service, and configure them with the required MCP tools.
- Once the Zoho MCP server is connected to your MCP Client, and you have authorized the MCP Tool actions, you can begin prompting it.
- The following then occurs:
- Leveraging the intelligence of the MCP Client, the context is extracted from the user's natural language prompt.
- The MCP Client, then matches the extracted context with the MCP Tools that are configured in the MCP server, to carry out the required operations.
Worth Noting:
- Zoho MCP is not AI. It is a service that lets you create your own MCP server. The MCP Tools that can be added to your MCP server are dependent on the actions that the service is willing to expose to the MCP Client. For example, sendEmail is a tool that the Zoho Mail service provides to the MCP client via the Zoho MCP server, which allows the MCP Client to send emails. However, there is no Tool from the Zoho Mail service that allows you to download attachments from emails. This means there is no way your MCP Client can download an attachment.
- We leverage the MCP Client's intelligence to perform the required operations.
- The Zoho MCP service, allows you to create an MCP server and configure it with the required tools which will provide context and instruct the MCP client on the actions it can perform in the configured services.
- If your MCP Client is not able to perform the exact expected operation, it can be because:
- The MCP server has not been configured with the right tool. Learn about supported MCP Tools.
- The MCP Client got a convoluted prompt where the right context could not be extracted.
- Limitations in the MCP Client, or a lack of tool support from the required service.
Zoho MCP vs. Traditional APIs
The following table will compare and detail the optimizations that can be possible when you choose to complete your operations using Zoho MCP over Traditional APIs.
Category | Zoho MCP | Traditional APIs |
Mode of Operations | Completely autonomous. | Automated at best. |
Operations | Entirely handled by your preferred MCP Client. Beyond the initial prompt, no manual intervention is required from task initiation to completion. | Each execution requires manual intervention and is dependent on various external factors, such as, availability of API endpoints, token validity, rate limits, and so on. |
Setup and Configuration | Typically a one-time setup. Configure your Zoho MCP server with the required tools and connect it your required MCP Client and the rest is handled by the MCP Client. | Each API integration requires individual setup, authentication, and ongoing maintenance. |
Operations Discovery | Leveraging its artificial intelligence, the MCP Client will be able to gather relevant context from your natural language prompt, and automatically discover the available commands, and structure parameter metadata for autonomous operation. | Requires manual API exploration. |
Parameter Handling | Capable of handling complex parameter relationships. Also supports dynamic parameter resolution and context-aware input handling. | Requires manual input with strict, static parameter handling only. |
Operations Workflow | All linked services operate in complete harmony through MCP protocols, executing seamlessly without additional authorization or intervention. | Typically, no meaningful harmony exists between services, even if they belong to the same ecosystem. Each service must be launched individually with operations carried out in silos. |
Context Awareness | Retains and leverages context across the entire workflow ensuring seamless interconnected operations. | Every API call is independent. No context awareness possible. |
Error Handling | MCP Clients can contextually interpret errors and attempt recovery autonomously without manual intervention. They will always try to fulfill the exact instruction, or at the very best provide the closest most relevant output possible. | Typically requires predefined error handling logic manually coded for every possible scenario. |
Security & Authorization |
| Rigidly static. You have to define access control manually and individually configure for every integration. |
Process Optimization | All aspects of a workflow are carried out autonomously regardless of complexity, significantly reducing time, effort, and overhead. | Individual services may be automated but cannot operate as a unified autonomous workflow, offering only marginal optimization. |
Robust Authorization With Flexible Options
When you add a tool from a Zoho or third-party service to your Zoho MCP server, you need to authenticate this addition using OAuth2.1 protocol. The Zoho MCP service allows you to establish this authorization using two methods:
- Authorization on Demand
- Authorization Via Connection
Category | Authorization on Demand | Authorization via Connections |
Definition | This is the default authorization type used to add MCP Tools from Zoho services to your Zoho MCP server. Each time you add a MCP Tool to your server, you need to authenticate it using OAuth2.1 protocols. | This is an additional authorization offered to authenticate the addition of MCP Tools to your server. Typically used to authenticate adding MCP Tools from third-party services. This method of authorization allows you to share Access Tokens and Refresh Tokens to trusted members of the org, to authenticate and provide access. |
Dependency | This method is account-dependent. Each user authenticates and authorizations the Tools using their account. | This method is Organization-dependent. Authorization can be shared from the Super Admin of the Org to their members. |
Functionality | Each user though using the same Zoho MCP server will need to authenticate the MCP Tools and actions using their individual accounts. | If you're the Super Admin of your organization, you can share the required OAuth Access and Refresh Tokens to members of your organization so that they can authenticate the MCP Tools and actions using the shared tokens instead of individual authentication. |
Ideal Implementation | Best suited for cases where individual users like solopreneurs or in cases where individual accountability is a priority. | Best suited for teams. This method streamlines authorization requirement through shared access, eliminating individual overhead. |
Primary Advantage | Since authentication is handled individually for each user, access is scoped in a more strict manner. This provides for more comprehensive security. | Centralized access control under the Super Admin of the organization. Without the need for individual accounts, the members of the team can easily begin using the Zoho MCP service using the shared access. This method also ensures consistent access levels and permissions throughout the organization. |
Example | Consider that you and a peer are both working with the same Zoho MCP server. You both use the tools from Zoho CRM, and Zoho Mail service. To authorize and use the required tools, you each would need to have individual accounts in the Zoho CRM and Zoho Mail services. | Imagine that you are the Super Admin of an organization containing four team members. All of you are using the same Zoho MCP server configured with MCP Tools from TrainerCentral and Zoho Cliq. Instead of each member creating individual accounts to authorize and use the actions, they can use the Super Admin's authentication tokens and begin implementing Zoho MCP server for their operations. |
Pre-Configured Servers
The Zoho MCP service, offers you a vast list of pre-configured servers that you can directly authorize and connect to your required MCP Client, and skip the entire process of creating a Zoho MCP server from scratch.
Sometimes, creating a Zoho MCP server to accomplish workflows like manipulating CRM Data and Metadata operations, or comprehending your application's engagement and screen analytics, require knowing to add the exact MCP Tool from the exact service. This can be a hassle if you're new to the service and are expertly aware of all the functionalities and service offerings.
In these cases, you can simply search our list of Pre-Configured Servers that fits your required use case, and authorize the added MCP Tools.
This removes the entire overhead of creating a Zoho MCP server from scratch and enables you to implement your required workflow soon as possible. These servers are not just plug-and-play models, they can be further customized as well. Meaning, you can add and remove your required MCP Tools to satisfy the demands of your use case.
MCP Server URL
An MCP Server URL is the access URL provided to your MCP Client to connect to and invoke the required MCP server and its tools.
The URL is automatically generated by the Zoho MCP service, when you create your server. Your URL will contain the required secure API Key to ensure proper authorization is followed when you connect to your required MCP Client.
You are also provided with the option to regenerate API Key if you feel the MCP Server URL has been compromised in someway.
Caution: Treat your MCP Server URL as you would your password! Your secure MCP Server URL essentially acts as an access URL using which you can trigger actions permitted by the MCP Tools configured to your server.
Collaborators
Collaborators is a feature in the Zoho MCP service, that allows you to add trusted members to your organization. When you create a Zoho MCP account, you will have the option to send out email invites. Anyone that you do invite will act as the collaborator and you will be the Super Admin of the organization.
As the Super Admin, you will have complete access to all the features of the Zoho MCP service. As for the Collaborators, they can be assigned to two roles:
- Admin: Can manage the other collaborators of the organization, in addition to being able to access all MCP features.
- User: Can only access all MCP features.
Using the Collaborators feature:
- Your team can use your MCP server to perform team operations instead of having to create individual MCP servers.
- You can offer access to your Zoho MCP servers without sharing credentials.
- You can ensure consistent operations throughout your configured services, as the MCP server configurations are handled by you and shared with your collaborators.
- You have better access control.
Logs
Logs is a feature in Zoho MCP that indexes all accesses made through the MCP Tools configured in your Zoho MCP server.
The result of every action made by the invoked tool on its respective service will be indexed in the Logs section and communicated using standard HTTP Codes. The shelf life of the logs is 30days beyond which they will continue to be deleted.
If you are following Authorization on Demand, auditing the log actions performed on your MCP server is much more accurate (using ZUID) when compared to auditing the actions performed using the Authorization via Connections.
You can filter and search for the required log by filtering by time executed and tool used.
Whats Next?
- Use the Quick Start Guide to execute your first workflow using Zoho MCP.
- Go through the Glossary to familiarize yourself with some of the terminology.
- Go through the implementation guide to learn more about using the Zoho MCP service.