Azure Data Explorer MCP Server
A Model Context Protocol (MCP) server for Azure Data Explorer.
This provides access to your Azure Data Explorer clusters and databases through standardized MCP interfaces, allowing AI assistants to execute KQL queries and explore your data.
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] Authentication support
- [x] Token credential support (Azure CLI, MSI, etc.)
-
[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
-
Login to your Azure account which has the permission to the ADX cluster using Azure CLI.
-
Configure the environment variables for your ADX cluster, either through a
.env
file or system environment variables:
1# Required: Azure Data Explorer configuration 2ADX_CLUSTER_URL=https://yourcluster.region.kusto.windows.net 3ADX_DATABASE=your_database
- Add the server configuration to your client configuration file. For example, for Claude Desktop:
1{ 2 "mcpServers": { 3 "adx": { 4 "command": "uv", 5 "args": [ 6 "--directory", 7 "<full path to adx-mcp-server directory>", 8 "run", 9 "src/adx_mcp_server/main.py" 10 ], 11 "env": { 12 "ADX_CLUSTER_URL": "https://yourcluster.region.kusto.windows.net", 13 "ADX_DATABASE": "your_database" 14 } 15 } 16 } 17}
Note: if you see
Error: spawn uv ENOENT
in Claude Desktop, you may need to specify the full path touv
or set the environment variableNO_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:
1docker build -t adx-mcp-server .
Running with Docker
You can run the server using Docker in several ways:
Using docker run directly:
1docker run -it --rm \ 2 -e ADX_CLUSTER_URL=https://yourcluster.region.kusto.windows.net \ 3 -e ADX_DATABASE=your_database \ 4 adx-mcp-server
Using docker-compose:
Create a .env
file with your Azure Data Explorer credentials and then run:
1docker-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:
1{ 2 "mcpServers": { 3 "adx": { 4 "command": "docker", 5 "args": [ 6 "run", 7 "--rm", 8 "-i", 9 "-e", "ADX_CLUSTER_URL", 10 "-e", "ADX_DATABASE", 11 "adx-mcp-server" 12 ], 13 "env": { 14 "ADX_CLUSTER_URL": "https://yourcluster.region.kusto.windows.net", 15 "ADX_DATABASE": "your_database" 16 } 17 } 18 } 19}
This configuration passes the environment variables from Claude Desktop to the Docker container by using the -e
flag with just the variable name, and providing the actual values in the env
object.
Development
Contributions are welcome! Please open an issue or submit a pull request if you have any suggestions or improvements.
This project uses uv
to manage dependencies. Install uv
following the instructions for your platform:
1curl -LsSf https://astral.sh/uv/install.sh | sh
You can then create a virtual environment and install the dependencies with:
1uv venv 2source .venv/bin/activate # On Unix/macOS 3.venv\Scripts\activate # On Windows 4uv pip install -e .
Project Structure
The project has been organized with a src
directory structure:
adx-mcp-server/
├── src/
│ └── adx_mcp_server/
│ ├── __init__.py # Package initialization
│ ├── server.py # MCP server implementation
│ ├── main.py # Main application logic
├── Dockerfile # Docker configuration
├── docker-compose.yml # Docker Compose configuration
├── .dockerignore # Docker ignore file
├── pyproject.toml # Project configuration
└── README.md # This file
Testing
The project includes a comprehensive test suite that ensures functionality and helps prevent regressions.
Run the tests with pytest:
1# Install development dependencies 2uv pip install -e ".[dev]" 3 4# Run the tests 5pytest 6 7# Run with coverage report 8pytest --cov=src --cov-report=term-missing
Tests are organized into:
- Configuration validation tests
- Server functionality tests
- Error handling tests
- Main application tests
When adding new features, please also add corresponding tests.
Tools
| Tool | Category | Description |
| --- | --- | --- |
| execute_query
| Query | Execute a KQL query against Azure Data Explorer |
| list_tables
| Discovery | List all tables in the configured database |
| get_table_schema
| Discovery | Get the schema for a specific table |
| sample_table_data
| Discovery | Get sample data from a table with optional sample size |
License
MIT