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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago