Example Prompts

# Example Prompts

Once you've connected your Catalyst MCP server, you can test its functionality using the following prompts.

### Workflows using only Catalyst MCP Tools

The following prompts can be handled by your preferred MCP Client, if the connected MCP server is either the Catalyst Global MCP Server, or an On-Demand MCP Server configured with only Catalyst MCP Tools.

#### Build a Subscription-Based SaaS Application

I am building a subscription management platform. Enable authentication for the project and configure roles for Super Admin, Account Owner, and Member. Create API Gateway routes for subscription creation, renewal, cancellation, and usage tracking. Deploy the application as a web app and configure CORS domains for the client portal origin. Set up a job pool to manage concurrent subscription renewal jobs and create an immediate job handler for on-demand plan upgrades. Cache active subscription states in a dedicated segment to reduce authentication overhead on every request. Schedule a cron job to run at midnight on the first of every month to trigger renewal processing and store monthly billing summaries as versioned objects in a Stratus bucket called 'billing-archives'. Generate pre-signed URLs for each billing summary so account owners can securely download their invoices without platform authentication.

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

<table border="1" cellpadding="8" cellspacing="0">
  <thead>
    <tr>
      <th>Catalyst Component</th>
      <th>MCP Tool</th>
      <th>Purpose</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td rowspan="2">Authentication</td>
      <td>Enable_Authentication</td>
      <td>Enables user authentication on the project, securing all subscription endpoints before access is granted</td>
    </tr>
    <tr>
      <td>List_All_Roles</td>
      <td>Retrieves existing roles to verify and configure Super Admin, Account Owner, and Member access levels</td>
    </tr>
    <tr>
      <td rowspan="2">API Gateway</td>
      <td>Configure_API_Gateway_Route</td>
      <td>Creates the subscription creation, renewal, cancellation, and usage tracking API endpoints</td>
    </tr>
    <tr>
      <td>Create_CORS_Domain</td>
      <td>Registers the client portal origin to permit cross-origin API requests from the front-end</td>
    </tr>
    <tr>
      <td>Web Client Hosting</td>
      <td>List_All_Web_Apps</td>
      <td>Retrieves web app configurations to support deploying the client-facing subscription portal</td>
    </tr>
    <tr>
      <td>Job Pool</td>
      <td>Create_Job_Pool</td>
      <td>Creates a pool to manage concurrent subscription renewal job execution</td>
    </tr>
    <tr>
      <td>Jobs</td>
      <td>Create_Immediate_Job</td>
      <td>Triggers on-demand plan upgrade jobs instantly for real-time plan change requests</td>
    </tr>
    <tr>
      <td rowspan="2">Cache</td>
      <td>Create_Segment</td>
      <td>Creates a dedicated cache segment to hold active subscription state data</td>
    </tr>
    <tr>
      <td>Create_Cache_Item</td>
      <td>Stores individual subscription states in the segment to reduce authentication overhead per request</td>
    </tr>
    <tr>
      <td>Cron</td>
      <td>Create_Cron_Job</td>
      <td>Schedules the monthly midnight renewal processing job to run on the first of every month</td>
    </tr>
    <tr>
      <td rowspan="2">Stratus</td>
      <td>Create_Bucket</td>
      <td>Creates the billing-archives bucket to store versioned monthly billing summaries</td>
    </tr>
    <tr>
      <td>Generate_Signed_URL</td>
      <td>Generates pre-signed URLs for account owners to securely download their invoices without platform authentication</td>
    </tr>
  </tbody>
</table>

#### Build a B2B Sales Intelligence and Prospecting Engine

I am building a B2B sales prospecting platform on Catalyst. Use the Lead Enrichment tool to gather detailed company and contact data for a target list of accounts. Use Similar Companies to identify adjacent prospects in the same industry vertical and Tech Stack Finder to qualify each prospect based on their existing technology infrastructure. Store all enriched and qualified lead records in a datastore table called 'Prospect Pipeline' and configure a bulk write job to import any existing CRM exports into the same table. Set up a serverless circuit to orchestrate the full enrichment and qualification workflow end to end. Configure a job pool to manage concurrent enrichment jobs across large prospect batches and schedule a weekly cron job every Monday at 6:00 AM to refresh the pipeline with newly enriched data. Expose the prospect data via API Gateway routes so the front-end sales dashboard can consume ranked and filtered lead lists in real time. Cache the top 100 ranked prospects in a dedicated segment for instant dashboard load. Store all prospect export files in a Stratus bucket called 'sales-intelligence' and generate pre-signed URLs for the sales team to download their assigned prospect lists securely.

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

<table border="1" cellpadding="8" cellspacing="0">
  <thead>
    <tr>
      <th>Catalyst Component</th>
      <th>MCP Tool</th>
      <th>Purpose</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td rowspan="3">Dataverse</td>
      <td>Lead_Enrichment</td>
      <td>Gathers detailed company and contact data to enrich the target prospect records</td>
    </tr>
    <tr>
      <td>Similar_Companies</td>
      <td>Identifies adjacent prospects in the same industry vertical for pipeline expansion</td>
    </tr>
    <tr>
      <td>Tech_Stack_Finder</td>
      <td>Qualifies prospects based on their existing technology infrastructure</td>
    </tr>
    <tr>
      <td rowspan="2">Datastore</td>
      <td>Create_Table</td>
      <td>Creates the Prospect Pipeline table to store all enriched and qualified lead records</td>
    </tr>
    <tr>
      <td>Insert_Rows</td>
      <td>Inserts enriched lead records into the Prospect Pipeline table</td>
    </tr>
    <tr>
      <td>Jobs</td>
      <td>Create_Bulk_Write_Job</td>
      <td>Imports existing CRM exports into the Prospect Pipeline table via a bulk write operation</td>
    </tr>
    <tr>
      <td>Circuits</td>
      <td>Execute_Circuit</td>
      <td>Orchestrates the end-to-end enrichment and qualification workflow from lead intake to scoring</td>
    </tr>
    <tr>
      <td>Job Pool</td>
      <td>Create_Job_Pool</td>
      <td>Creates a pool to manage concurrent enrichment jobs across large prospect batches</td>
    </tr>
    <tr>
      <td>Cron</td>
      <td>Create_Cron_Job</td>
      <td>Schedules the weekly Monday 6:00 AM refresh job to pull in newly enriched pipeline data</td>
    </tr>
    <tr>
      <td>API Gateway</td>
      <td>Configure_API_Gateway_Route</td>
      <td>Exposes prospect data via API routes for the front-end sales dashboard to consume</td>
    </tr>
    <tr>
      <td rowspan="2">Cache</td>
      <td>Create_Segment</td>
      <td>Creates a dedicated cache segment to store the top-ranked prospect records</td>
    </tr>
    <tr>
      <td>Create_Cache_Item</td>
      <td>Caches the top 100 ranked prospects for instant dashboard load without datastore queries</td>
    </tr>
    <tr>
      <td rowspan="2">Stratus</td>
      <td>Create_Bucket</td>
      <td>Creates the sales-intelligence bucket to store prospect export files</td>
    </tr>
    <tr>
      <td>Generate_Signed_URL</td>
      <td>Generates pre-signed URLs for the sales team to securely download their assigned prospect lists</td>
    </tr>
  </tbody>
</table>

#### Build a Real-Time Logistics and Delivery Tracking Platform

I am building a logistics platform for tracking deliveries across multiple regions. Create API Gateway routes for order intake, driver assignment, status updates, and delivery confirmation mapped to their respective serverless functions. Execute each function via POST and PATCH methods for order creation and status transitions. Configure a job pool to manage concurrent dispatch jobs and create immediate jobs for urgent on-demand delivery assignments. Cache real-time delivery status data in a dedicated segment so the tracking dashboard can poll status without hitting the backend functions on every request. Set up a cron job to run every hour to reconcile undelivered orders and flag exceptions. Store all delivery confirmation documents and proof-of-delivery images in a Stratus bucket called 'delivery-records' with pre-signed URLs generated for customer access. Configure environment variables for all functions with region-specific API keys and routing service credentials. Retrieve application logs filtered by error level to proactively monitor failed delivery events.

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

