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-tablesA | 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 7 tools
Most tools have clearly distinct purposes (connection, query execution, issue reporting). The singular/plural pairs show-tables vs show-table and show-function vs show-functions could cause momentary confusion, but descriptions clarify that the plural forms list and singular forms show details.
All tool names follow a consistent kebab-case verb_noun pattern (show-tables, execute-query, initialize-connection, report-issue, show-function, show-functions, show-table). The only variation is singular/plural, which reflects a meaningful semantic distinction rather than a naming inconsistency.
Seven tools is well-scoped for a Kusto/ADX query server: connection setup, query execution, table and function introspection, plus a feedback mechanism. Each tool earns its place without bloating the surface.
The core lifecycle for a read-only Kusto client is covered: connect, query, inspect tables and functions, and report issues. Minor gaps exist (e.g., no dedicated tool for listing databases or checking connection status), but these can be worked around via KQL queries.