Azure Log Analytics MCP Server

Created By
MananShahTRa year ago
MCP server for querying Azure Log Analytics using natural language
Overview

what is Azure Log Analytics MCP Server?

Azure Log Analytics MCP Server is a Model Context Protocol server designed to query Azure Log Analytics using natural language, allowing users to convert their queries into Kusto Query Language (KQL) and execute them seamlessly.

how to use Azure Log Analytics MCP Server?

To use the server, clone the repository, install the dependencies, and run it either as a CLI tool or an MCP server by providing your Anthropic API key and Azure credentials.

key features of Azure Log Analytics MCP Server?

  • Converts natural language queries to KQL using Claude AI.
  • Executes KQL queries against Azure Log Analytics.
  • Formats results for easy consumption by large language models (LLMs).
  • Supports both CLI mode and MCP server mode for integrations.

use cases of Azure Log Analytics MCP Server?

  1. Querying Azure Log Analytics for specific log data using natural language.
  2. Integrating with LLMs for enhanced data analysis and reporting.
  3. Simplifying log queries for users unfamiliar with KQL.

FAQ from Azure Log Analytics MCP Server?

  • What are the prerequisites for using the server?

You need Node.js 18.x or higher, an Azure subscription with a Log Analytics workspace, an Anthropic API key for Claude AI, and Azure CLI configured with appropriate credentials.

  • Is there a specific way to run the server?

Yes, you can run it as a CLI tool or as an MCP server by using the provided commands in the documentation.

  • Can I customize the queries?

Yes, you can customize your natural language queries to retrieve specific log data as needed.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MananShahTR
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.

21 hours ago