<table border="1" cellpadding="8" cellspacing="0">
  <thead>
    <tr>
      <th>Catalyst Component</th>
      <th>MCP Tool</th>
      <th>Purpose</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>API Gateway</td>
      <td>Configure_API_Gateway_Route</td>
      <td>Creates endpoints for order intake, driver assignment, status updates, and delivery confirmation</td>
    </tr>
    <tr>
      <td rowspan="3">Serverless Functions</td>
      <td>Execute_Function_Via_POST</td>
      <td>Executes order creation and assignment functions via POST for new delivery submissions</td>
    </tr>
    <tr>
      <td>Execute_Function_Via_PATCH</td>
      <td>Executes status update functions via PATCH for incremental delivery status transitions</td>
    </tr>
    <tr>
      <td>Create_Env_Variables</td>
      <td>Sets region-specific API keys and routing service credentials as function environment variables</td>
    </tr>
    <tr>
      <td>Job Pool</td>
      <td>Create_Job_Pool</td>
      <td>Creates a pool to manage concurrent dispatch jobs across simultaneous delivery assignments</td>
    </tr>
    <tr>
      <td>Jobs</td>
      <td>Create_Immediate_Job</td>
      <td>Triggers urgent on-demand delivery assignment jobs instantly for priority dispatches</td>
    </tr>
    <tr>
      <td rowspan="2">Cache</td>
      <td>Create_Segment</td>
      <td>Creates a dedicated cache segment to hold real-time delivery status data</td>
    </tr>
    <tr>
      <td>Create_Cache_Item</td>
      <td>Caches per-order delivery status so the tracking dashboard polls without backend round-trips</td>
    </tr>
    <tr>
      <td>Cron</td>
      <td>Create_Cron_Job</td>
      <td>Schedules an hourly job to reconcile undelivered orders and surface delivery exceptions</td>
    </tr>
    <tr>
      <td rowspan="2">Stratus</td>
      <td>Create_Bucket</td>
      <td>Creates the delivery-records bucket to store confirmation documents and proof-of-delivery images</td>
    </tr>
    <tr>
      <td>Generate_Signed_URL</td>
      <td>Generates pre-signed URLs for customers to access delivery confirmation records securely</td>
    </tr>
    <tr>
      <td>Logs</td>
      <td>Get_Logs</td>
      <td>Retrieves logs filtered by error level to proactively detect and monitor failed delivery events</td>
    </tr>
  </tbody>
</table>

#### Build a Catalyst-Powered DevOps Automation Platform

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

<table border="1" cellpadding="8" cellspacing="0">
  <thead>
    <tr>
      <th>Catalyst Component</th>
      <th>MCP Tool</th>
      <th>Purpose</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td rowspan="3">Dataverse</td>
      <td>Lead_Enrichment</td>
      <td>Gathers detailed company and contact data to enrich the target prospect records</td>
    </tr>
    <tr>
      <td>Similar_Companies</td>
      <td>Identifies adjacent prospects in the same industry vertical for pipeline expansion</td>
    </tr>
    <tr>
      <td>Tech_Stack_Finder</td>
      <td>Qualifies prospects based on their existing technology infrastructure</td>
    </tr>
    <tr>
      <td rowspan="2">Datastore</td>
      <td>Create_Table</td>
      <td>Creates the Prospect Pipeline table to store all enriched and qualified lead records</td>
    </tr>
    <tr>
      <td>Insert_Rows</td>
      <td>Inserts enriched lead records into the Prospect Pipeline table</td>
    </tr>
    <tr>
      <td>Jobs</td>
      <td>Create_Bulk_Write_Job</td>
      <td>Imports existing CRM exports into the Prospect Pipeline table via a bulk write operation</td>
    </tr>
    <tr>
      <td>Circuits</td>
      <td>Execute_Circuit</td>
      <td>Orchestrates the end-to-end enrichment and qualification workflow from lead intake to scoring</td>
    </tr>
    <tr>
      <td>Job Pool</td>
      <td>Create_Job_Pool</td>
      <td>Creates a pool to manage concurrent enrichment jobs across large prospect batches</td>
    </tr>
    <tr>
      <td>Cron</td>
      <td>Create_Cron_Job</td>
      <td>Schedules the weekly Monday 6:00 AM refresh job to pull in newly enriched pipeline data</td>
    </tr>
    <tr>
      <td>API Gateway</td>
      <td>Configure_API_Gateway_Route</td>
      <td>Exposes prospect data via API routes for the front-end sales dashboard to consume</td>
    </tr>
    <tr>
      <td rowspan="2">Cache</td>
      <td>Create_Segment</td>
      <td>Creates a dedicated cache segment to store the top-ranked prospect records</td>
    </tr>
    <tr>
      <td>Create_Cache_Item</td>
      <td>Caches the top 100 ranked prospects for instant dashboard load without datastore queries</td>
    </tr>
    <tr>
      <td rowspan="2">Stratus</td>
      <td>Create_Bucket</td>
      <td>Creates the sales-intelligence bucket to store prospect export files</td>
    </tr>
    <tr>
      <td>Generate_Signed_URL</td>
      <td>Generates pre-signed URLs for the sales team to securely download their assigned prospect lists</td>
    </tr>
  </tbody>
</table>

#### Build an AI-Powered Content Publishing Platform

I am building a content publishing platform where writers submit articles, editors review them, and publishers approve and schedule them for release. Enable authentication and configure roles for Writer, Editor, and Publisher with appropriate table permissions and scopes for each role. Create API Gateway routes for content submission, review, approval, and scheduling. Configure serverless circuits to orchestrate the end-to-end editorial workflow from submission through to publication. Set up a cron job to automatically publish approved articles at their scheduled time and another to send digest notifications every Friday at 9:00 AM. Store all media assets including images, videos, and attachments in a Stratus bucket called 'content-assets' with pre-signed upload signatures for direct writer uploads. Cache the most recently published articles in a dedicated segment to accelerate front-end load times. Deploy the platform as a web app and configure CORS domains for the editorial dashboard and the public-facing reader portal separately.

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

<table border="1" cellpadding="8" cellspacing="0">
  <thead>
    <tr>
      <th>Catalyst Component</th>
      <th>MCP Tool</th>
      <th>Purpose</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td rowspan="2">Authentication</td>
      <td>Enable_Authentication</td>
      <td>Enables user authentication to secure the content platform across all editorial roles</td>
    </tr>
    <tr>
      <td>List_All_Roles</td>
      <td>Retrieves existing roles to configure Writer, Editor, and Publisher access levels</td>
    </tr>
    <tr>
      <td rowspan="2">API Gateway</td>
      <td>Configure_API_Gateway_Route</td>
      <td>Creates endpoints for content submission, review, approval, and scheduling</td>
    </tr>
    <tr>
      <td>Create_CORS_Domain</td>
      <td>Registers the editorial dashboard and public reader portal as separate allowed CORS origins</td>
    </tr>
    <tr>
      <td>Circuits</td>
      <td>Execute_Circuit</td>
      <td>Orchestrates the end-to-end editorial workflow from submission through to publication</td>
    </tr>
    <tr>
      <td>Cron</td>
      <td>Create_Cron_Job</td>
      <td>Schedules automated article publication at release times and weekly digest notifications every Friday</td>
    </tr>
    <tr>
      <td rowspan="2">Stratus</td>
      <td>Create_Bucket</td>
      <td>Creates the content-assets bucket to store media files including images, videos, and attachments</td>
    </tr>
    <tr>
      <td>Create_Upload_Signature</td>
      <td>Generates pre-signed upload signatures for writers to upload media assets directly from the browser</td>
    </tr>
    <tr>
      <td rowspan="2">Cache</td>
      <td>Create_Segment</td>
      <td>Creates a dedicated cache segment to hold recently published article data</td>
    </tr>
    <tr>
      <td>Create_Cache_Item</td>
      <td>Caches the most recently published articles to accelerate front-end load times</td>
    </tr>
    <tr>
      <td>Web Client Hosting</td>
      <td>List_All_Web_Apps</td>
      <td>Retrieves web app configurations to support deploying the content platform</td>
    </tr>
  </tbody>
</table>

#### Build a Multi-Region Event Management Platform

I am building an event management platform that handles registrations, ticketing, and post-event reporting across multiple regions. Create API Gateway routes for event creation, attendee registration, ticket generation, and cancellation mapped to serverless functions executed via GET, POST, PUT, and DELETE methods. Enable authentication and configure roles for Event Organizer, Attendee, and Platform Admin. Set up a job pool to manage high-concurrency ticket processing during peak registration windows and configure immediate jobs for on-demand ticket reissuance. Store all event assets including banners, schedules, and speaker profiles in a Stratus bucket called 'event-assets' and generate pre-signed URLs for secure attendee access to event materials. Cache event capacity and availability data in a dedicated segment to prevent overselling under high load. Schedule a cron job to run one hour before each event to send automated reminders and another post-event to trigger a bulk read job exporting attendee data for reporting. Store all exported reports as versioned objects in a Stratus bucket called 'event-reports'.

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

<table border="1" cellpadding="8" cellspacing="0">
  <thead>
    <tr>
      <th>Catalyst Component</th>
      <th>MCP Tool</th>
      <th>Purpose</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>API Gateway</td>
      <td>Configure_API_Gateway_Route</td>
      <td>Creates endpoints for event creation, attendee registration, ticket generation, and cancellation</td>
    </tr>
    <tr>
      <td rowspan="4">Serverless Functions</td>
      <td>Execute_Function_Via_GET</td>
      <td>Executes event and ticket retrieval functions via GET requests</td>
    </tr>
    <tr>
      <td>Execute_Function_Via_POST</td>
      <td>Executes event creation and attendee registration functions via POST requests</td>
    </tr>
    <tr>
      <td>Execute_Function_Via_PUT</td>
      <td>Executes event update functions via PUT requests</td>
    </tr>
    <tr>
      <td>Execute_Function_Via_DELETE</td>
      <td>Executes cancellation and cleanup functions via DELETE requests</td>
    </tr>
    <tr>
      <td rowspan="2">Authentication</td>
      <td>Enable_Authentication</td>
      <td>Enables user authentication to secure event creation, ticketing, and registration operations</td>
    </tr>
    <tr>
      <td>List_All_Roles</td>
      <td>Retrieves and configures roles for Event Organizer, Attendee, and Platform Admin</td>
    </tr>
    <tr>
      <td>Job Pool</td>
      <td>Create_Job_Pool</td>
      <td>Creates a pool to manage high-concurrency ticket processing during peak registration windows</td>
    </tr>
    <tr>
      <td rowspan="2">Jobs</td>
      <td>Create_Immediate_Job</td>
      <td>Triggers on-demand ticket reissuance jobs instantly when requested</td>
    </tr>
    <tr>
      <td>Create_Bulk_Read_Job</td>
      <td>Creates a bulk read job to export attendee data for post-event reporting</td>
    </tr>
    <tr>
      <td rowspan="2">Cache</td>
      <td>Create_Segment</td>
      <td>Creates a dedicated cache segment to store event capacity and availability data</td>
    </tr>
    <tr>
      <td>Create_Cache_Item</td>
      <td>Caches event capacity state to prevent overselling under high registration load</td>
    </tr>
    <tr>
      <td>Cron</td>
      <td>Create_Cron_Job</td>
      <td>Schedules pre-event automated reminder dispatch and post-event attendee data export trigger</td>
    </tr>
    <tr>
      <td rowspan="2">Stratus</td>
      <td>Create_Bucket</td>
      <td>Creates the event-assets and event-reports buckets for event materials and exported attendee data</td>
    </tr>
    <tr>
      <td>Generate_Signed_URL</td>
      <td>Generates pre-signed URLs for attendees to securely access event materials</td>
    </tr>
  </tbody>
</table>

#### Build a Catalyst AppSail-Powered Microservices Platform

I am building a microservices platform on Catalyst using AppSail to host independent services for authentication, payments, notifications, and analytics. Retrieve all existing AppSail configurations and map each service to its corresponding API Gateway route. Configure environment variables per service deployment with the required runtime credentials and service-to-service communication keys. Set up serverless circuits to orchestrate cross-service workflows such as payment confirmation triggering notification dispatch and analytics event logging. Configure a job pool to manage concurrent background processing jobs across all microservices and schedule cron jobs for each service's maintenance window payments reconciliation at 2:00 AM, analytics aggregation at 3:00 AM, and notification queue flush at 4:00 AM. Cache inter-service authentication tokens in a dedicated segment to eliminate redundant token generation on every service call. Store all service-level audit logs in a Stratus bucket called 'microservices-audit' and configure CORS domains for each service's permitted front-end origin. Enable authentication at the platform level and configure roles scoped to each microservice domain.

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

<table border="1" cellpadding="8" cellspacing="0">
  <thead>
    <tr>
      <th>Catalyst Component</th>
      <th>MCP Tool</th>
      <th>Purpose</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td rowspan="3">AppSail</td>
      <td>List_All_AppSail</td>
      <td>Retrieves all existing AppSail service configurations for mapping to API routes</td>
    </tr>
    <tr>
      <td>Get_AppSail</td>
      <td>Retrieves detailed configuration for each individual AppSail service</td>
    </tr>
    <tr>
      <td>Create_Env_Variables</td>
      <td>Sets runtime credentials and service-to-service communication keys per service deployment</td>
    </tr>
    <tr>
      <td rowspan="2">API Gateway</td>
      <td>Configure_API_Gateway_Route</td>
      <td>Maps each microservice to its corresponding API Gateway route</td>
    </tr>
    <tr>
      <td>Create_CORS_Domain</td>
      <td>Registers each service's permitted front-end origin as a separate CORS domain</td>
    </tr>
    <tr>
      <td>Circuits</td>
      <td>Execute_Circuit</td>
      <td>Orchestrates cross-service workflows such as payment confirmation triggering notifications and analytics logging</td>
    </tr>
    <tr>
      <td>Job Pool</td>
      <td>Create_Job_Pool</td>
      <td>Creates a pool to manage concurrent background processing jobs across all microservices</td>
    </tr>
    <tr>
      <td>Cron</td>
      <td>Create_Cron_Job</td>
      <td>Schedules maintenance window jobs for payments reconciliation, analytics aggregation, and notification queue flush</td>
    </tr>
    <tr>
      <td rowspan="2">Cache</td>
      <td>Create_Segment</td>
      <td>Creates a dedicated cache segment to store inter-service authentication tokens</td>
    </tr>
    <tr>
      <td>Create_Cache_Item</td>
      <td>Caches authentication tokens to eliminate redundant token generation on every service call</td>
    </tr>
    <tr>
      <td>Stratus</td>
      <td>Create_Bucket</td>
      <td>Creates the microservices-audit bucket to store service-level audit logs</td>
    </tr>
    <tr>
      <td rowspan="2">Authentication</td>
      <td>Enable_Authentication</td>
      <td>Enables platform-level authentication to secure all microservice interactions</td>
    </tr>
    <tr>
      <td>List_All_Roles</td>
      <td>Retrieves and configures roles scoped to each microservice domain</td>
    </tr>
  </tbody>
</table>

#### Build a Healthcare Appointment and Records Management System

I am building a healthcare platform for managing patient appointments, medical records, and physician workflows. Enable authentication for the project and configure roles for Patient, Physician, Nurse, and Admin with granular table permissions and scopes ensuring patients can only access their own records. Create API Gateway routes for appointment booking, cancellation, rescheduling, and medical record retrieval mapped to serverless functions. Execute functions via GET for record retrieval and POST and PATCH for appointment management. Configure a serverless circuit to orchestrate the appointment confirmation workflow including availability checks, booking confirmation, and notification dispatch. Set up a cron job to run every morning at 7:00 AM to generate the day's appointment schedule and another at 10:00 PM to archive completed appointment records. Store all patient documents, lab reports, and prescriptions in a Stratus bucket called 'patient-records' with pre-signed URLs generated per patient for secure time-limited document access. Cache physician availability slots in a dedicated segment to accelerate the booking experience. Configure environment variables for all functions with HIPAA-compliant service credentials and encryption keys.

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

<table border="1" cellpadding="8" cellspacing="0">
  <thead>
    <tr>
      <th>Catalyst Component</th>
      <th>MCP Tool</th>
      <th>Purpose</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td rowspan="2">Authentication</td>
      <td>Enable_Authentication</td>
      <td>Enables user authentication for the healthcare platform, securing all patient and physician data</td>
    </tr>
    <tr>
      <td>List_All_Roles</td>
      <td>Configures Patient, Physician, Nurse, and Admin roles with appropriate access levels</td>
    </tr>
    <tr>
      <td rowspan="2">Datastore</td>
      <td>Update_Table_Permissions</td>
      <td>Sets granular table permissions so patients can only read and write their own records</td>
    </tr>
    <tr>
      <td>Update_Table_Scopes</td>
      <td>Configures table scope to enforce per-user data isolation across patient records</td>
    </tr>
    <tr>
      <td>API Gateway</td>
      <td>Configure_API_Gateway_Route</td>
      <td>Creates endpoints for appointment booking, cancellation, rescheduling, and medical record retrieval</td>
    </tr>
    <tr>
      <td rowspan="4">Serverless Functions</td>
      <td>Execute_Function_Via_GET</td>
      <td>Executes medical record and schedule retrieval functions via GET requests</td>
    </tr>
    <tr>
      <td>Execute_Function_Via_POST</td>
      <td>Executes appointment booking functions via POST requests</td>
    </tr>
    <tr>
      <td>Execute_Function_Via_PATCH</td>
      <td>Executes appointment rescheduling functions via PATCH for partial updates</td>
    </tr>
    <tr>
      <td>Create_Env_Variables</td>
      <td>Configures HIPAA-compliant service credentials and encryption keys as function environment variables</td>
    </tr>
    <tr>
      <td>Circuits</td>
      <td>Execute_Circuit</td>
      <td>Orchestrates the appointment confirmation workflow including availability checks and notification dispatch</td>
    </tr>
    <tr>
      <td>Cron</td>
      <td>Create_Cron_Job</td>
      <td>Schedules the 7:00 AM daily schedule generation job and the 10:00 PM completed appointment archival job</td>
    </tr>
    <tr>
      <td rowspan="2">Stratus</td>
      <td>Create_Bucket</td>
      <td>Creates the patient-records bucket to store documents, lab reports, and prescriptions</td>
    </tr>
    <tr>
      <td>Generate_Signed_URL</td>
      <td>Generates per-patient time-limited pre-signed URLs for secure document access</td>
    </tr>
    <tr>
      <td rowspan="2">Cache</td>
      <td>Create_Segment</td>
      <td>Creates a dedicated cache segment to store physician availability slots</td>
    </tr>
    <tr>
      <td>Create_Cache_Item</td>
      <td>Caches physician availability slots to accelerate the appointment booking experience</td>
    </tr>
  </tbody>
</table>

#### Build a Catalyst-Powered IoT Data Ingestion and Monitoring Platform

I am building an IoT platform on Catalyst to ingest, process, and monitor sensor data from thousands of connected devices across multiple facilities. Configure API Gateway routes for device registration, data ingestion, threshold alerts, and device status updates mapped to serverless functions executed via POST for ingestion and GET for status retrieval. Set up a job pool to manage high-concurrency data ingestion jobs from simultaneous device streams and configure immediate jobs for on-demand device diagnostics triggered by field engineers. Create a serverless circuit to orchestrate the alert workflow evaluating incoming sensor readings against defined thresholds, triggering alerts for breaches, and logging events. Schedule a cron job to run every 15 minutes to aggregate device telemetry and another at midnight to archive the day's sensor data via a bulk read job. Store all archived telemetry data and device configuration files in a Stratus bucket called 'iot-telemetry' as versioned objects. Cache the latest sensor readings per device in a dedicated segment so the monitoring dashboard reflects near real-time device status without querying the datastore on every poll. Retrieve application logs filtered by error level to detect device connectivity failures and configure environment variables for all ingestion functions with facility-specific device authentication credentials.

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

<table border="1" cellpadding="8" cellspacing="0">
  <thead>
    <tr>
      <th>Catalyst Component</th>
      <th>MCP Tool</th>
      <th>Purpose</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>API Gateway</td>
      <td>Configure_API_Gateway_Route</td>
      <td>Creates endpoints for device registration, data ingestion, threshold alerts, and device status updates</td>
    </tr>
    <tr>
      <td rowspan="3">Serverless Functions</td>
      <td>Execute_Function_Via_POST</td>
      <td>Executes data ingestion functions via POST for incoming sensor data streams</td>
    </tr>
    <tr>
      <td>Execute_Function_Via_GET</td>
      <td>Executes device status retrieval functions via GET requests</td>
    </tr>
    <tr>
      <td>Create_Env_Variables</td>
      <td>Configures facility-specific device authentication credentials as function environment variables</td>
    </tr>
    <tr>
      <td>Job Pool</td>
      <td>Create_Job_Pool</td>
      <td>Creates a pool to manage high-concurrency data ingestion jobs from simultaneous device streams</td>
    </tr>
    <tr>
      <td rowspan="2">Jobs</td>
      <td>Create_Immediate_Job</td>
      <td>Triggers on-demand device diagnostic jobs instantly for field engineer requests</td>
    </tr>
    <tr>
      <td>Create_Bulk_Read_Job</td>
      <td>Creates a bulk read job to export the day's sensor data for archival at midnight</td>
    </tr>
    <tr>
      <td>Circuits</td>
      <td>Execute_Circuit</td>
      <td>Orchestrates the alert workflow evaluating sensor readings against thresholds and triggering breach notifications</td>
    </tr>
    <tr>
      <td>Cron</td>
      <td>Create_Cron_Job</td>
      <td>Schedules the 15-minute telemetry aggregation job and the midnight sensor data archival job</td>
    </tr>
    <tr>
      <td>Stratus</td>
      <td>Create_Bucket</td>
      <td>Creates the iot-telemetry bucket to store versioned archived telemetry and device configuration files</td>
    </tr>
    <tr>
      <td rowspan="2">Cache</td>
      <td>Create_Segment</td>
      <td>Creates a dedicated cache segment to store the latest sensor readings per device</td>
    </tr>
    <tr>
      <td>Create_Cache_Item</td>
      <td>Caches the most recent sensor reading per device for near real-time dashboard display</td>
    </tr>
    <tr>
      <td>Logs</td>
      <td>Get_Logs</td>
      <td>Retrieves logs filtered by error level to detect device connectivity failures</td>
    </tr>
  </tbody>
</table>

### Catalyst MCP Tools in Multi-Service Zoho Workflows

You can execute these prompts using:

* **2 Zoho MCP Servers**: Catalyst Global MCP Server and an On-Demand Zoho MCP Server configured with the required MCP Tools of other Zoho services.

* An On-Demand Zoho MCP Server, configured to contain MCP tools from multiple Zoho Services, including Catalyst by Zoho.

#### Build an Automated Customer Support Intelligence Platform

I am building a customer support intelligence platform that connects helpdesk operations with CRM data and analytics. Pull all open and overdue tickets from the helpdesk and enrich each ticket's associated contact with additional company and lead data using Catalyst Dataverse. Cross-reference the enriched contact records against CRM leads and accounts to identify high-value customers experiencing support issues and escalate their tickets with priority tags. Create a Catalyst serverless circuit to orchestrate the full triage workflow receiving new ticket webhooks, enriching the contact, evaluating priority, and triggering an automatic reassignment to the most suitable agent based on department. Store all enriched ticket and contact data in a Catalyst datastore table called 'Support Intelligence' and schedule a cron job every morning at 7:00 AM to generate a daily support health report. Export the report as a bulk read job, store it in a Stratus bucket called 'support-reports', and push a summary into a Zoho Analytics dashboard with a chart report breaking down ticket volume by priority, department, and resolution time.

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

<table border="1" cellpadding="8" cellspacing="0">
  <thead>
    <tr>
      <th>Zoho Service</th>
      <th>MCP Tool</th>
      <th>Purpose</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td rowspan="6">Catalyst by Zoho</td>
      <td>Create_Table</td>
      <td>Creates the Support Intelligence datastore table to store enriched ticket and contact records</td>
    </tr>
    <tr>
      <td>Insert_Rows</td>
      <td>Inserts enriched ticket and contact data into the Support Intelligence table</td>
    </tr>
    <tr>
      <td>Execute_Circuit</td>
      <td>Orchestrates the full triage workflow from ticket webhook receipt through enrichment, priority evaluation, and agent reassignment</td>
    </tr>
    <tr>
      <td>Create_Cron_Job</td>
      <td>Schedules the daily 7:00 AM job to generate and export the support health report</td>
    </tr>
    <tr>
      <td>Create_Bulk_Read_Job</td>
      <td>Exports the daily report data from the datastore for storage in the support-reports Stratus bucket</td>
    </tr>
    <tr>
      <td>Create_Immediate_Job</td>
      <td>Triggers on-demand triage and enrichment for newly received ticket webhooks outside the scheduled run</td>
    </tr>
    <tr>
      <td rowspan="5">Zoho Desk</td>
      <td>getTickets</td>
      <td>Pulls all open and overdue tickets from the helpdesk for triage and enrichment</td>
    </tr>
    <tr>
      <td>searchTickets</td>
      <td>Searches tickets to filter overdue and high-priority cases requiring escalation</td>
    </tr>
    <tr>
      <td>getContact</td>
      <td>Retrieves the contact details associated with each ticket for Dataverse enrichment</td>
    </tr>
    <tr>
      <td>updateTicket</td>
      <td>Updates ticket priority tags to escalate issues from identified high-value customers</td>
    </tr>
    <tr>
      <td>getAgents</td>
      <td>Retrieves available agents by department for automatic ticket reassignment</td>
    </tr>
    <tr>
      <td rowspan="3">Zoho CRM</td>
      <td>getLeadsRecords</td>
      <td>Cross-references enriched contacts against CRM lead records to identify high-value prospects with active support issues</td>
    </tr>
    <tr>
      <td>getAccountsRecord</td>
      <td>Retrieves CRM account data to flag high-value customers experiencing recurring support problems</td>
    </tr>
    <tr>
      <td>Lead_Enrichment</td>
      <td>Enriches ticket contact records with additional company and lead intelligence from Catalyst Dataverse</td>
    </tr>
    <tr>
      <td rowspan="4">Zoho Analytics</td>
      <td>import_data</td>
      <td>Pushes enriched ticket and contact data into the Zoho Analytics workspace</td>
    </tr>
    <tr>
      <td>query_data</td>
      <td>Queries aggregated support data to compile the daily health report</td>
    </tr>
    <tr>
      <td>create_chart_report</td>
      <td>Creates a chart breaking down ticket volume by priority, department, and resolution time</td>
    </tr>
    <tr>
      <td>create_summary_report</td>
      <td>Creates a summary report for the daily support health dashboard</td>
    </tr>
  </tbody>
