Skip to main content
Glama
Sign In
azure-query-mcp

azure-query-mcp

by kapetanios55
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to azure-query-mcp

No user-submitted related servers found.

    Related Servers

    • Generic Database MCP Server

      bleckcorp
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables read-only SQL querying and schema inspection across MSSQL, PostgreSQL, and MySQL databases via MCP tools.
      ISC

    • Purple AI MCP Server

      wojtekkura
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to SentinelOne's platform through MCP, allowing security investigations, threat hunting, and asset inventory queries via natural language.
      MIT

    • Claude Ops Investigator

      Randhir123
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only Kubernetes incident investigation through MCP tools for listing pods, describing resources, fetching logs, and searching runbooks.
      1
      -

    • entraid-mcp

      sedattavukcu
      F
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server for Microsoft Entra ID (Azure AD) that enables querying user sign-in logs, group memberships, and assigned Microsoft 365 licenses via Microsoft Graph API. Provides security and audit visibility without any write operations.
      -

    • BetterAzureMCP

      SH-G401
      A
      license
      A
      quality
      C
      maintenance
      Enables read-only debugging of Azure applications from GitHub Copilot, VS Code, and other MCP clients, with tools for resource health, changes, metrics, Application Insights telemetry, and logs for App Service, Container Apps, and AKS.
      20
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Tools are cleanly partitioned by intent, and the two most conflict-prone tools (query_workspace vs query_azure_resources) explicitly exclude each other's use cases in their descriptions. Incident tools (list vs get) and table tools (search_tables vs describe_table) are clearly separated, and entity_timeline is framed as a cross-source pivot rather than a generic query.

    Naming Consistency4/5

    Nearly all tools follow a verb_noun pattern (list_incidents, get_incident, run_hunting_query, check_ingestion_health, describe_table, search_tables). The lone deviation, entity_timeline, is a noun-only name but remains readable and unambiguous in context.

    Tool Count5/5

    Eleven tools is well within the ideal range for a security/telemetry server, and each maps to a distinct stage of the workflow (discovery, querying, schema introspection, incident triage, hunting, health checks). No tool appears redundant or filler.

    Completeness4/5

    The read-only surface covers workspace/table discovery, KQL querying, resource graph inventory, ingestion health, incident retrieval, entity timelines, and hunting queries with good lifecycle coherence. The main gap is incident write-back — the description says list_incidents is for finding incidents to triage, but there is no update_incident to assign, comment, or close one.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources