MCP Kusto

🚀 Vibe Queries with MCP Server and Azure Data Explorer (Kusto)

This is an implementation of an MCP server built for Azure Data Explorer (Kusto) using its Go SDK. You can use it with VS Code (or other MCP tools) to simplify data analysis and exploration.

It offers the following functions to interact with Azure Data Explorer:

1. list_databases - List all databases in a specific Azure Data Explorer cluster.
2. list_tables - List all tables in a specific Azure Data Explorer database.
3. get_table_schema - Get the schema information of a specific table.
4. execute_query - Execute a read - only KQL query against a database.

⚠️ Important Note

Although I hope everyone can benefit from this, it must be noted that large language models (LLMs) are inherently non - deterministic and may produce errors. I strongly recommend always validating before basing results or queries on them.

Here is a demonstration of its functionality:

🚀 Quick Start

Installation

git clone https://github.com/abhirockzz/mcp_kusto
cd mcp_kusto

go build -o mcp_kusto main.go

Configure the MCP Server

The configuration varies depending on the MCP client/tool you are using. For VS Code, you can follow these instructions to configure it using an mcp.json file.

Here is an example of the mcp.json file:

{
  "servers": {
    "Kusto MCP Server": {
      "type": "stdio",
      "command": "Enter the path to the executable file, e.g., /Users/demo/Desktop/mcp_kusto",
      "args": []
    },
    // Other MCP servers...
  }
}

Here is an example of the Claude Desktop configuration:

{
  "mcpServers": {
    "Kusto MCP Server": {
      "command": "Enter the path to the executable file, e.g., /Users/demo/Desktop/mcp_kusto",
      "args": []
    },
    // Other MCP servers...
  }
}

Authentication

• The user principal used must have permissions for .show databases, .show table, .show tables, and query execution operations on the database. For more details, refer to the Azure Data Explorer documentation.
• Authentication (local credentials) - To keep it secure and simple, the MCP server uses DefaultAzureCredential. This method looks for application service principal settings in environment variables or a set of developer credentials in locally installed development tools such as the Azure CLI. Both methods can be used to authenticate the MCP server to Azure Data Explorer. For example, simply log in locally using the Azure CLI (az login).

You're all set! Now start VS Code, Claude Desktop, or any other MCP tool and start exploring your Azure Data Explorer (Kusto) cluster!

🔧 Local Development/Testing

Start from MCP inspector - npx @modelcontextprotocol/inspector ./mcp_kusto