Azure Data Explorer MCP Server

A Model Context Protocol (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.

Features

• Execute KQL queries against Azure Data Explorer
• Discover and explore database resources
• List tables in the configured database
• View table schemas
• Sample data from tables
• Get table statistics/details
• Authentication support
• Token credential support (Azure CLI, MSI, etc.)
• Workload Identity credential support for AKS
• Docker containerization support
• Provide interactive tools for AI assistants

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:

ADX_CLUSTER_URL=https://yourcluster.region.kusto.windows.net
ADX_DATABASE=your_database\n\n# Optional: Azure Workload Identity credentials\n\n# AZURE_TENANT_ID=your-tenant-id\n\n# AZURE_CLIENT_ID=your-client-id\n\n# ADX_TOKEN_FILE_PATH=/var/run/secrets/azure/tokens/azure-identity-token

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.

Docker Usage

This project includes Docker support for easy deployment and isolation.

Building the Docker Image

Build the Docker image using:

docker build -t adx-mcp-server .

Running with Docker

You can run the server using Docker in several ways:

Using docker run directly:

docker run -it --rm \
- e ADX_CLUSTER_URL=https://yourcluster.region.kusto.windows.net \
- e ADX_DATABASE=your_database \
- e AZURE_TENANT_ID=your_tenant_id \
- e AZURE_CLIENT_ID=your_client_id \
 adx-mcp-server

Using docker-compose:

Create a .env file with your Azure Data Explorer credentials and then run:

docker-compose up

Running with Docker in Claude Desktop

To use the containerized server with Claude Desktop, update the configuration to use Docker with the environment variables:

{
 "mcpServers": {
 "adx": {
 "command": "docker",
 "args": [ "run", "--rm", "-i", "-e", "ADX_CLUSTER_URL", "-e", "ADX_DATABASE", "-e", "AZURE_TENANT_ID", "-e", "AZURE_CLIENT_ID", "-e", "ADX_TOKEN_FILE_PATH", "adx-mcp-server" ],
 "env": {
 "ADX_CLUSTER_URL": "https://yourcluster.region.kusto.windows.net",
 "ADX_DATABASE": "your_database",
 "AZURE_TENANT_ID": "your_tenant_id",
 "AZURE_CLIENT_ID": "your_client_id",
 "ADX_TOKEN_FILE_PATH": "/var/run/secrets/azure/tokens/azure-identity-token"
 }
 }
 }
}

License

MIT