kusto-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| initialize-connectionB | Creates connection to an ADX cluster |
| show-tables | List tables in the current database |
| show-tableB | Show the table schema columns |
| execute-queryA | Runs KQL queries and returns results. By default, limits results to 20 rows to prevent context overflow. Use the "limit" parameter to specify a different maximum. If results are marked as partial, consider revising your query to use aggregations, filters, or summarizations. |
| show-functionsB | List functions in the current database |
| show-functionA | Show details of a specific function, including its code and parameters |
| report-issueA | Report a bug or request a feature for kusto-mcp on GitHub. Returns a pre-filled GitHub issue link you open in your browser and submit under your own GitHub account — no GitHub token is used or stored, and no Kusto connection is required. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analyze-query-perf | Analyze KQL query performance by measuring scanned extents and totalCpu impact of each query part |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clearly distinct role: connection setup, schema inspection, query execution, function listing, function details, and issue reporting. The only close pair, show-functions vs show-function, is clearly separated by plural vs singular and explicit descriptions.
All tool names follow the same verb_noun hyphenated pattern: initialize, show, execute, and report. The show-functions/show-function pair is a consistent singular/plural distinction rather than a naming deviation.
Six tools is a well-scoped size for a Kusto/ADX read-only query server. Each tool contributes to connection, querying, schema/function inspection, or server support without significant redundancy.
Core querying and function inspection workflows are covered, but there is no way to list tables or databases, so an agent cannot discover available tables before running show-table or execute-query. This is a notable gap for a metadata/query server, though users can work around it if they already know object names.