Azure Data Explorer (Kusto)
About
Integrates with Azure Data Explorer to enable listing databases, retrieving table schemas, and executing KQL queries for data analysis and exploration.
Details
- Author
- abhirockzz
- Repository
- abhirockzz/mcp_kusto
- GitHub stars
- 1
- Categories
- Developer Tools, AI, Database, Infrastructure, Security, Cloud Service
Jump to
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
Azure Data Explorer (Kusto)Command (node, npx, python, etc.)enter path to binary e.g. /Users/demo/Desktop/mcp_kustoPlease refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
This will differ based on the MCP client/tool you use. For VS Code you can follow these instructions on how to configure this server using a mcp.json file.
Here is an example of the mcp.json file:
{
"servers": {
"Kusto MCP server": {
"type": "stdio",
"command": "enter path to binary e.g. /Users/demo/Desktop/mcp_kusto",
"args": []
},
//other MCP servers...
}
}
Here is an example of Claude Desktop configuration:
{
"mcpServers": {
"Kusto MCP server": {
"command": "enter path to binary e.g. /Users/demo/Desktop/mcp_kusto",
"args": []
},
//other MCP servers...
}
}
- The user principal you use should have permissions required for .show databases, .show table, .show tables, and execute queries on the database. Refer to the documentation for Azure Data Explorer for more details.
- Authentication (Local credentials) - To keep things secure and simple, the MCP server uses DefaultAzureCredential. This approach looks in the environment variables for an application service principal or at locally installed developer tools, such as the Azure CLI, for a set of developer credentials. Either approach can be used to authenticate the MCP server to Azure Data Explorer. For example, just login locally using Azure CLI (az login).
You are good to go! Now spin up VS Code, Claude Desktop, or any other MCP tool and start vibe querying your Azure Data Explorer (Kusto) cluster!
list_databases
Lists all databases in a specific Azure Data Explorer cluster.
list_tables
Lists all tables in a specific Azure Data Explorer database.
get_table_schema
Gets the schema of a specific table in an Azure Data Explorer database.
execute_query
Executes a read-only KQL query against a database.
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"azure data explorer (kusto)": {
"cwd": "mcp_kusto",
"env": {},
"args": [],
"command": "enter path to binary e.g. /Users/demo/Desktop/mcp_kusto"
}
}
}Linux
{
"cwd": "mcp_kusto",
"env": [],
"args": [],
"command": "enter path to binary e.g. /Users/demo/Desktop/mcp_kusto"
}Macos
{
"cwd": "mcp_kusto",
"env": [],
"args": [],
"command": "enter path to binary e.g. /Users/demo/Desktop/mcp_kusto"
}Windows
{
"cwd": "mcp_kusto",
"env": [],
"args": [],
"command": "enter path to binary e.g. /Users/demo/Desktop/mcp_kusto"
}Vibe querying with MCP server for Azure Data Explorer (Kusto)
This is an implementation of an MCP server for Azure Data Explorer (Kusto) built using its Go SDK. You can use this with VS Code (or other MCP tools) for making data analysis and exploration easier.
It exposes tools for interacting with Azure Data Explorer:
1. list_databases - Lists all databases in a specific Azure Data Explorer cluster.
2. list_tables - Lists all tables in a specific Azure Data Explorer database.
3. get_table_schema - Gets the schema of a specific table in an Azure Data Explorer database.
4. execute_query - Executes a read-only KQL query against a database.
> Word(s) of caution: As much as I want folks to benefit from this, I have to call out that Large Language Models (LLMs) are non-deterministic by nature and can make mistakes. I would recommend you to always validate the results and queries before making any decisions based on them.
Here is a sneak peek:
How to run
git clone https://github.com/abhirockzz/mcp_kusto
cd mcp_kusto
go build -o mcp_kusto main.go
Configure the MCP server
This will differ based on the MCP client/tool you use. For VS Code you can follow these instructions on how to configure this server using a mcp.json file.
Here is an example of the mcp.json file:
{
"servers": {
"Kusto MCP server": {
"type": "stdio",
"command": "enter path to binary e.g. /Users/demo/Desktop/mcp_kusto",
"args": []
},
//other MCP servers...
}
}
Here is an example of Claude Desktop configuration:
{
"mcpServers": {
"Kusto MCP server": {
"command": "enter path to binary e.g. /Users/demo/Desktop/mcp_kusto",
"args": []
},
//other MCP servers...
}
}
Authentication
- The user principal you use should have permissions required for .show databases, .show table, .show tables, and execute queries on the database. Refer to the documentation for Azure Data Explorer for more details.
- Authentication (Local credentials) - To keep things secure and simple, the MCP server uses DefaultAzureCredential. This approach looks in the environment variables for an application service principal or at locally installed developer tools, such as the Azure CLI, for a set of developer credentials. Either approach can be used to authenticate the MCP server to Azure Data Explorer. For example, just login locally using Azure CLI (az login).
You are good to go! Now spin up VS Code, Claude Desktop, or any other MCP tool and start vibe querying your Azure Data Explorer (Kusto) cluster!
Local dev/testing
Start with MCP inspector - npx @modelcontextprotocol/inspector ./mcp_kusto
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
