@kadoa/mcp 0.3.5-rc.0 → 0.3.5-rc.1

package/dist/index.js

@@ -49275,7 +49275,13 @@ function registerTools(server, ctx) {
     });
   }));
   server.registerTool("create_workflow", {
-    description: "Create a new workflow that extracts data using agentic navigation. Supports one-time, scheduled, and real-time (continuous monitoring) modes via the interval parameter. If entity and schema are provided, they guide the extraction. Otherwise, the AI agent auto-detects the schema from the page based on the prompt. The workflow runs asynchronously and may take several minutes. Do NOT poll or sleep-wait for completion. Instead, return the workflow ID to the user and let them check back later with get_workflow or fetch_data.",
+    description: `Create a new workflow that extracts data using agentic navigation. Supports one-time, scheduled, and real-time (continuous monitoring) modes via the interval parameter. If entity and schema are provided, they guide the extraction. Otherwise, the AI agent auto-detects the schema from the page based on the prompt. The workflow runs asynchronously and may take several minutes. Do NOT poll or sleep-wait for completion. Instead, return the workflow ID to the user and let them check back later with get_workflow or fetch_data.
+
+` + `IMPORTANT — REAL_TIME vs regular workflows:
+` + `• REAL_TIME workflows are fundamentally different from regular extraction workflows. They route to a separate Observer service, run continuously, and cannot be triggered manually.
+` + `• A regular workflow CANNOT be converted to real-time after creation (and vice versa). The interval=REAL_TIME flag MUST be set at creation time.
+` + `• If the user wants to monitor a page for changes, set interval='REAL_TIME' here. Do NOT create a regular workflow and then try to change its interval to REAL_TIME via update_workflow — this will be rejected.
+` + "• When unclear whether the user wants monitoring (real-time) or data extraction (regular), ask them to clarify before creating the workflow.",
     inputSchema: {
       prompt: exports_external.string().describe('Natural language description of what to extract (e.g., "Extract product prices and names")'),
       urls: exports_external.array(exports_external.string()).min(1).describe("Starting URLs for the workflow"),
@@ -49514,7 +49520,9 @@ function registerTools(server, ctx) {
     });
   }));
   server.registerTool("update_workflow", {
-    description: "Update a workflow's configuration. All fields are optional — only provided fields will be updated. Use this to change the name, URLs, extraction schema, entity, prompt, schedule, or other metadata.",
+    description: `Update a workflow's configuration. All fields are optional — only provided fields will be updated. Use this to change the name, URLs, extraction schema, entity, prompt, schedule, or other metadata.
+
+` + "IMPORTANT: You cannot change a workflow's interval to or from REAL_TIME. Real-time workflows are architecturally different (Observer service vs Scraper) and must be created as real-time from the start using create_workflow with interval='REAL_TIME'. To switch a workflow between real-time and regular, delete it and create a new one with the correct interval.",
     inputSchema: {
       workflowId: exports_external.string().describe("The workflow ID to update"),
       name: exports_external.string().optional().describe("New name for the workflow"),
@@ -49541,15 +49549,25 @@ function registerTools(server, ctx) {
         "TRIWEEKLY",
         "FOUR_WEEKS",
         "MONTHLY",
-        "REAL_TIME",
         "CUSTOM"
-      ]).optional().describe("How often the workflow should run. Use REAL_TIME for continuous monitoring, CUSTOM with schedules for cron-based."),
+      ]).optional().describe("How often the workflow should run. CUSTOM requires schedules. Note: REAL_TIME is NOT allowed here — real-time workflows must be created via create_workflow."),
       schedules: exports_external.array(exports_external.string()).optional().describe("Cron expressions for CUSTOM update interval"),
       limit: exports_external.number().optional().describe("Maximum number of records to extract per run")
     },
     annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: true }
   }, withErrorHandling("update_workflow", async (args) => {
     const { workflowId, ...updates } = args;
+    if (updates.updateInterval) {
+      const workflow = await ctx.client.workflow.get(workflowId);
+      const isCurrentlyRealTime = workflow.updateInterval === "REAL_TIME";
+      const isRequestingRealTime = updates.updateInterval === "REAL_TIME";
+      if (isRequestingRealTime && !isCurrentlyRealTime) {
+        return errorResult("Cannot change a regular workflow's interval to REAL_TIME. " + "Real-time workflows use a different service (Observer) and must be created as real-time from the start. " + "Delete this workflow and create a new one with interval='REAL_TIME' using create_workflow.");
+      }
+      if (!isRequestingRealTime && isCurrentlyRealTime) {
+        return errorResult("Cannot change a real-time workflow's interval to a scheduled interval. " + "Real-time workflows are architecturally different and cannot be converted to regular workflows. " + "Delete this workflow and create a new one with the desired interval using create_workflow.");
+      }
+    }
     const result = await ctx.client.workflow.update(workflowId, updates);
     return jsonResult({
       success: true,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kadoa/mcp",
-  "version": "0.3.5-rc.0",
+  "version": "0.3.5-rc.1",
   "description": "Kadoa MCP Server — manage workflows from Claude Desktop, Cursor, and other MCP clients",
   "type": "module",
   "main": "dist/index.js",