kusto-mcp
Related Servers
Alternatives to kusto-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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.84 PyPI24MIT
- 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.559MIT

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.425 npmMIT
TDQS
Scored across 7 tools
The set contains two near-homographic pairs (show-function/show-functions and show-table/show-tables) that differ by a single character, which is a real misselection hazard for an agent. Descriptions do clarify the distinction (detail with code/parameters vs. list), and execute-query vs. show-* is clearly separated, so boundaries are recoverable but not crisp.
All names use kebab-case with a leading verb (initialize-, show-, execute-, report-), which is predictable and readable. The only deviation is the singular/plural suffix convention used to encode detail-vs-list, which is consistent as a rule but collides visually with the base names.
Seven tools is well within the ideal range and each one maps to a distinct step in a Kusto workflow: connect, discover tables/functions, inspect schema, run queries, and report issues. Nothing feels redundant or padded.
The query lifecycle is covered, but the surface lacks database-level discovery (no show-databases) and connection management (no list/switch connection or change-database), even though show-tables/show-functions are scoped to the 'current database'. There is also no way to inspect a function definition's siblings or sample table data other than writing a query, which agents can work around but may stumble on.