QueryMind

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

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
80%
Naming quality
83%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~1,695Tokens (tool definitions)
~681 BTypical response size
Moderate attention impact (1.32% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

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

What it can do

Tool inventory

Tools (13)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢capabilities

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

Input Schema

{
  "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.

Input Schema

{
  "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.

Input Schema

{
  "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.

Input Schema

{
  "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.

Input Schema

{
  "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.

Input Schema

{
  "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.

Input Schema

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

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

Input Schema

{
  "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.

Input Schema

{
  "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.

Input Schema

{
  "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.

Input Schema

{
  "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.

Input Schema

{
  "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.

Input Schema

{
  "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
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded13 tools