redash-mcp 3.1.5 → 3.1.6

package/README.ja.md

@@ -4,6 +4,7 @@
 [![Downloads](https://img.shields.io/npm/dm/redash-mcp.svg)](https://www.npmjs.com/package/redash-mcp)
 [![Node](https://img.shields.io/node/v/redash-mcp.svg)](https://nodejs.org)
 [![smithery badge](https://smithery.ai/badge/dev-seob717/redash-mcp)](https://smithery.ai/servers/dev-seob717/redash-mcp)
+[![Glama](https://glama.ai/mcp/servers/seob717/redash-mcp/badges/score.svg)](https://glama.ai/mcp/servers/seob717/redash-mcp)
 
 [English](README.md) | [한국어](README.ko.md) | 日本語
 
@@ -11,6 +12,8 @@
 
 [なぜ redash-mcp か](#なぜ-redash-mcp-か) · [機能](#機能) · [インストール](#インストール) · [環境変数](#環境変数) · [使用例](#使用例) · [Privacy](#privacy-policy)
 
+![redash-mcp デモ — Claude が Redash のテーブルを調べ、カテゴリ別売上をチャート化し、SQL セーフティガードが PII エクスポートをブロックする](docs/demo.gif)
+
 > 英語版 README との最終同期: 2026-06-09
 
 ---
@@ -252,3 +255,13 @@ redash-mcp は **ローカル MCP サーバー** であり、ユーザーの Red
 ### 連絡先
 
 お問い合わせ・セキュリティ報告: [GitHub Issues](https://github.com/seob717/redash-mcp/issues)
+
+---
+
+## 免責事項 (Disclaimer)
+
+redash-mcp はコミュニティが開発した非公式の統合ツールであり、**Redash とは提携・承認・後援のいずれの関係もありません**。「Redash」は各権利者の商標であり、ここでは互換性を説明する目的でのみ使用しています。本プロジェクトは Redash の公開 REST API を通じてのみ通信します。
+
+## ライセンス
+
+MIT © seob717

package/README.ko.md

@@ -4,6 +4,7 @@
 [![Downloads](https://img.shields.io/npm/dm/redash-mcp.svg)](https://www.npmjs.com/package/redash-mcp)
 [![Node](https://img.shields.io/node/v/redash-mcp.svg)](https://nodejs.org)
 [![smithery badge](https://smithery.ai/badge/dev-seob717/redash-mcp)](https://smithery.ai/servers/dev-seob717/redash-mcp)
+[![Glama](https://glama.ai/mcp/servers/seob717/redash-mcp/badges/score.svg)](https://glama.ai/mcp/servers/seob717/redash-mcp)
 
 [English](README.md) | 한국어 | [日本語](README.ja.md)
 
@@ -11,6 +12,8 @@
 
 [왜 redash-mcp인가](#왜-redash-mcp인가) · [기능](#기능) · [설치](#설치) · [환경 변수](#환경-변수) · [사용 예시](#사용-예시) · [Privacy](#privacy-policy)
 
+![redash-mcp 데모 — Claude가 Redash 테이블을 살펴보고, 카테고리별 매출을 차트로 만든 뒤, SQL 안전 가드가 PII 내보내기를 차단한다](docs/demo.gif)
+
 > 영문 README와 마지막 동기화: 2026-06-09
 
 ---
@@ -252,3 +255,13 @@ redash-mcp는 **로컬 MCP 서버**로, 사용자의 Redash 인스턴스와 직
 ### 연락처
 
 문의 및 보안 이슈 보고: [GitHub Issues](https://github.com/seob717/redash-mcp/issues)
+
+---
+
+## 고지 (Disclaimer)
+
+redash-mcp는 커뮤니티가 만든 비공식 통합 도구이며, **Redash와 제휴·보증·후원 관계가 없습니다**. "Redash"는 해당 상표권자의 상표이며, 여기서는 호환성을 설명하기 위한 용도로만 사용합니다. 이 프로젝트는 Redash의 공개 REST API를 통해서만 통신합니다.
+
+## 라이선스
+
+MIT © seob717

package/README.md

@@ -4,6 +4,7 @@
 [![Downloads](https://img.shields.io/npm/dm/redash-mcp.svg)](https://www.npmjs.com/package/redash-mcp)
 [![Node](https://img.shields.io/node/v/redash-mcp.svg)](https://nodejs.org)
 [![smithery badge](https://smithery.ai/badge/dev-seob717/redash-mcp)](https://smithery.ai/servers/dev-seob717/redash-mcp)
+[![Glama](https://glama.ai/mcp/servers/seob717/redash-mcp/badges/score.svg)](https://glama.ai/mcp/servers/seob717/redash-mcp)
 
 English | [한국어](README.ko.md) | [日本語](README.ja.md)
 
@@ -11,6 +12,8 @@ English | [한국어](README.ko.md) | [日本語](README.ja.md)
 
 [Why](#why-redash-mcp) · [Features](#features) · [Install](#installation) · [Env](#environment-variables) · [Examples](#usage-examples) · [Privacy](#privacy-policy)
 
+![redash-mcp demo — Claude explores Redash tables, charts revenue by category, then the SQL safety guard blocks a PII export](docs/demo.gif)
+
 ---
 
 ## Why redash-mcp?
@@ -250,3 +253,13 @@ We do not sell or share user data with third parties. When the LLM Fallback feat
 ### Contact
 
 For inquiries and security reports: [GitHub Issues](https://github.com/seob717/redash-mcp/issues)
+
+---
+
+## Disclaimer
+
+redash-mcp is an unofficial, community-built integration and is **not affiliated with, endorsed by, or sponsored by Redash**. "Redash" is a trademark of its respective owners and is used here only to describe compatibility. This project communicates with Redash solely through its public REST API.
+
+## License
+
+MIT © seob717

package/dist/index.js

@@ -8610,12 +8610,13 @@ ${c}
 // src/setup.ts
 var setup_exports = {};
 __export(setup_exports, {
+  buildClaudeMcpAddArgs: () => buildClaudeMcpAddArgs,
   main: () => main
 });
 import * as fs from "fs";
 import * as path3 from "path";
 import * as os2 from "os";
-import { execSync } from "child_process";
+import { execFileSync, execSync } from "child_process";
 function findNpxPath() {
   try {
     const result = execSync("which npx", { encoding: "utf8" }).trim();
@@ -8642,8 +8643,18 @@ function getDesktopConfigPath() {
     return path3.join(os2.homedir(), ".config", "Claude", "claude_desktop_config.json");
   }
 }
-function getClaudeCodeConfigPath() {
-  return path3.join(os2.homedir(), ".claude", "settings.json");
+function buildClaudeMcpAddArgs(mcpEntry) {
+  return [
+    "mcp",
+    "add",
+    "--scope",
+    "user",
+    "redash-mcp",
+    ...Object.entries(mcpEntry.env).flatMap(([key, value]) => ["-e", `${key}=${value}`]),
+    "--",
+    mcpEntry.command,
+    ...mcpEntry.args
+  ];
 }
 async function main() {
   ge("redash-mcp setup wizard");
@@ -8722,20 +8733,15 @@ function setupDesktop(mcpEntry) {
   fs.writeFileSync(configPath, JSON.stringify(config2, null, 2), "utf8");
 }
 function setupClaudeCode(mcpEntry) {
-  const configPath = getClaudeCodeConfigPath();
-  let config2 = {};
-  if (fs.existsSync(configPath)) {
-    try {
-      config2 = JSON.parse(fs.readFileSync(configPath, "utf8"));
-    } catch {
-      throw new Error(`Failed to read Claude Code settings.json: ${configPath}`);
-    }
-  } else {
-    fs.mkdirSync(path3.dirname(configPath), { recursive: true });
+  const args = buildClaudeMcpAddArgs(mcpEntry);
+  try {
+    execFileSync("claude", args, { stdio: "pipe" });
+  } catch {
+    throw new Error(
+      `Failed to run "claude mcp add". Make sure the Claude Code CLI is installed, or run manually:
+  claude ${args.join(" ")}`
+    );
   }
-  config2.mcpServers ??= {};
-  config2.mcpServers["redash-mcp"] = mcpEntry;
-  fs.writeFileSync(configPath, JSON.stringify(config2, null, 2), "utf8");
 }
 var init_setup = __esm({
   "src/setup.ts"() {
@@ -42130,7 +42136,7 @@ ${result.guidance}`);
   );
   server2.tool(
     "manage_few_shot_examples",
-    "Manage few-shot examples (list/add/remove). Register domain-specific examples to improve SQL accuracy.",
+    "Manage the few-shot examples that smart_query uses to generate more accurate SQL. Behavior: action 'list' returns all stored examples with their ids; 'add' saves a new example (requires the example object); 'remove' deletes one (requires example_id). Each example pairs a natural-language question with the correct SQL and the tables it uses, teaching the model your schema's domain conventions. Usage: examples are stored locally per data_source_id and are retrieved automatically by smart_query \u2014 register a few for recurring question patterns to raise accuracy.",
     {
       data_source_id: external_exports.number().describe("Data source ID"),
       action: external_exports.enum(["list", "add", "remove"]).describe("Action to perform"),
@@ -42200,7 +42206,7 @@ ${text}` }] };
   );
   server2.tool(
     "submit_query_feedback",
-    "Submit feedback on generated SQL. Incorrect SQL is automatically classified and may be promoted to a few-shot example.",
+    "Record whether the SQL produced for a question was correct, so smart_query improves over time. Behavior: stores an up/down rating; when you rate 'down' and supply the correct SQL, the error is classified and, if the same kind of mistake recurs, automatically promoted into a few-shot example. Returns the feedback id and any error type or promotion. Usage: call after reviewing smart_query/run_query output; feedback is stored locally per data_source_id and feeds the learning loop.",
     {
       data_source_id: external_exports.number().describe("Data source ID"),
       question: external_exports.string().describe("Original natural-language question"),
@@ -42232,7 +42238,7 @@ ${text}` }] };
   );
   server2.tool(
     "evaluate_queries",
-    "Manage SQL accuracy evaluation. Add/list test cases, run evaluations, and view results.",
+    "Build and run an accuracy test suite for SQL generation on a data source. Behavior: action 'add_test' stores a question paired with ground-truth SQL; 'list_tests' shows them; 'remove_test' deletes one; 'run' scores generated SQL against the test cases; 'results' shows the latest run. Usage: use this to measure whether keyword maps and few-shot examples actually improve smart_query accuracy over time; test cases and runs are stored locally per data_source_id.",
     {
       data_source_id: external_exports.number().describe("Data source ID"),
       action: external_exports.enum(["list_tests", "add_test", "remove_test", "run", "results"]).describe("Action to perform"),
@@ -42503,7 +42509,7 @@ ${tables.join("\n")}`;
 );
 server.tool(
   "get_table_columns",
-  "Get column names and types for one or more tables (comma-separated). Verify columns before writing SQL.",
+  "Get the column names and data types for one or more tables in a data source. Accepts a single table or a comma-separated list of tables. Use this to confirm exact column names and types before writing SQL with run_query or smart_query. Returns each table's columns; if a table name is not found, it suggests verifying it with list_tables.",
   {
     data_source_id: external_exports.number().describe("Data source ID from list_data_sources"),
     table_name: external_exports.string().describe("Table name(s), comma-separated (e.g., 'users' or 'users,orders')")
@@ -42543,7 +42549,7 @@ var MAX_TIMEOUT_SECS = 300;
 var MAX_CACHE_AGE_SECS = 86400 * 7;
 server.tool(
   "run_query",
-  "Execute SQL against a data source and return results. Check schema with list_tables and get_table_columns first.",
+  "Execute an ad-hoc SQL query against a data source and return the resulting rows. Every query passes through the SQL safety guard, which blocks destructive statements (DROP/TRUNCATE/ALTER, DELETE/UPDATE without WHERE) and flags PII columns and expensive full scans; results are cached in memory. Behavior: returns up to max_rows rows as a markdown table or JSON, with the column list and a truncation note when there are more rows. Usage: confirm table and column names with list_tables and get_table_columns first; for natural-language questions, plan the SQL with smart_query before calling this. To run an already-saved query instead, use get_query_result.",
   {
     data_source_id: external_exports.number().int().nonnegative().describe("Data source ID from list_data_sources"),
     query: external_exports.string().describe("SQL query to execute"),
@@ -42628,11 +42634,11 @@ ${body}`
 );
 server.tool(
   "list_queries",
-  "List saved queries in Redash.",
+  "List saved (named) queries in Redash, most recently updated first. Behavior: returns a paginated array where each item has id, name, description, data_source_id, and updated_at. Usage: use this to discover query_ids, then call get_query for a query's full SQL and visualizations, or get_query_result to run it. Supports keyword search and pagination; for ad-hoc SQL that isn't saved, use run_query instead.",
   {
-    search: external_exports.string().optional().describe("Search keyword"),
-    page: external_exports.number().optional().default(1),
-    page_size: external_exports.number().optional().default(20).describe("Page size (max 100)")
+    search: external_exports.string().optional().describe("Optional keyword to filter queries by name/description"),
+    page: external_exports.number().optional().default(1).describe("Page number to fetch, 1-based (default 1)"),
+    page_size: external_exports.number().optional().default(20).describe("Number of queries per page, 1-100 (default 20)")
   },
   { readOnlyHint: true },
   async ({ search, page, page_size }) => {
@@ -42662,9 +42668,9 @@ server.tool(
 );
 server.tool(
   "get_query_result",
-  "Execute a saved query by ID and return results.",
+  "Run an existing saved query by its ID and return the latest results. Behavior: executes the query as stored in Redash and returns up to max_rows rows as a markdown table or JSON, with the column list and a truncation note. Usage: find the query_id with list_queries or get_query. Unlike run_query, this executes already-saved SQL rather than ad-hoc SQL, so the safety guard does not apply.",
   {
-    query_id: external_exports.number().int().nonnegative().describe("Saved query ID (from list_queries)"),
+    query_id: external_exports.number().int().nonnegative().describe("ID of the saved query to run (from list_queries)"),
     max_rows: external_exports.number().int().min(1).max(MAX_ROWS_LIMIT).optional().default(100).describe(`Max rows to return (1 to ${MAX_ROWS_LIMIT}, default 100)`),
     format: external_exports.enum(["table", "json"]).optional().default("table").describe("Output format: table (markdown) or json"),
     timeout_secs: external_exports.number().int().min(1).max(MAX_TIMEOUT_SECS).optional().default(30).describe(`Query execution timeout in seconds (1 to ${MAX_TIMEOUT_SECS}, default 30)`)
@@ -42712,9 +42718,9 @@ ${body}`
 );
 server.tool(
   "get_query",
-  "Get saved query details (SQL, visualizations, tags).",
+  "Get the full definition of a saved query. Behavior: returns the query's SQL text, data_source_id, tags, owner, update time, and its visualizations (each with id, name, type). Usage: find the query_id with list_queries. The returned visualization ids can be placed on a dashboard with add_widget; to actually run the query use get_query_result.",
   {
-    query_id: external_exports.number().describe("Query ID (from list_queries)")
+    query_id: external_exports.number().describe("ID of the saved query to inspect (from list_queries)")
   },
   { readOnlyHint: true },
   async ({ query_id }) => {
@@ -42742,13 +42748,13 @@ server.tool(
 );
 server.tool(
   "create_query",
-  "Save a new query to Redash.",
+  "Save a new named SQL query to Redash so it can be reused, scheduled, visualized, or added to a dashboard. Behavior: creates the query and returns its new id, name, and created_at. Usage: get the data_source_id from list_data_sources and verify the SQL runs with run_query first; to change an existing query use update_query instead. Note: this only saves the query \u2014 use get_query_result to execute it.",
   {
-    name: external_exports.string().describe("Query name"),
-    query: external_exports.string().describe("SQL query"),
-    data_source_id: external_exports.number().describe("Data source ID from list_data_sources"),
-    description: external_exports.string().optional().describe("Query description"),
-    tags: external_exports.array(external_exports.string()).optional().describe("Tags")
+    name: external_exports.string().describe("Display name for the saved query"),
+    query: external_exports.string().describe("The SQL statement to save"),
+    data_source_id: external_exports.number().describe("ID of the data source this query runs against (from list_data_sources)"),
+    description: external_exports.string().optional().describe("Optional human-readable description of what the query does"),
+    tags: external_exports.array(external_exports.string()).optional().describe("Optional tags to categorize the query (e.g., ['finance', 'weekly'])")
   },
   { destructiveHint: true },
   async ({ name, query, data_source_id, description, tags }) => {
@@ -42775,13 +42781,13 @@ server.tool(
 );
 server.tool(
   "update_query",
-  "Update a saved query's name, SQL, description, or tags.",
+  "Update fields of an existing saved query. Behavior: only the fields you pass are changed (name, SQL, description, or tags); any omitted field is left untouched. Returns the query's id, name, and updated_at. Usage: find the query_id with list_queries or get_query; to create a brand-new query instead, use create_query.",
   {
-    query_id: external_exports.number().describe("Query ID to update"),
-    name: external_exports.string().optional().describe("New name"),
-    query: external_exports.string().optional().describe("New SQL"),
-    description: external_exports.string().optional().describe("New description"),
-    tags: external_exports.array(external_exports.string()).optional().describe("New tags")
+    query_id: external_exports.number().describe("ID of the saved query to update (from list_queries)"),
+    name: external_exports.string().optional().describe("New display name (omit to keep current)"),
+    query: external_exports.string().optional().describe("New SQL statement (omit to keep current)"),
+    description: external_exports.string().optional().describe("New description (omit to keep current)"),
+    tags: external_exports.array(external_exports.string()).optional().describe("New tag list, replacing the existing tags (omit to keep current)")
   },
   { destructiveHint: true },
   async ({ query_id, name, query, description, tags }) => {
@@ -42810,9 +42816,9 @@ server.tool(
 );
 server.tool(
   "fork_query",
-  "Fork (duplicate) an existing query.",
+  "Fork (duplicate) an existing saved query into a new, independently editable copy, leaving the original unchanged. Behavior: creates the copy and returns its new id and name. Usage: find the query_id to fork with list_queries; use this when you want to experiment with or adapt a query without modifying the original.",
   {
-    query_id: external_exports.number().describe("Query ID to fork")
+    query_id: external_exports.number().describe("ID of the saved query to duplicate (from list_queries)")
   },
   { destructiveHint: true },
   async ({ query_id }) => {
@@ -42836,9 +42842,9 @@ server.tool(
 );
 server.tool(
   "archive_query",
-  "Archive (delete) a query. This action is irreversible.",
+  "Archive a saved query, removing it from active query lists. This is Redash's form of deletion and cannot be undone through the API, so confirm with the user before calling it. Behavior: archives the query and returns a confirmation message. Usage: find the query_id with list_queries.",
   {
-    query_id: external_exports.number().describe("Query ID to archive")
+    query_id: external_exports.number().describe("ID of the saved query to archive/delete (from list_queries)")
   },
   { destructiveHint: true },
   async ({ query_id }) => {
@@ -42854,11 +42860,11 @@ server.tool(
 );
 server.tool(
   "list_dashboards",
-  "List dashboards in Redash.",
+  "List dashboards in Redash, most recently updated first. Behavior: returns a paginated array where each item has id, name, slug, and created/updated timestamps. Usage: use this to discover a dashboard's id or slug, then call get_dashboard to inspect its widgets and visualizations, or create_dashboard to make a new one. Supports keyword search and pagination.",
   {
-    search: external_exports.string().optional().describe("Search keyword"),
-    page: external_exports.number().optional().default(1),
-    page_size: external_exports.number().optional().default(20).describe("Page size (max 100)")
+    search: external_exports.string().optional().describe("Optional keyword to filter dashboards by name"),
+    page: external_exports.number().optional().default(1).describe("Page number to fetch, 1-based (default 1)"),
+    page_size: external_exports.number().optional().default(20).describe("Number of dashboards per page, 1-100 (default 20)")
   },
   { readOnlyHint: true },
   async ({ search, page, page_size }) => {
@@ -42888,9 +42894,9 @@ server.tool(
 );
 server.tool(
   "get_dashboard",
-  "Get dashboard details including widgets and visualizations.",
+  "Get a dashboard's full layout. Behavior: returns the dashboard's id, name, slug, and every widget, each with its linked visualization (id, name, type) and the query behind it (id, name). Usage: find the dashboard id or slug with list_dashboards; use the returned visualization/query ids to understand or extend the dashboard with add_widget.",
   {
-    dashboard_id_or_slug: external_exports.string().describe("Dashboard ID or slug (from list_dashboards)")
+    dashboard_id_or_slug: external_exports.string().describe("Dashboard ID or slug to fetch (from list_dashboards)")
   },
   { readOnlyHint: true },
   async ({ dashboard_id_or_slug }) => {
@@ -42916,9 +42922,9 @@ server.tool(
 );
 server.tool(
   "create_dashboard",
-  "Create a new dashboard.",
+  "Create a new, empty dashboard. Behavior: creates the dashboard and returns its id, name, and slug. Usage: after creating it, populate it with charts using add_widget, passing visualization ids obtained from get_query. To list or inspect existing dashboards instead, use list_dashboards / get_dashboard.",
   {
-    name: external_exports.string().describe("Dashboard name")
+    name: external_exports.string().describe("Display name for the new dashboard")
   },
   { destructiveHint: true },
   async ({ name }) => {
@@ -42942,12 +42948,12 @@ server.tool(
 );
 server.tool(
   "add_widget",
-  "Add a visualization widget to a dashboard. Get visualization_id from get_query.",
+  "Add a saved query's visualization onto a dashboard as a widget. Behavior: places the widget and returns its id and dashboard_id. Usage: get the dashboard_id from list_dashboards or create_dashboard, and the visualization_id from get_query (each saved query exposes its visualizations). This is how you build up a dashboard after creating it.",
   {
-    dashboard_id: external_exports.number().describe("Dashboard ID"),
-    visualization_id: external_exports.number().describe("Visualization ID (from get_query's visualizations)"),
-    text: external_exports.string().optional().default("").describe("Widget text"),
-    width: external_exports.union([external_exports.literal(1), external_exports.literal(2)]).optional().default(1).describe("Widget width (1 = half, 2 = full)")
+    dashboard_id: external_exports.number().describe("ID of the dashboard to add the widget to (from list_dashboards/create_dashboard)"),
+    visualization_id: external_exports.number().describe("ID of the visualization to embed (from get_query's visualizations list)"),
+    text: external_exports.string().optional().default("").describe("Optional text/markdown caption shown on the widget"),
+    width: external_exports.union([external_exports.literal(1), external_exports.literal(2)]).optional().default(1).describe("Widget width: 1 = half row, 2 = full row (default 1)")
   },
   { destructiveHint: true },
   async ({ dashboard_id, visualization_id, text, width }) => {
@@ -42977,7 +42983,7 @@ server.tool(
 );
 server.tool(
   "list_alerts",
-  "List alerts in Redash.",
+  "List all alerts configured in Redash. Behavior: returns an array where each alert has id, name, current state (ok / triggered / unknown), last_triggered_at, its linked query (id, name), and threshold options. Usage: use this to discover alert_ids, then call get_alert for one alert's full detail, or create_alert to add a new one.",
   {},
   { readOnlyHint: true },
   async () => {
@@ -43002,9 +43008,9 @@ server.tool(
 );
 server.tool(
   "get_alert",
-  "Get alert details (threshold, linked query, state).",
+  "Get the full detail of a single alert. Behavior: returns the alert's id, name, current state, last_triggered_at, threshold options (column, operator, value), and the query it monitors (id, name, description, data_source_id). Usage: find the alert_id with list_alerts.",
   {
-    alert_id: external_exports.number().describe("Alert ID (from list_alerts)")
+    alert_id: external_exports.number().describe("ID of the alert to inspect (from list_alerts)")
   },
   { readOnlyHint: true },
   async ({ alert_id }) => {
@@ -43033,14 +43039,14 @@ server.tool(
 );
 server.tool(
   "create_alert",
-  "Create a new alert. Triggers when a query result column crosses a threshold.",
+  "Create an alert that watches a saved query and fires when a chosen result column crosses a threshold (e.g., daily_signups less than 10). Behavior: creates the alert and returns its id and name. Usage: get the query_id from list_queries and confirm the exact column name with get_query / get_query_result first. The alert evaluates the query's latest result on Redash's schedule.",
   {
-    name: external_exports.string().describe("Alert name"),
-    query_id: external_exports.number().describe("Query ID to monitor"),
-    column: external_exports.string().describe("Column name to monitor"),
-    op: external_exports.enum(["greater than", "less than", "equals"]).describe("Comparison operator"),
-    value: external_exports.number().describe("Threshold value"),
-    rearm: external_exports.number().optional().default(0).describe("Rearm interval in seconds (0 = fire once)")
+    name: external_exports.string().describe("Display name for the alert"),
+    query_id: external_exports.number().describe("ID of the saved query whose results are monitored (from list_queries)"),
+    column: external_exports.string().describe("Name of the result column to compare against the threshold"),
+    op: external_exports.enum(["greater than", "less than", "equals"]).describe("Comparison operator between the column value and the threshold"),
+    value: external_exports.number().describe("Threshold value that triggers the alert when the comparison is true"),
+    rearm: external_exports.number().optional().default(0).describe("Seconds to wait before the alert can fire again; 0 means fire only once until manually reset (default 0)")
   },
   { destructiveHint: true },
   async ({ name, query_id, column, op, value, rearm }) => {

package/glama.json

@@ -0,0 +1,6 @@
+{
+  "$schema": "https://glama.ai/mcp/schemas/server.json",
+  "maintainers": [
+    "seob717"
+  ]
+}

package/manifest.json

@@ -1,7 +1,7 @@
 {
   "manifest_version": "0.3",
   "name": "redash-mcp",
-  "version": "3.1.5",
+  "version": "3.1.6",
   "description": "MCP server for Redash -- query data, manage dashboards, and run SQL with natural language. 24 tools including BIRD SQL methodology.",
   "long_description": "Connects an MCP client to a Redash instance: list data sources, inspect schemas, run SQL, manage saved queries / dashboards / alerts, and use BIRD SQL helpers (smart_query, keyword maps, few-shot examples, feedback, evaluation). Built-in SQL safety guards flag PII access and expensive scans; safety mode can be tuned per install. **Third-party data flow:** if you also set ANTHROPIC_API_KEY in the shell environment, the BIRD smart_query tool may send table-name lists (never query results or row data) to the Anthropic API as a fallback for table selection. Leave ANTHROPIC_API_KEY unset to disable this entirely.",
   "icon": "icon.png",

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "redash-mcp",
   "mcpName": "io.github.seob717/redash-mcp",
-  "version": "3.1.5",
+  "version": "3.1.6",
   "description": "MCP server that connects Redash to Claude AI — query data, manage dashboards, and run SQL with natural language, with built-in SQL safety guards.",
   "license": "MIT",
   "author": "seob717",