Kusto MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KUSTO_CLI_PATH | No | Path to Kusto.Cli.dll | Auto-detected |
| KUSTO_MAX_ROWS | No | Default max rows | 10000 |
| KUSTO_DEFAULT_TIMEOUT | No | Default query timeout (ms) | 60000 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kusto_queryC | Execute a KQL (Kusto Query Language) query against an Azure Data Explorer cluster. This is the primary tool for running queries. |
| kusto_executeA | Execute advanced Kusto commands with full CLI options. Use this for control commands, multiple statements, or when you need fine-grained control. |
| kusto_scriptC | Execute a Kusto script file containing multiple KQL statements. Useful for running saved queries or batch operations. |
| kusto_connection_addB | Add or update a named connection configuration for Azure Data Explorer. |
| kusto_connection_listA | List all configured Kusto connections. |
| kusto_connection_testB | Test connectivity to a Kusto cluster using a saved connection. |
| kusto_connection_removeB | Remove a saved connection configuration. |
| kusto_connection_set_defaultC | Set a connection as the default. |
| kusto_schemaA | Get database schema information including tables, columns, and their types. |
| kusto_helpB | Get help information about the Kusto CLI and available options. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
All tools are clearly distinct: connection management (add, list, remove, set_default, test), query execution (query, execute, script), schema retrieval, and help. No overlapping purposes.
All tools follow a consistent 'kusto_verb_noun' pattern using snake_case, making it easy to predict tool names and understand their roles.
10 tools is appropriate for a database query server, covering connection management, query execution, scripting, schema, and help without being excessive or insufficient.
Core workflows are covered (connection CRUD, query, script, schema, help). Missing explicit update for connections (though add serves upsert) and possibly a dedicated list-databases tool, but schema provides that info.