Azure Data Explorer MCP Server

Created By
cheng306a year ago
Overview

what is Azure Data Explorer MCP Server?

Azure Data Explorer MCP Server is a Model Context Protocol (MCP) server that allows users to log in to Azure Data Explorer and execute KQL (Kusto Query Language) queries.

how to use Azure Data Explorer MCP Server?

To use the MCP server, clone the repository, install the dependencies, build the project, and start the server. Then, configure your MCP client (like Claude for Desktop) to connect to this server.

key features of Azure Data Explorer MCP Server?

  • Login to Azure Data Explorer using service principal credentials.
  • Execute KQL queries against an Azure Data Explorer database.
  • View formatted results of the executed queries.

use cases of Azure Data Explorer MCP Server?

  1. Running data analysis queries on Azure Data Explorer databases.
  2. Integrating with applications that require data querying capabilities.
  3. Automating data retrieval processes in cloud applications.

FAQ from Azure Data Explorer MCP Server?

  • What are the prerequisites for using the MCP server?

You need Node.js (v16 or higher), npm (v7 or higher), an Azure Data Explorer cluster, and a service principal with access.

  • How do I run a KQL query?

Use the run-adx-query tool with the desired KQL query as a parameter.

  • Can I run the server in development mode?

Yes, you can run the server in development mode using the command npm run dev.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
cheng306
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago