Kusto MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| cluster | No | URL of the Azure Data Explorer (ADX) cluster | |
| client_id | No | Client ID for Azure authentication | |
| authority_id | No | Tenant ID for Azure authentication | |
| client_secret | No | Client secret for Azure authentication |
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_internal_tablesC | List all internal tables in the database |
| list_external_tablesC | List all external tables in the database |
| list_materialized_viewsC | List all materialized views in the database |
| execute_query_internal_tableC | Execute a kql query to internal table or materialized view |
| execute_query_external_tableC | Execute a kql query to external table |
| retrieve_internal_table_schemaC | Get the schema of a table or materialized view |
| retrieve_external_table_schemaC | Get the schema of an external table |
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 7 tools
Tools are mostly distinct with separate verbs for listing, querying, and schema retrieval. However, execute_query_internal_table includes materialized views, slightly overlapping with the listing tools.
All tool names follow a consistent verb_noun pattern in snake_case, such as execute_query, list_, retrieve_. No mixing of styles.
With 7 tools, the set is well-scoped for a focused Kusto query server, covering essential operations without unnecessary bloat.
The set covers querying, listing, and schema retrieval for tables and views. Minor gaps include no tools for database-level listing or management operations, but the read-only focus seems intentional.