Adx MCP Server

Adx MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. 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.

What the assistant can call

Once Adx is connected, these are the calls the assistant has available:

• execute_query — Query
• list_tables — Discovery
• get_table_schema — Discovery
• sample_table_data — Discovery
• get_table_details — Discovery
• Authentication — The Authentication tool exposed by this server
• Testing — The project includes a comprehensive test suite that ensures functionality and helps prevent regressions
• Logging — The Logging tool exposed by this server

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Configuration and credentials

You will need 8 environment variables: ADX_CLUSTER_URL, ADX_DATABASE, AZURE_TENANT_ID, AZURE_CLIENT_ID, ADX_TOKEN_FILE_PATH, ADX_MCP_SERVER_TRANSPORT, ADX_MCP_BIND_HOST, ADX_MCP_BIND_PORT. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

This sits in the cloud and infrastructure group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Adx's toolset — execute_query, list_tables, get_table_schema and 5 more — is a fair guide to whether it matches your workflow. It is maintained by pab1it0; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the adx mcp server does with a few real requests.