</table>

#### Launch a Full Product Lifecycle Management Platform

I am building a product lifecycle management platform that tracks products from initial sales estimate through to delivery and invoicing. When a new sales order is approved in Zoho Books, trigger a Catalyst serverless circuit to initiate the fulfillment workflow — create a delivery challan, assign the responsible team member, and update the project task status in the associated project. Configure API Gateway routes for order status, fulfillment tracking, and invoice generation. Set up a recurring invoice profile for subscription-based product orders and enable auto-bill against the customer's stored payment method. Schedule a cron job every Monday at 8:00 AM to generate a weekly sales summary using a bulk read job and store the export in a Stratus bucket called 'sales-exports'. Push all order, invoice, and delivery data into a Zoho Analytics workspace with a pivot report showing revenue by product category and customer, and a summary report tracking order-to-delivery cycle times. Set up a webhook in Zoho Books to notify the Catalyst circuit whenever an invoice is approved or overdue, triggering automated payment reminder emails to the customer.

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

<table border="1" cellpadding="8" cellspacing="0">
  <thead>
    <tr>
      <th>Zoho Service</th>
      <th>MCP Tool</th>
      <th>Purpose</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td rowspan="5">Catalyst by Zoho</td>
      <td>Execute_Circuit</td>
      <td>Triggers the fulfillment workflow when a Books sales order is approved, orchestrating delivery challan creation, team assignment, and project task updates</td>
    </tr>
    <tr>
      <td>Configure_API_Gateway_Route</td>
      <td>Creates API endpoints for order status, fulfillment tracking, and invoice generation</td>
    </tr>
    <tr>
      <td>Create_Cron_Job</td>
      <td>Schedules the weekly Monday 8:00 AM sales summary generation job</td>
    </tr>
    <tr>
      <td>Create_Bulk_Read_Job</td>
      <td>Generates the weekly sales summary by exporting order data from the datastore for storage in the sales-exports bucket</td>
    </tr>
    <tr>
      <td>Create_Serverless_Function</td>
      <td>Creates the webhook handler function that receives and processes Zoho Books invoice approval and overdue events</td>
    </tr>
    <tr>
      <td rowspan="7">Zoho Books</td>
      <td>create_sales_order</td>
      <td>Creates a sales order when a new product order is initiated in the platform</td>
    </tr>
    <tr>
      <td>create_invoice</td>
      <td>Generates invoices for completed and approved product orders</td>
    </tr>
    <tr>
      <td>create_delivery_challan</td>
      <td>Creates a delivery challan when the Catalyst circuit triggers fulfillment for an approved order</td>
    </tr>
    <tr>
      <td>create_recurring_invoice</td>
      <td>Sets up a recurring invoice profile for subscription-based product orders</td>
    </tr>
    <tr>
      <td>enable_recurring_invoice_autobill</td>
      <td>Enables automatic billing against the customer's stored payment method for recurring subscriptions</td>
    </tr>
    <tr>
      <td>create_webhook</td>
      <td>Sets up a Zoho Books webhook to notify the Catalyst circuit when invoices are approved or become overdue</td>
    </tr>
    <tr>
      <td>bulk_invoice_reminder</td>
      <td>Sends automated payment reminder emails to customers with overdue invoices</td>
    </tr>
    <tr>
      <td rowspan="4">Zoho Analytics</td>
      <td>import_data</td>
      <td>Pushes order, invoice, and delivery data into the Zoho Analytics workspace</td>
    </tr>
    <tr>
      <td>create_pivot_report</td>
      <td>Creates a pivot report showing revenue broken down by product category and customer</td>
    </tr>
    <tr>
      <td>create_summary_report</td>
      <td>Creates a summary report tracking order-to-delivery cycle times</td>
    </tr>
    <tr>
      <td>create_chart_report</td>
      <td>Creates a chart report for visual revenue trend analysis across the product portfolio</td>
    </tr>
  </tbody>
</table>

#### Build a Unified B2B Revenue Operations Platform

I am building a revenue operations platform that unifies sales intelligence, CRM pipeline management, financial reporting, and meeting productivity. Use Catalyst Lead Enrichment and Similar Companies to identify and qualify new prospects and push enriched lead records directly into Zoho CRM as new lead records with assigned owners. Configure a CRM workflow rule that triggers when a lead reaches the qualified stage automatically creating a sales estimate in Zoho Books and scheduling a Zoho Meeting with the assigned sales rep and the prospect. After each meeting, retrieve the participant report and store attendance and engagement data in a Catalyst datastore table called 'Meeting Intelligence'. Configure a Catalyst cron job every Friday at 5:00 PM to generate a weekly pipeline report. Also, open deals from CRM, outstanding estimates from Zoho Books, and meeting engagement data from the datastore — then push the consolidated report into a Zoho Analytics dashboard with a chart report showing pipeline value by stage and a summary report tracking estimate-to-deal conversion rates.

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

<table border="1" cellpadding="8" cellspacing="0">
  <thead>
    <tr>
      <th>Zoho Service</th>
      <th>MCP Tool</th>
      <th>Purpose</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td rowspan="6">Catalyst by Zoho</td>
      <td>Lead_Enrichment</td>
      <td>Enriches prospect records with detailed company and contact intelligence for qualification</td>
    </tr>
    <tr>
      <td>Similar_Companies</td>
      <td>Identifies new prospects similar to existing high-value accounts for pipeline expansion</td>
    </tr>
    <tr>
      <td>Tech_Stack_Finder</td>
      <td>Qualifies prospects based on their existing technology infrastructure before CRM entry</td>
    </tr>
    <tr>
      <td>Create_Cron_Job</td>
      <td>Schedules the weekly Friday 5:00 PM pipeline report generation job</td>
    </tr>
    <tr>
      <td>Create_Table</td>
      <td>Creates the Meeting Intelligence table to store post-meeting attendance and engagement data</td>
    </tr>
    <tr>
      <td>Insert_Rows</td>
      <td>Stores participant report and meeting engagement data in the Meeting Intelligence table</td>
    </tr>
    <tr>
      <td rowspan="4">Zoho CRM</td>
      <td>createLeadsRecords</td>
      <td>Pushes enriched prospect records into Zoho CRM as new lead entries with assigned owners</td>
    </tr>
    <tr>
      <td>postWorkflowRule</td>
      <td>Configures the CRM workflow rule that triggers when a lead reaches the qualified stage to initiate the estimate and meeting flow</td>
    </tr>
    <tr>
      <td>getDealsRecords</td>
      <td>Retrieves open deal data from CRM for the weekly pipeline report consolidation</td>
    </tr>
    <tr>
      <td>updateLeadsRecord</td>
      <td>Updates lead records with qualification status and owner assignments after enrichment</td>
    </tr>
    <tr>
      <td rowspan="3">Zoho Books</td>
      <td>create_estimate</td>
      <td>Creates a sales estimate in Zoho Books when a CRM lead reaches the qualified stage</td>
    </tr>
    <tr>
      <td>email_estimate</td>
      <td>Sends the estimate to the prospect for review immediately after creation</td>
    </tr>
    <tr>
      <td>approve_estimate</td>
      <td>Marks estimates as approved for tracking in the estimate-to-deal conversion pipeline</td>
    </tr>
    <tr>
      <td rowspan="3">Zoho Meeting</td>
      <td>createMeetingSession</td>
      <td>Schedules a Zoho Meeting between the assigned sales rep and the qualified prospect</td>
    </tr>
    <tr>
      <td>getParticipantReport</td>
      <td>Retrieves post-meeting attendance and engagement data for storage in the Meeting Intelligence table</td>
    </tr>
    <tr>
      <td>getMeetingDetails</td>
      <td>Retrieves full meeting metadata to store alongside engagement records in the Meeting Intelligence table</td>
    </tr>
    <tr>
      <td rowspan="4">Zoho Analytics</td>
      <td>import_data</td>
      <td>Pushes consolidated pipeline, estimate, and meeting engagement data into the Analytics workspace</td>
    </tr>
    <tr>
      <td>query_data</td>
      <td>Queries CRM deals, Books estimates, and Meeting Intelligence data for the weekly pipeline report</td>
    </tr>
    <tr>
      <td>create_chart_report</td>
      <td>Creates a pipeline value by stage chart report for the weekly revenue summary</td>
    </tr>
    <tr>
      <td>create_summary_report</td>
      <td>Creates an estimate-to-deal conversion rate summary report for the dashboard</td>
    </tr>
  </tbody>
