kusto-mcp
Related Servers
Alternatives to kusto-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables intelligent KQL query execution against Azure Data Explorer clusters with AI-powered schema caching and natural language to KQL conversion. Provides automated schema discovery and context-aware query assistance for enhanced data exploration.121 PyPI23MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to query and analyze data in Azure Data Explorer, Log Analytics, and Microsoft Sentinel using Kusto Query Language (KQL) through tools, resources, and prompts.6MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to execute KQL queries against Azure Data Explorer and explore database resources like tables and schemas.MIT
- AlicenseAqualityDmaintenanceAI assistants to query and analyze Azure Data Explorer databases through standardized interfaces.558MIT

Microsoft Sentinel Dataofficial
AlicenseNot gradedqualityDmaintenanceEnables searching for relevant tables and retrieving data from Microsoft Sentinel's data lake using natural language, supporting security hunting scenarios like password-spray detection and impossible travel checks.1MIT- AlicenseNot gradedqualityDmaintenanceEnables users to authenticate with Azure Data Explorer and execute KQL queries via natural language through the Model Context Protocol.284 npmMIT
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.