What is a Progressive MCP server?
A Progressive MCP server is a Zoho MCP server type that removes the need to manually select and load tools. You only select the Zoho products you need. When you prompt a compatible AI client, it finds and runs the right tools from the authorized tool set to perform the required actions.
How does a Progressive MCP server work?
A Progress MCP server is loaded with five tools, irrespective of the Zoho Product configured to be loaded in the server:
- ZohoMCP_listProducts: To fetch list of products associated with the server.
- ZohoMCP_getFeatures: To fetch list of features in a product.
- ZohoMCP_listTools: To fetch list of tools in a feature or product.
- ZohoMCP_getSchema: To fetch a tool's schema before invoking.
- ZohoMCP_executeTools: To invoke the requried tool with necessary parameters.
Based on the context gathered from the execution of these tools, the AI Client will be able to match the context from your prompt and invoke the right tool form the configured product and complete its execution.
The following illustration details the functionality and the sequence of tool executions in a Progressive MCP server.
The five Zoho MCP tools will allow the AI Client to discover the required tool through progressive discovery.
Conventionally, an AI client would check against every tool that has been configured in the Zoho MCP server against its requirement and then invoke the required tool. This is an exhaustive search, which at times exceeds an AI client's context length leading it to hallucinate and burn through your tokens. This limitation on AI client's context size made us set the tool limit of a single MCP server at 300.
But, now with Progressive MCP servers, this tool limit is invalid. While Zoho products are configured to the Progressive MCP servers, their tools are only loaded based on your authorization, the AI client's requirement.
This also makes the soft limit of only loading 300 tools per MCP server invalid, and removes your manual action of loading the required MCP tools to your server.
Permitted Actions
Once you've selected your required Zoho Products that needed to be configured to your Progressive MCP server, you have further control to select the permitted actions based on their scope of action. For example, you can choose if your AI client can only perform Read actions, or if your AI client has full access to perform all actions possible in the configured Zoho product, through your MCP server.
You can set the required permitted actions, using the following three options:
- View Only: Only MCP Tools that perform Read, Search, and Retrieve actions.
- View, Create & Modify: Only MCP Tools that perform Create, and Edit actions along with View Only actions.
- Full Access: Permits all Create, Read, Update, and Delete (CRUD) actions available as MCP tools in the configured Zoho products.
Note: Permitted actions apply to all the products configured in your Progressive MCP server. For example, if you’ve added Zoho CRM, Zoho Desk, and Zoho Books to your Progressive MCP server, the permitted actions you set apply to the tool sets of all three products. You cannot set View Only for Zoho CRM and Full Access for Zoho Desk and Zoho Books. If you do require your permitted actions to be handled exclusively, then you need to configure your Zoho products in a Progressive MCP server based on the permitted actions that you are willing to authorize. Continuing with the earlier example, this would mean that you need to add View Only permitted action Zoho products in one Progressive MCP server, and Full Access Zoho products in a different Progressive MCP server.
Progressive MCP Server vs Custom MCP Server
This section illuminates the differences between Progressive MCP and Custom MCP servers, and the use cases that suit each one.
Category | Progressive MCP Server | Custom MCP Server |
Setup overhead | Quite minimal, limited to selection of required Zoho products, and their associated tool bundles. | Significant manual effort required. You will need to manually add every single MCP tool required for your process. |
Knowledge overhead | Quite minimal. You can comfortably use it, if you're aware of the functionalities present in the configured products. | You are required to know the tools that have been exposed by your configured products. |
Tool match methodology | The AI client discovers progressively: it lists products, narrows down features, finds the relevant tools, fetches their schema, then executes them. | The AI client matches the extracted context directly against the tools already configured in the server. |
Context load | Utilizes significantly less context window compared to the conventional MCP tool calls. | Every tool that is configured in the server is loaded on every call, and then the AI proceeds to rundown the list of tools to match the required action. This consumes a lot of context and more often than not pushes the AI to hallucinate. |
Tool limits | Given that only the required tools are invoked, there are effectively no tool limits. | To ensure an AI Client has sufficient context window to complete the required action, there is a 300 MCP Tool limit. |
Best suited for | Broad, dynamic, or exploratory workflows where the required tools aren’t known in advance. | Well-defined, repeatable workflows where the exact tools are known. |
Example use cases for you to try
This section presents example use cases and the type of Zoho MCP server best suited to each requirement.
Example 1:
Prepare for a customer renewal call: pull the customer’s open deals from Zoho CRM, their recent support tickets from Zoho Desk, and their unpaid invoices from Zoho Books, then summarize the account’s health.
Example prompt: “I have a renewal call with Zylker tomorrow. Pull their open deals from Zoho CRM, their support tickets from the last 90 days in Zoho Desk, and any overdue invoices in Zoho Books, and give me a summary of the account.”
Recommended server: Progressive Zoho MCP server
Reason: The workflow spans three of the largest tool sets (1,324 CRM tools, 887 Desk tools, and 1,132 Books tools). The AI client discovers and loads only the few it needs, such as searchRecords, getRelatedRecords, getTicketsByContact, and list_invoices, instead of carrying all 3,343 upfront.
Example 2:
Triage an escalated support ticket: read the ticket and its conversation in Zoho Desk, check the customer’s deal value in Zoho CRM, and post a summary to your team’s escalation channel in Zoho Cliq.
Example prompt: “Look into the latest high-priority ticket in Zoho Desk, check how much that customer’s open deals are worth in Zoho CRM, and post a summary with a recommended next step to the #support-escalations channel in Zoho Cliq.”
Recommended server: Progressive Zoho MCP server
Reason: What the client needs to check depends on the ticket, the customer, and what the conversation reveals, making the required tools hard to predict. Progressive discovery lets the client pick tools like getTicket, getTicketConversations, searchRecords, and postMessageInChannelByChannelUniqueName as the task unfolds.
Example 3:
Follow up on overdue invoices every week: list overdue invoices in Zoho Books, send payment reminders to those customers, and post a summary to your finance channel in Zoho Cliq.
Example prompt: “Find all overdue invoices in Zoho Books, send each customer a payment reminder, and post a summary of who was reminded and the total amount outstanding to the #finance channel in Zoho Cliq.”
Recommended server: Custom Zoho MCP server
Reason: A fixed, repeatable workflow that needs only a handful of known tools, such as list_invoices, bulk_invoice_reminder, and postMessageInChannelByChannelUniqueName. Configuring exactly these keeps the server lean and the operation predictable every run.