</table>

#### Build a Multi-Channel Customer Engagement and Retention Platform

I am building a customer engagement platform that monitors customer health across support, CRM, calendar, and analytics touchpoints. Pull all contacts from Zoho Desk that have more than three unresolved tickets in the past 30 days and cross-reference them against CRM accounts to identify at-risk customers. For each identified at-risk account, trigger a Catalyst serverless circuit that creates a CRM task for the account owner, schedules a follow-up meeting via Zoho Calendar, and generates a personalised retention estimate in Zoho Books with a special pricing offer applied from a custom pricebook. Store all at-risk account data and engagement actions in a Catalyst cache segment for fast retrieval by the account management dashboard. Configure a Catalyst cron job every Sunday at 6:00 AM to refresh the at-risk account list and a job pool to manage concurrent engagement workflows across large account volumes. Push all customer health metrics ticket volume, deal stage, meeting history, and estimate status into a Zoho Analytics workspace with a summary report tracking engagement actions per account owner and a chart report visualising at-risk account distribution by industry and revenue band.

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

<table border="1" cellpadding="8" cellspacing="0">
  <thead>
    <tr>
      <th>Zoho Service</th>
      <th>MCP Tool</th>
      <th>Purpose</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td rowspan="5">Catalyst by Zoho</td>
      <td>Execute_Circuit</td>
      <td>Orchestrates the engagement workflow per at-risk account, triggering CRM task creation, meeting scheduling, and retention estimate generation</td>
    </tr>
    <tr>
      <td>Create_Cache_Item</td>
      <td>Stores at-risk account data and engagement action states in a cache segment for fast retrieval by the account management dashboard</td>
    </tr>
    <tr>
      <td>Create_Job_Pool</td>
      <td>Manages concurrent engagement workflows across large at-risk account volumes</td>
    </tr>
    <tr>
      <td>Create_Cron_Job</td>
      <td>Schedules the Sunday 6:00 AM refresh of the at-risk account list</td>
    </tr>
    <tr>
      <td>Create_Immediate_Job</td>
      <td>Triggers the engagement workflow immediately for newly identified at-risk accounts outside the scheduled refresh</td>
    </tr>
    <tr>
      <td rowspan="4">Zoho Desk</td>
      <td>getTickets</td>
      <td>Pulls open tickets to identify contacts with more than three unresolved tickets in the past 30 days</td>
    </tr>
    <tr>
      <td>searchTickets</td>
      <td>Searches for unresolved tickets from the past 30 days to build the at-risk contact list</td>
    </tr>
    <tr>
      <td>getContact</td>
      <td>Retrieves contact details for ticket owners to cross-reference against CRM accounts</td>
    </tr>
    <tr>
      <td>getContactStatistics</td>
      <td>Gets ticket statistics per contact to identify those exceeding the three-ticket threshold in the 30-day window</td>
    </tr>
    <tr>
      <td rowspan="3">Zoho CRM</td>
      <td>getAccountsRecord</td>
      <td>Retrieves CRM account records to match against identified at-risk contacts and confirm account value</td>
    </tr>
    <tr>
      <td>updateDealsRecord</td>
      <td>Updates deal records for at-risk accounts to flag escalation status for the account owner</td>
    </tr>
    <tr>
      <td>createWorkflowTasks</td>
      <td>Creates a CRM follow-up task for the account owner for each identified at-risk account</td>
    </tr>
    <tr>
      <td rowspan="3">Zoho Books</td>
      <td>create_pricebook</td>
      <td>Creates the custom pricebook containing special retention pricing offers for at-risk accounts</td>
    </tr>
    <tr>
      <td>create_estimate</td>
      <td>Generates a personalised retention estimate with the special pricing offer for each at-risk account</td>
    </tr>
    <tr>
      <td>apply_pricebook_to_invoice</td>
      <td>Applies the retention pricebook pricing to the generated estimate for the at-risk customer</td>
    </tr>
    <tr>
      <td rowspan="3">Zoho Analytics</td>
      <td>import_data</td>
      <td>Pushes customer health metrics including ticket volume, deal stage, meeting history, and estimate status into the Analytics workspace</td>
    </tr>
    <tr>
      <td>create_summary_report</td>
      <td>Creates a report tracking engagement actions taken per account owner across the at-risk portfolio</td>
    </tr>
    <tr>
      <td>create_chart_report</td>
      <td>Creates a chart visualising at-risk account distribution by industry and revenue band</td>
    </tr>
  </tbody>
</table>

Once you’ve connected your Catalyst MCP server, you can test its functionality using the following prompts.

Workflows using only Catalyst MCP Tools

Build a Subscription-Based SaaS Application

Prompt

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

Catalyst Component	MCP Tool	Purpose
Authentication	Enable_Authentication	Enables user authentication on the project, securing all subscription endpoints before access is granted
Authentication	List_All_Roles	Retrieves existing roles to verify and configure Super Admin, Account Owner, and Member access levels
API Gateway	Configure_API_Gateway_Route	Creates the subscription creation, renewal, cancellation, and usage tracking API endpoints
API Gateway	Create_CORS_Domain	Registers the client portal origin to permit cross-origin API requests from the front-end
Web Client Hosting	List_All_Web_Apps	Retrieves web app configurations to support deploying the client-facing subscription portal
Job Pool	Create_Job_Pool	Creates a pool to manage concurrent subscription renewal job execution
Jobs	Create_Immediate_Job	Triggers on-demand plan upgrade jobs instantly for real-time plan change requests
Cache	Create_Segment	Creates a dedicated cache segment to hold active subscription state data
Cache	Create_Cache_Item	Stores individual subscription states in the segment to reduce authentication overhead per request
Cron	Create_Cron_Job	Schedules the monthly midnight renewal processing job to run on the first of every month
Stratus	Create_Bucket	Creates the billing-archives bucket to store versioned monthly billing summaries
Stratus	Generate_Signed_URL	Generates pre-signed URLs for account owners to securely download their invoices without platform authentication

Build a B2B Sales Intelligence and Prospecting Engine

Prompt

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

Catalyst Component	MCP Tool	Purpose
Dataverse	Lead_Enrichment	Gathers detailed company and contact data to enrich the target prospect records
	Similar_Companies	Identifies adjacent prospects in the same industry vertical for pipeline expansion
	Tech_Stack_Finder	Qualifies prospects based on their existing technology infrastructure
Datastore	Create_Table	Creates the Prospect Pipeline table to store all enriched and qualified lead records
Datastore	Insert_Rows	Inserts enriched lead records into the Prospect Pipeline table
Jobs	Create_Bulk_Write_Job	Imports existing CRM exports into the Prospect Pipeline table via a bulk write operation
Circuits	Execute_Circuit	Orchestrates the end-to-end enrichment and qualification workflow from lead intake to scoring
Job Pool	Create_Job_Pool	Creates a pool to manage concurrent enrichment jobs across large prospect batches
Cron	Create_Cron_Job	Schedules the weekly Monday 6:00 AM refresh job to pull in newly enriched pipeline data
API Gateway	Configure_API_Gateway_Route	Exposes prospect data via API routes for the front-end sales dashboard to consume
Cache	Create_Segment	Creates a dedicated cache segment to store the top-ranked prospect records
Cache	Create_Cache_Item	Caches the top 100 ranked prospects for instant dashboard load without datastore queries
Stratus	Create_Bucket	Creates the sales-intelligence bucket to store prospect export files
Stratus	Generate_Signed_URL	Generates pre-signed URLs for the sales team to securely download their assigned prospect lists

Build a Real-Time Logistics and Delivery Tracking Platform

Prompt

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

Catalyst Component	MCP Tool	Purpose
API Gateway	Configure_API_Gateway_Route	Creates endpoints for order intake, driver assignment, status updates, and delivery confirmation
Serverless Functions	Execute_Function_Via_POST	Executes order creation and assignment functions via POST for new delivery submissions
	Execute_Function_Via_PATCH	Executes status update functions via PATCH for incremental delivery status transitions
	Create_Env_Variables	Sets region-specific API keys and routing service credentials as function environment variables
Job Pool	Create_Job_Pool	Creates a pool to manage concurrent dispatch jobs across simultaneous delivery assignments
Jobs	Create_Immediate_Job	Triggers urgent on-demand delivery assignment jobs instantly for priority dispatches
Cache	Create_Segment	Creates a dedicated cache segment to hold real-time delivery status data
Cache	Create_Cache_Item	Caches per-order delivery status so the tracking dashboard polls without backend round-trips
Cron	Create_Cron_Job	Schedules an hourly job to reconcile undelivered orders and surface delivery exceptions
Stratus	Create_Bucket	Creates the delivery-records bucket to store confirmation documents and proof-of-delivery images
Stratus	Generate_Signed_URL	Generates pre-signed URLs for customers to access delivery confirmation records securely
Logs	Get_Logs	Retrieves logs filtered by error level to proactively detect and monitor failed delivery events

