zzzhdw

Provides access to ADX clusters via MCP tools to list tables, run queries, and fetch schemas.

typescript

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "mcp-mirror-zzzhdw_mcp-server-kusto": {
      "command": "uv",
      "args": [
        "--directory",
        "{{PATH_TO_PROJECT}}\\\\mcp-server-kusto\\\\src\\\\mcp_server_kusto",
        "run",
        "mcp-server-kusto",
        "--cluster",
        "{{ADX_CLUSTER_URL}}",
        "--authority_id",
        "{{TENANT_ID}}",
        "--client_id",
        "{{CLIENT_ID}}",
        "--client_secret",
        "{{CLIENT_SECRET}}"
      ]
    }
  }
}

This MCP server gives you programmatic access to Azure Data Explorer (ADX) clusters from your MCP client. It exposes a set of practical tools to list metadata, run queries against internal and external tables, and retrieve schemas, enabling you to build data-driven applications and dashboards against your ADX data sources.

How to use

Connect your MCP client to the Kusto MCP Server to interact with ADX clusters. You can run the following tools to explore the cluster and retrieve data and schemas.

list_internal_tables: list all internal tables in the cluster.
list_external_tables: list all external tables in the cluster.
list_materialized_views: list all materialized views in the cluster.
execute_query_internal_table: execute a query on an internal table or materialized view.
execute_query_external_table: execute a query on an external table.
get_internal_table_schema: get the schema of an internal table or materialized view.
get_external_table_schema: get the schema of an external table.

How to install

Prerequisites: you need the MCP runtime available on your system (the runtime used here is uv). Ensure you have access to your ADX cluster URL and, if you are not using a local emulator, the appropriate Azure AD credentials.

Create the MCP server configuration in your client by adding the MCP server entry for the Kusto server.
Start the MCP server using the provided command snippet.
Connect your MCP client to the server and begin issuing tool calls against the cluster.

Additional notes

If you are running against a local azure data explorer emulator, use the cluster URL like https://localhost:8082. In that case, you do not need to provide authority_id, client_id, or client_secret.

The following configuration snippet shows how to set up the MCP server in your Claude Desktop client. Use your actual project paths and cluster URL in place of placeholders.

Available tools

list_internal_tables

Lists all internal tables in the connected ADX cluster.

list_external_tables

Lists all external tables in the connected ADX cluster.

list_materialized_views

Lists all materialized views in the connected ADX cluster.

execute_query_internal_table

Executes a query against an internal table or materialized view in the connected ADX cluster.

execute_query_external_table

Executes a query against an external table in the connected ADX cluster.

get_internal_table_schema

Retrieves the schema for an internal table or materialized view.

get_external_table_schema

Retrieves the schema for an external table in the connected ADX cluster.

Built by

VeilStrat

AI signals for GTM teams