MCP server for Azure Data Explorer integration
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"adx-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Azure Data Explorer MCP Server <a href="https://glama.ai/mcp/servers/1yysyd147h"> <img width="380" height="200" src="https://glama.ai/mcp/servers/1yysyd147h/badge" /> </a> A [Model Context Protocol][mcp] (MCP) server for Azure Data Explorer/Eventhouse in Microsoft Fabric. This provides access to your Azure Data Explorer/Eventhouse clusters and databases through standardized MCP interfaces, allowing AI assistants to execute KQL queries and explore your data. [mcp]: https://modelcontextprotocol.io ## Features - [x] Execute KQL queries against Azure Data Explorer - [x] Discover and explore database resources - [x] List tables in the configured database - [x] View table schemas - [x] Sample data from tables - [x] Get table statistics/details - [x] Authentication support - [x] Token credential support (Azure CLI, MSI, etc.) - [x] Workload Identity credential support for AKS - [x] Docker containerization support - [x] Provide interactive tools for AI assistants The list of tools is configurable, so you can choose which tools you want to make available to the MCP client. This is useful if you don't use certain functionality or if you don't want to take up too much of the context window. ## Usage 1. Login to your Azure account which has the permission to the ADX cluster using Azure CLI. 2. Configure the environment variables for your ADX cluster, either through a `.env` file or system environment variables: ```env # Required: Azure Data Explorer configuration ADX_CLUSTER_URL=https://yourcluster.region.kusto.windows.net ADX_DATABASE=your_database # Optional: Azure Workload Identity credentials # AZURE_TENANT_ID=your-tenant-id # AZURE_CLIENT_ID=your-client-id # ADX_TOKEN_FILE_PATH=/var/run/secrets/azure/tokens/azure-identity-token # Optional: Custom MCP Server configuration ADX_MCP_SERVER_TRANSPORT=stdio # Choose between http/sse/stdio, default = stdio # Optional: Only relevant for non-stdio transports ADX_MCP_BIND_HOST=127.0.0.1 # default =…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.