pab1it0/adx-mcp-server

A [Model Context Protocol][mcp] (MCP) server that enables AI assistants to execute KQL queries and explore Azure Data Explorer (ADX/Kusto) databases through standardized interfaces.
This server provides seamless access to Azure Data Explorer and Eventhouse (in Microsoft Fabric) clusters, allowing AI assistants to query and analyze your data using the powerful Kusto Query Language.
[mcp]: https://modelcontextprotocol.io
Features
Query Execution
- **Execute KQL queries** - Run arbitrary KQL queries against your ADX database
- **Structured results** - Get results formatted as JSON for easy consumption
Database Discovery
- **List tables** - Discover all tables in your database
- **View schemas** - Inspect table schemas and column types
- **Sample data** - Preview table contents with configurable sample sizes
- **Table statistics** - Get detailed metadata including row counts and storage size
Authentication
- **DefaultAzureCredential** - Supports Azure CLI, Managed Identity, and more
- **Workload Identity** - Native support for AKS workload identity
- **Flexible credentials** - Works with multiple Azure authentication methods
Deployment Options
- **Multiple transports** - stdio (default), HTTP, and Server-Sent Events (SSE)
- **Docker support** - Production-ready container images with security best practices
- **Dev Container** - Seamless development experience with GitHub Codespaces
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:
Azure Workload Identity Support
The server now uses WorkloadIdentityCredential by default when running in Azure Kubernetes Service (AKS) environments with workload identity configured. It prioritizes the use of WorkloadIdentityCredential whenever the necessary environment variables are present.
For AKS with Azure Workload Identity, you only need to:
1. Make sure the pod has AZURE_TENANT_ID and AZURE_CLIENT_ID environment variables set
2. Ensure the token file is mounted at the default path or specify a custom path with ADX_TOKEN_FILE_PATH
If these environment variables are not present, the server will automatically fall back to DefaultAzureCredential, which tries multiple authentication methods in sequence.
3. Add the server configuration to your client configuration file. For example, for Claude Desktop:
> Note: if you see Error: spawn uv ENOENT in Claude Desktop, you may need to specify the full path to uv or set the environment variable NO_UV=1 in the configuration.
Docker Usage
This project includes Docker support for easy deployment and isolation.
Building the Docker Image
Build the Docker image using:
Running with Docker
You can run the server using Docker in several ways:
Using docker run directly:
Using docker-compose:
Create a .env file with your Azure Data Explorer credentials and then run:
Running with Docker in Claude Desktop
To use the containerized server with Claude Desktop, update the configuration to use Docker with the environment variables: