@parseable/parseable-mcp-server - npm Package Compare versions

Comparing version 0.2.11 to 0.2.12

dist/bootstrap.d.ts

 import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import type { ToolContext } from "./tools/types.js";
-declare const SERVER_VERSION = "0.2.11";
+declare const SERVER_VERSION = "0.2.12";
 export declare function buildMcpServer(ctx: ToolContext): McpServer;
 export { SERVER_VERSION };

dist/bootstrap.js

@@ -6,3 +6,3 @@ import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { errorResult, jsonResult } from "./tools/types.js";
-const SERVER_VERSION = "0.2.11";
+const SERVER_VERSION = "0.2.12";
 export function buildMcpServer(ctx) {
@@ -9,0 +9,0 @@ const server = new McpServer({

dist/tools/create_alert.js

 import { z } from "zod";
 const schema = {
-    spec: z.record(z.unknown()).describe(`Full alert spec, camelCase JSON. Required:
-- title (string)
-- query (string, SQL SELECT returning a single numeric column)
-- alertType ("threshold" | "anomaly" | "forecast")
-- thresholdConfig { operator: ">"|"<"|"="|">="|"<="|"!=", value: number }
-- evalConfig { rollingWindow: { evalStart: "5m", evalEnd: "now", evalFrequency: 1 } }
-- targets (string[] - target UUIDs; empty array if no destinations)
+    spec: z.record(z.unknown()).describe(`Complete alert object sent as the POST /api/v1/alerts request body. Use camelCase JSON:
+{
+  "title": "High error count",
+  "alertType": "threshold",
+  "query": "SELECT ... FROM logs ...",
+  "severity": "high",
+  "thresholdConfig": { "operator": ">", "value": 10 },
+  "evalConfig": {
+    "rollingWindow": {
+      "evalStart": "10 minutes",
+      "evalEnd": "now",
+      "evalFrequency": 10
+    }
+  },
+  "anomalyConfig": { "historicDuration": "1d" },
+  "forecastConfig": { "historicDuration": "1d", "forecastDuration": "3h" },
+  "notificationConfig": { "interval": 1 },
+  "targets": ["target-id"],
+  "tags": []
+}
 
-Optional:
-- severity ("critical"|"high"|"medium"|"low", default "medium")
-- tags (string[])
-- notificationConfig (object)
+Required by the Prism create-alert flow: title, alertType, query, severity,
+thresholdConfig, evalConfig, anomalyConfig, forecastConfig,
+notificationConfig, targets, and tags. thresholdConfig.value and both interval
+fields are numbers. evalStart uses a duration such as "10 minutes"; evalEnd is
+"now"; evalFrequency is minutes. targets must contain valid alert-target IDs.
+For threshold alerts, use alertType "threshold". Prism currently shows anomaly
+and forecast as unavailable creation modes; retain their default config objects.
 
@@ -28,13 +44,18 @@ Reference: https://www.parseable.com/docs/user-guide/alerting`),
 3. "What condition should trigger it?" → translate user's natural-language condition into:
-   - a SQL SELECT against the dataset that returns a single numeric column
+   - alert SQL against the selected dataset, matching Parseable's alert-query format
    - operator from > < = >= <= !=
    - numeric threshold value
    Confirm the translated SQL + operator + value back to the user.
-4. "How far back should each check look?" → evalStart (e.g. "5m", "15m", "1h")
+4. "How far back should each check look?" → evalStart (e.g. "5 minutes", "15 minutes", "1 hour")
 5. "How often should it evaluate?" → evalFrequency in minutes (integer)
-6. "Severity: critical, high, medium, or low?" → default medium
+6. "Severity: critical, high, medium, or low?" → default high
 7. "Any tags? (comma-separated, optional)" → tags array, empty if none
-8. "Notification targets?" → call list_alert_targets to fetch existing targets, present them as a numbered list, ask user to pick by number/name. Collect chosen target IDs into the targets array. If no targets exist or user wants none, use an empty array.
+8. "Notification targets?" → call list_alert_targets to fetch existing targets, present them as a numbered list, ask user to pick by number/name. Collect chosen target IDs into the targets array. Prism requires at least one target to create an alert.
 
-Then show the fully assembled JSON spec to the user and ask "Create this alert?" Only call create_alert after explicit confirmation. If user wants edits, update fields and re-confirm.`,
+Assemble alertType "threshold", evalEnd "now", anomalyConfig
+{ historicDuration: "1d" }, forecastConfig { historicDuration: "1d",
+forecastDuration: "3h" }, and notificationConfig { interval: 1 } unless the user
+requests supported alternatives. Then show the complete JSON spec and ask "Create
+this alert?" Only call create_alert after explicit confirmation. If user wants
+edits, update fields and re-confirm.`,
     inputSchema: schema,
@@ -41,0 +62,0 @@ handler: async (args, { client }) => {

dist/tools/create_alert.js.map

@@ -1,1 +0,1 @@
-{"version":3,"file":"create_alert.js","sourceRoot":"","sources":["../../src/tools/create_alert.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAGxB,MAAM,MAAM,GAAG;IACb,IAAI,EAAE,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,OAAO,EAAE,CAAC,CAAC,QAAQ,CAClC;;;;;;;;;;;;;8DAa0D,CAC3D;CACF,CAAC;AAEF,MAAM,CAAC,MAAM,WAAW,GAA2B;IACjD,IAAI,EAAE,cAAc;IACpB,KAAK,EAAE,cAAc;IACrB,WAAW,EAAE;;;;;;;;;;;;;;;;;wLAiByK;IACtL,WAAW,EAAE,MAAM;IACnB,OAAO,EAAE,KAAK,EAAE,IAAI,EAAE,EAAE,MAAM,EAAE,EAAE,EAAE;QAClC,OAAO,MAAM,MAAM,CAAC,WAAW,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IAC7C,CAAC;CACF,CAAC"}
+{"version":3,"file":"create_alert.js","sourceRoot":"","sources":["../../src/tools/create_alert.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAC;AAGxB,MAAM,MAAM,GAAG;IACb,IAAI,EAAE,CAAC,CAAC,MAAM,CAAC,CAAC,CAAC,OAAO,EAAE,CAAC,CAAC,QAAQ,CAClC;;;;;;;;;;;;;;;;;;;;;;;;;;;;;8DA6B0D,CAC3D;CACF,CAAC;AAEF,MAAM,CAAC,MAAM,WAAW,GAA2B;IACjD,IAAI,EAAE,cAAc;IACpB,KAAK,EAAE,cAAc;IACrB,WAAW,EAAE;;;;;;;;;;;;;;;;;;;;;;qCAsBsB;IACnC,WAAW,EAAE,MAAM;IACnB,OAAO,EAAE,KAAK,EAAE,IAAI,EAAE,EAAE,MAAM,EAAE,EAAE,EAAE;QAClC,OAAO,MAAM,MAAM,CAAC,WAAW,CAAC,IAAI,CAAC,IAAI,CAAC,CAAC;IAC7C,CAAC;CACF,CAAC"}

package.json

 {
   "name": "@parseable/parseable-mcp-server",
-  "version": "0.2.11",
+  "version": "0.2.12",
   "description": "Model Context Protocol server for Parseable. Lets LLMs discover and query Parseable datasets.",
@@ -5,0 +5,0 @@ "repository": {

New alerts

Long strings

Supply chain risk

Contains long string literals, which may be a sign of obfuscated or packed code.

URL strings

Supply chain risk

Package contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.

Fixed alerts

Long strings

Supply chain risk

Contains long string literals, which may be a sign of obfuscated or packed code.

URL strings

Supply chain risk

Package contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.

Improved metrics

Total package byte prevSize

151117

0.59%

Lines of code

1877

1.13%

Worsened metrics

Number of low supply chain risk alerts

21

5%

No dependency changes