Azure Data Explorer MCP Server

Name: Azure Data Explorer MCP Server
Author: pab1it0

@pab1it0

About Azure Data Explorer MCP Server

A Model Context Protocol (MCP) server that enables AI assistants to query and analyze Azure Data Explorer databases through standardized interfaces.

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "adx-mcp-server": {
      "command": "docker",
      "args": [
        "build",
        "-t",
        "adx-mcp-server",
        "."
      ]
    }
  }
}

Tools

Query

Discovery

Overview

What is Azure Data Explorer MCP Server?

An MCP server that enables AI assistants to execute KQL queries and explore Azure Data Explorer (ADX/Kusto) and Eventhouse databases through a standardized interface. It is for developers and analysts who want to query ADX clusters using AI-driven tools.

How to use Azure Data Explorer MCP Server?

Configure the required environment variables (ADX_CLUSTER_URL and ADX_DATABASE), log in to Azure via the Azure CLI, then add the server configuration to your MCP client (e.g., Claude Desktop). You can run it directly with uv, via Docker, or in a Dev Container.

Key features of Azure Data Explorer MCP Server

Execute arbitrary KQL queries and receive structured JSON results.
Discover tables, view schemas, sample data, and get table statistics.
Supports DefaultAzureCredential and Azure Workload Identity authentication.
Configurable transports: stdio, HTTP, and Server-Sent Events (SSE).
Docker images and Dev Container support for easy deployment.

Use cases of Azure Data Explorer MCP Server

AI assistants querying Azure Data Explorer databases on demand.
Automated data exploration and analysis through natural language.
Integrating ADX queries into MCP‑compatible clients like Claude Desktop.
Running ADX queries from CI/CD pipelines or containerized environments.

FAQ from Azure Data Explorer MCP Server

What authentication methods are supported?

The server uses DefaultAzureCredential by default and falls back to WorkloadIdentityCredential when the required environment variables are present (e.g., in AKS with workload identity).