Build a Catalyst-Powered DevOps Automation Platform

Prompt

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

Catalyst Component	MCP Tool	Purpose
Dataverse	Lead_Enrichment	Gathers detailed company and contact data to enrich the target prospect records
	Similar_Companies	Identifies adjacent prospects in the same industry vertical for pipeline expansion
	Tech_Stack_Finder	Qualifies prospects based on their existing technology infrastructure
Datastore	Create_Table	Creates the Prospect Pipeline table to store all enriched and qualified lead records
Datastore	Insert_Rows	Inserts enriched lead records into the Prospect Pipeline table
Jobs	Create_Bulk_Write_Job	Imports existing CRM exports into the Prospect Pipeline table via a bulk write operation
Circuits	Execute_Circuit	Orchestrates the end-to-end enrichment and qualification workflow from lead intake to scoring
Job Pool	Create_Job_Pool	Creates a pool to manage concurrent enrichment jobs across large prospect batches
Cron	Create_Cron_Job	Schedules the weekly Monday 6:00 AM refresh job to pull in newly enriched pipeline data
API Gateway	Configure_API_Gateway_Route	Exposes prospect data via API routes for the front-end sales dashboard to consume
Cache	Create_Segment	Creates a dedicated cache segment to store the top-ranked prospect records
Cache	Create_Cache_Item	Caches the top 100 ranked prospects for instant dashboard load without datastore queries
Stratus	Create_Bucket	Creates the sales-intelligence bucket to store prospect export files
Stratus	Generate_Signed_URL	Generates pre-signed URLs for the sales team to securely download their assigned prospect lists

Build an AI-Powered Content Publishing Platform

Prompt

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

Catalyst Component	MCP Tool	Purpose
Authentication	Enable_Authentication	Enables user authentication to secure the content platform across all editorial roles
Authentication	List_All_Roles	Retrieves existing roles to configure Writer, Editor, and Publisher access levels
API Gateway	Configure_API_Gateway_Route	Creates endpoints for content submission, review, approval, and scheduling
API Gateway	Create_CORS_Domain	Registers the editorial dashboard and public reader portal as separate allowed CORS origins
Circuits	Execute_Circuit	Orchestrates the end-to-end editorial workflow from submission through to publication
Cron	Create_Cron_Job	Schedules automated article publication at release times and weekly digest notifications every Friday
Stratus	Create_Bucket	Creates the content-assets bucket to store media files including images, videos, and attachments
Stratus	Create_Upload_Signature	Generates pre-signed upload signatures for writers to upload media assets directly from the browser
Cache	Create_Segment	Creates a dedicated cache segment to hold recently published article data
Cache	Create_Cache_Item	Caches the most recently published articles to accelerate front-end load times
Web Client Hosting	List_All_Web_Apps	Retrieves web app configurations to support deploying the content platform

Build a Multi-Region Event Management Platform

Prompt

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

Catalyst Component	MCP Tool	Purpose
API Gateway	Configure_API_Gateway_Route	Creates endpoints for event creation, attendee registration, ticket generation, and cancellation
Serverless Functions	Execute_Function_Via_GET	Executes event and ticket retrieval functions via GET requests
	Execute_Function_Via_POST	Executes event creation and attendee registration functions via POST requests
	Execute_Function_Via_PUT	Executes event update functions via PUT requests
	Execute_Function_Via_DELETE	Executes cancellation and cleanup functions via DELETE requests
Authentication	Enable_Authentication	Enables user authentication to secure event creation, ticketing, and registration operations
Authentication	List_All_Roles	Retrieves and configures roles for Event Organizer, Attendee, and Platform Admin
Job Pool	Create_Job_Pool	Creates a pool to manage high-concurrency ticket processing during peak registration windows
Jobs	Create_Immediate_Job	Triggers on-demand ticket reissuance jobs instantly when requested
Jobs	Create_Bulk_Read_Job	Creates a bulk read job to export attendee data for post-event reporting
Cache	Create_Segment	Creates a dedicated cache segment to store event capacity and availability data
Cache	Create_Cache_Item	Caches event capacity state to prevent overselling under high registration load
Cron	Create_Cron_Job	Schedules pre-event automated reminder dispatch and post-event attendee data export trigger
Stratus	Create_Bucket	Creates the event-assets and event-reports buckets for event materials and exported attendee data
Stratus	Generate_Signed_URL	Generates pre-signed URLs for attendees to securely access event materials

Build a Catalyst AppSail-Powered Microservices Platform

Prompt

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

Catalyst Component	MCP Tool	Purpose
AppSail	List_All_AppSail	Retrieves all existing AppSail service configurations for mapping to API routes
	Get_AppSail	Retrieves detailed configuration for each individual AppSail service
	Create_Env_Variables	Sets runtime credentials and service-to-service communication keys per service deployment
API Gateway	Configure_API_Gateway_Route	Maps each microservice to its corresponding API Gateway route
API Gateway	Create_CORS_Domain	Registers each service's permitted front-end origin as a separate CORS domain
Circuits	Execute_Circuit	Orchestrates cross-service workflows such as payment confirmation triggering notifications and analytics logging
Job Pool	Create_Job_Pool	Creates a pool to manage concurrent background processing jobs across all microservices
Cron	Create_Cron_Job	Schedules maintenance window jobs for payments reconciliation, analytics aggregation, and notification queue flush
Cache	Create_Segment	Creates a dedicated cache segment to store inter-service authentication tokens
Cache	Create_Cache_Item	Caches authentication tokens to eliminate redundant token generation on every service call
Stratus	Create_Bucket	Creates the microservices-audit bucket to store service-level audit logs
Authentication	Enable_Authentication	Enables platform-level authentication to secure all microservice interactions
Authentication	List_All_Roles	Retrieves and configures roles scoped to each microservice domain

Build a Healthcare Appointment and Records Management System

Prompt

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

Catalyst Component	MCP Tool	Purpose
Authentication	Enable_Authentication	Enables user authentication for the healthcare platform, securing all patient and physician data
Authentication	List_All_Roles	Configures Patient, Physician, Nurse, and Admin roles with appropriate access levels
Datastore	Update_Table_Permissions	Sets granular table permissions so patients can only read and write their own records
Datastore	Update_Table_Scopes	Configures table scope to enforce per-user data isolation across patient records
API Gateway	Configure_API_Gateway_Route	Creates endpoints for appointment booking, cancellation, rescheduling, and medical record retrieval
Serverless Functions	Execute_Function_Via_GET	Executes medical record and schedule retrieval functions via GET requests
	Execute_Function_Via_POST	Executes appointment booking functions via POST requests
	Execute_Function_Via_PATCH	Executes appointment rescheduling functions via PATCH for partial updates
	Create_Env_Variables	Configures HIPAA-compliant service credentials and encryption keys as function environment variables
Circuits	Execute_Circuit	Orchestrates the appointment confirmation workflow including availability checks and notification dispatch
Cron	Create_Cron_Job	Schedules the 7:00 AM daily schedule generation job and the 10:00 PM completed appointment archival job
Stratus	Create_Bucket	Creates the patient-records bucket to store documents, lab reports, and prescriptions
Stratus	Generate_Signed_URL	Generates per-patient time-limited pre-signed URLs for secure document access
Cache	Create_Segment	Creates a dedicated cache segment to store physician availability slots
Cache	Create_Cache_Item	Caches physician availability slots to accelerate the appointment booking experience

Build a Catalyst-Powered IoT Data Ingestion and Monitoring Platform

Prompt

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

Catalyst Component	MCP Tool	Purpose
API Gateway	Configure_API_Gateway_Route	Creates endpoints for device registration, data ingestion, threshold alerts, and device status updates
Serverless Functions	Execute_Function_Via_POST	Executes data ingestion functions via POST for incoming sensor data streams
	Execute_Function_Via_GET	Executes device status retrieval functions via GET requests
	Create_Env_Variables	Configures facility-specific device authentication credentials as function environment variables
Job Pool	Create_Job_Pool	Creates a pool to manage high-concurrency data ingestion jobs from simultaneous device streams
Jobs	Create_Immediate_Job	Triggers on-demand device diagnostic jobs instantly for field engineer requests
Jobs	Create_Bulk_Read_Job	Creates a bulk read job to export the day's sensor data for archival at midnight
Circuits	Execute_Circuit	Orchestrates the alert workflow evaluating sensor readings against thresholds and triggering breach notifications
Cron	Create_Cron_Job	Schedules the 15-minute telemetry aggregation job and the midnight sensor data archival job
Stratus	Create_Bucket	Creates the iot-telemetry bucket to store versioned archived telemetry and device configuration files
Cache	Create_Segment	Creates a dedicated cache segment to store the latest sensor readings per device
Cache	Create_Cache_Item	Caches the most recent sensor reading per device for near real-time dashboard display
Logs	Get_Logs	Retrieves logs filtered by error level to detect device connectivity failures

Catalyst MCP Tools in Multi-Service Zoho Workflows

You can execute these prompts using:

2 Zoho MCP Servers: Catalyst Global MCP Server and an On-Demand Zoho MCP Server configured with the required MCP Tools of other Zoho services.
An On-Demand Zoho MCP Server, configured to contain MCP tools from multiple Zoho Services, including Catalyst by Zoho.

Build an Automated Customer Support Intelligence Platform

Prompt

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

Zoho Service	MCP Tool	Purpose
Catalyst by Zoho	Create_Table	Creates the Support Intelligence datastore table to store enriched ticket and contact records
	Insert_Rows	Inserts enriched ticket and contact data into the Support Intelligence table
	Execute_Circuit	Orchestrates the full triage workflow from ticket webhook receipt through enrichment, priority evaluation, and agent reassignment
	Create_Cron_Job	Schedules the daily 7:00 AM job to generate and export the support health report
	Create_Bulk_Read_Job	Exports the daily report data from the datastore for storage in the support-reports Stratus bucket
	Create_Immediate_Job	Triggers on-demand triage and enrichment for newly received ticket webhooks outside the scheduled run
Zoho Desk	getTickets	Pulls all open and overdue tickets from the helpdesk for triage and enrichment
	searchTickets	Searches tickets to filter overdue and high-priority cases requiring escalation
	getContact	Retrieves the contact details associated with each ticket for Dataverse enrichment
	updateTicket	Updates ticket priority tags to escalate issues from identified high-value customers
	getAgents	Retrieves available agents by department for automatic ticket reassignment
Zoho CRM	getLeadsRecords	Cross-references enriched contacts against CRM lead records to identify high-value prospects with active support issues
	getAccountsRecord	Retrieves CRM account data to flag high-value customers experiencing recurring support problems
	Lead_Enrichment	Enriches ticket contact records with additional company and lead intelligence from Catalyst Dataverse
Zoho Analytics	import_data	Pushes enriched ticket and contact data into the Zoho Analytics workspace
	query_data	Queries aggregated support data to compile the daily health report
	create_chart_report	Creates a chart breaking down ticket volume by priority, department, and resolution time
	create_summary_report	Creates a summary report for the daily support health dashboard

Launch a Full Product Lifecycle Management Platform

Prompt

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

Zoho Service	MCP Tool	Purpose
Catalyst by Zoho	Execute_Circuit	Triggers the fulfillment workflow when a Books sales order is approved, orchestrating delivery challan creation, team assignment, and project task updates
	Configure_API_Gateway_Route	Creates API endpoints for order status, fulfillment tracking, and invoice generation
	Create_Cron_Job	Schedules the weekly Monday 8:00 AM sales summary generation job
	Create_Bulk_Read_Job	Generates the weekly sales summary by exporting order data from the datastore for storage in the sales-exports bucket
	Create_Serverless_Function	Creates the webhook handler function that receives and processes Zoho Books invoice approval and overdue events
Zoho Books	create_sales_order	Creates a sales order when a new product order is initiated in the platform
	create_invoice	Generates invoices for completed and approved product orders
	create_delivery_challan	Creates a delivery challan when the Catalyst circuit triggers fulfillment for an approved order
	create_recurring_invoice	Sets up a recurring invoice profile for subscription-based product orders
	enable_recurring_invoice_autobill	Enables automatic billing against the customer's stored payment method for recurring subscriptions
	create_webhook	Sets up a Zoho Books webhook to notify the Catalyst circuit when invoices are approved or become overdue
	bulk_invoice_reminder	Sends automated payment reminder emails to customers with overdue invoices
Zoho Analytics	import_data	Pushes order, invoice, and delivery data into the Zoho Analytics workspace
	create_pivot_report	Creates a pivot report showing revenue broken down by product category and customer
	create_summary_report	Creates a summary report tracking order-to-delivery cycle times
	create_chart_report	Creates a chart report for visual revenue trend analysis across the product portfolio

Build a Unified B2B Revenue Operations Platform

Prompt

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

Zoho Service	MCP Tool	Purpose
Catalyst by Zoho	Lead_Enrichment	Enriches prospect records with detailed company and contact intelligence for qualification
	Similar_Companies	Identifies new prospects similar to existing high-value accounts for pipeline expansion
	Tech_Stack_Finder	Qualifies prospects based on their existing technology infrastructure before CRM entry
	Create_Cron_Job	Schedules the weekly Friday 5:00 PM pipeline report generation job
	Create_Table	Creates the Meeting Intelligence table to store post-meeting attendance and engagement data
	Insert_Rows	Stores participant report and meeting engagement data in the Meeting Intelligence table
Zoho CRM	createLeadsRecords	Pushes enriched prospect records into Zoho CRM as new lead entries with assigned owners
	postWorkflowRule	Configures the CRM workflow rule that triggers when a lead reaches the qualified stage to initiate the estimate and meeting flow
	getDealsRecords	Retrieves open deal data from CRM for the weekly pipeline report consolidation
	updateLeadsRecord	Updates lead records with qualification status and owner assignments after enrichment
Zoho Books	create_estimate	Creates a sales estimate in Zoho Books when a CRM lead reaches the qualified stage
	email_estimate	Sends the estimate to the prospect for review immediately after creation
	approve_estimate	Marks estimates as approved for tracking in the estimate-to-deal conversion pipeline
Zoho Meeting	createMeetingSession	Schedules a Zoho Meeting between the assigned sales rep and the qualified prospect
	getParticipantReport	Retrieves post-meeting attendance and engagement data for storage in the Meeting Intelligence table
	getMeetingDetails	Retrieves full meeting metadata to store alongside engagement records in the Meeting Intelligence table
Zoho Analytics	import_data	Pushes consolidated pipeline, estimate, and meeting engagement data into the Analytics workspace
	query_data	Queries CRM deals, Books estimates, and Meeting Intelligence data for the weekly pipeline report
	create_chart_report	Creates a pipeline value by stage chart report for the weekly revenue summary
	create_summary_report	Creates an estimate-to-deal conversion rate summary report for the dashboard

Build a Multi-Channel Customer Engagement and Retention Platform

Prompt

With Catalyst MCP server connected, the LLM uses the given prompt to access and implement the following Catalyst components:

Zoho Service	MCP Tool	Purpose
Catalyst by Zoho	Execute_Circuit	Orchestrates the engagement workflow per at-risk account, triggering CRM task creation, meeting scheduling, and retention estimate generation
	Create_Cache_Item	Stores at-risk account data and engagement action states in a cache segment for fast retrieval by the account management dashboard
	Create_Job_Pool	Manages concurrent engagement workflows across large at-risk account volumes
	Create_Cron_Job	Schedules the Sunday 6:00 AM refresh of the at-risk account list
	Create_Immediate_Job	Triggers the engagement workflow immediately for newly identified at-risk accounts outside the scheduled refresh
Zoho Desk	getTickets	Pulls open tickets to identify contacts with more than three unresolved tickets in the past 30 days
	searchTickets	Searches for unresolved tickets from the past 30 days to build the at-risk contact list
	getContact	Retrieves contact details for ticket owners to cross-reference against CRM accounts
	getContactStatistics	Gets ticket statistics per contact to identify those exceeding the three-ticket threshold in the 30-day window
Zoho CRM	getAccountsRecord	Retrieves CRM account records to match against identified at-risk contacts and confirm account value
	updateDealsRecord	Updates deal records for at-risk accounts to flag escalation status for the account owner
	createWorkflowTasks	Creates a CRM follow-up task for the account owner for each identified at-risk account
Zoho Books	create_pricebook	Creates the custom pricebook containing special retention pricing offers for at-risk accounts
	create_estimate	Generates a personalised retention estimate with the special pricing offer for each at-risk account
	apply_pricebook_to_invoice	Applies the retention pricebook pricing to the generated estimate for the at-risk customer
Zoho Analytics	import_data	Pushes customer health metrics including ticket volume, deal stage, meeting history, and estimate status into the Analytics workspace
	create_summary_report	Creates a report tracking engagement actions taken per account owner across the at-risk portfolio
	create_chart_report	Creates a chart visualising at-risk account distribution by industry and revenue band

Last Updated 2026-07-27 22:16:44 +0530 IST

Yes

Thank you for your feedback!

Send your feedback to us

Skip

Submit

Zoho MCP Help Zoho MCP Tool List Catalyst MCP Server Overview