MCP KQL Server

io.github.4R9UNPublished by GitHub account 4R9UNv2.1.5Updated Oct 24, 2026

Execute KQL in AI prompts via NL2KQL with schema discovery and Azure Data Explorer integration

VerifiedSTDIODesktop onlyDatabasesData & Analytics

Overview

AI-generated overview

A local MCP server that lets an assistant turn natural-language questions into KQL and run them against Azure Data Explorer, with schema discovery.

What you can do
Translate natural-language prompts into KQL queries for Azure Data Explorer, using schema discovery to ground the generated query in the available tables and columns. Execute the resulting KQL against the connected Azure Data Explorer resource. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Worth adding when you work with Azure Data Explorer and want an assistant to draft and run KQL queries from plain-language questions instead of writing the query syntax yourself.
Requirements
Runs as a local process installed from the PyPI package mcp-kql-server over stdio, so a Python environment is needed. It connects to Azure Data Explorer, which implies an accessible cluster and database plus Azure credentials, though the manifest declares no authentication method or environment variables.
Before you install
Queries are executed against a live Azure Data Explorer database, so generated KQL can read data and may be costly or slow on large tables; review queries before running them. The manifest declares no authentication details, so confirm how credentials are supplied and where query data is sent before installing.

Installation

In SourceWeft

  1. Open MCP KQL Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.1.5LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.