QueryMind

Read-only answers from your business database, with the SQL and conditions behind each number.

使うべきか

品質と安全性

A
説明の品質
100%
スキーマの完全性
80%
命名の品質
83%
ポイズニングのリスク
100%
権限の一致
100%
プロトコルへの準拠
100%

ツール定義とプロトコルへの準拠に関する自動分析に基づいています。

コンテキストコスト

~1,695トークン数(ツール定義)
~681 B一般的なレスポンスサイズ
注意への影響は中程度(128k コンテキストの 1.32%)

これは、サーバーのツールがモデルのコンテキストに読み込まれるたびに消費されるおおよそのトークン数です。数が多いほど、ほかのタスクに使える注意が減ります。

インストール

ワンクリックインストール

これを `claude_desktop_config.json` ファイルに追加してください:

{
  "mcpServers": {
    "connect": {
      "url": "https://querymind.co.kr/mcp"
    }
  }
}

リモートエンドポイント

https://querymind.co.kr/mcpstreamable-http

できること

ツール一覧

ツール(13)

🟢 読み取り専用🟡 書き込み🔴 削除⚪ 不明
🟢capabilities

Describe the connected data source, access limits and setup status. Before sign-in, returns public connection guidance only.

入力スキーマ

{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
🟡ask(question)

Send a natural-language question to the analysis engine. Reads business data without modifying it, but creates QueryMind query jobs, audit records, conversation context and usage records. Returns an answer, state, limited result rows and evidence. If state=clarifying_question, ask the user the returned question before calling clarify.

入力スキーマ

{
  "type": "object",
  "properties": {
    "question": {
      "type": "string",
      "description": "The user's natural-language data question; preserve their business meaning."
    }
  },
  "required": [
    "question"
  ],
  "additionalProperties": false
}
🟡clarify(choice)

Continue the previous ask after the engine requests clarification. May create a QueryMind query job and update audit records, conversation context and usage records; business data remains read-only. Send the user's choice or additional explanation; do not invent their choice.

入力スキーマ

{
  "type": "object",
  "properties": {
    "choice": {
      "type": "string",
      "description": "The user's choice or additional explanation."
    }
  },
  "required": [
    "choice"
  ],
  "additionalProperties": false
}
🟢result(job_id)

Retrieve the answer, state, limited result rows and evidence for the job_id returned by ask or clarify with state=pending. Completing retrieval can record QueryMind usage; business data remains read-only.

入力スキーマ

{
  "type": "object",
  "properties": {
    "job_id": {
      "type": "integer",
      "description": "The job_id returned by ask or clarify."
    }
  },
  "required": [
    "job_id"
  ],
  "additionalProperties": false
}
🟢explain(audit_id)

Show the data source, query conditions (SQL), time basis and access restrictions for a recent answer accessible to this connection.

入力スキーマ

{
  "type": "object",
  "properties": {
    "audit_id": {
      "type": "integer",
      "description": "Omit to explain the most recent ask answer."
    }
  },
  "additionalProperties": false
}
🟡connect_database(kind, name)

Create a secure setup link for the user's business database. Show the link to the user. Credentials must be entered there, never in chat. The link expires in 10 minutes and is single-use. Use a read-only database account.

入力スキーマ

{
  "type": "object",
  "properties": {
    "kind": {
      "type": "string",
      "description": "postgres, mysql, mssql or oracle; omit if unknown."
    },
    "name": {
      "type": "string",
      "description": "Optional display name for this database."
    }
  },
  "required": [],
  "additionalProperties": false
}
🟢onboard

Start a durable job to learn the connected database structure. Reuses a running job for the same database. Check onboarding_status; candidates requiring approval are handled with review.

入力スキーマ

{
  "type": "object",
  "properties": {},
  "required": [],
  "additionalProperties": false
}
🟢onboarding_status(job_id)

Return onboarding stage, status and next steps, with question examples when available.

入力スキーマ

{
  "type": "object",
  "properties": {
    "job_id": {
      "type": "string",
      "description": "Omit for the most recent onboarding job for the current database."
    }
  },
  "required": [],
  "additionalProperties": false
}
🟡define(term, definition, preview, confirm_token, undo_def_id, ...)

Propose a business definition for this user's questions only. First send term and definition, then show the preview to the user. Send confirm_token only after their explicit confirmation. Use undo_def_id to undo or list=true to list definitions.

入力スキーマ

{
  "type": "object",
  "properties": {
    "term": {
      "type": "string",
      "description": "Business term to define."
    },
    "definition": {
      "type": "string",
      "description": "The user's intended business definition."
    },
    "preview": {
      "type": "boolean",
      "description": "Defaults to true."
    },
    "confirm_token": {
      "type": "string",
      "description": "Token from a preview explicitly approved by the user."
    },
    "undo_def_id": {
      "type": "string",
      "description": "ID of a personal definition to undo."
    },
    "list": {
      "type": "boolean",
      "description": "Set true to list personal definitions."
    }
  },
  "required": [],
  "additionalProperties": false
}
🟢review(action, candidate_ids)

List or propose approval/rejection of onboarding candidates (table labels, joins, code dictionaries). An administrator must confirm changes through a secure reauthentication link.

入力スキーマ

{
  "type": "object",
  "properties": {
    "action": {
      "type": "string",
      "enum": [
        "list",
        "approve",
        "dismiss"
      ],
      "description": "list, approve or dismiss."
    },
    "candidate_ids": {
      "type": "array",
      "items": {
        "type": "integer"
      },
      "description": "Candidate IDs returned by list."
    }
  },
  "required": [],
  "additionalProperties": false
}
🔴set_access_rule(role, table, predicate, description)

Propose which rows a role can access. Changes take effect only after an administrator reauthenticates and confirms through a secure link, never through chat alone.

入力スキーマ

{
  "type": "object",
  "properties": {
    "role": {
      "type": "string",
      "enum": [
        "viewer",
        "analyst",
        "admin"
      ],
      "description": "Role affected by the rule."
    },
    "table": {
      "type": "string",
      "description": "Table to which the rule applies."
    },
    "predicate": {
      "type": "string",
      "description": "SQL WHERE condition, for example dept_id = 101."
    },
    "description": {
      "type": "string",
      "description": "Business explanation of the proposed rule."
    }
  },
  "required": [
    "role",
    "table",
    "predicate"
  ],
  "additionalProperties": false
}
🟢usage

Return this month's question usage, account limits and connected database count.

入力スキーマ

{
  "type": "object",
  "properties": {},
  "required": [],
  "additionalProperties": false
}
🟡invite(email, role)

Administrators can create a single-use invitation link valid for 24 hours. Share the link yourself; this tool does not send email. The recipient signs in or signs up through the link and uses the same connector address.

入力スキーマ

{
  "type": "object",
  "properties": {
    "email": {
      "type": "string",
      "description": "Recipient email, which becomes their login ID."
    },
    "role": {
      "type": "string",
      "enum": [
        "admin",
        "analyst",
        "viewer"
      ],
      "description": "Role in the organization; defaults to analyst."
    }
  },
  "required": [
    "email"
  ],
  "additionalProperties": false
}

コミュニティ

このサーバーを評価する

エビデンス

最近の観測

検証済みバージョンは記録されていませんツール 13 件