azure-query-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AZURE_CLIENT_ID | No | Azure client (application) ID for service principal authentication. | |
| AZURE_TENANT_ID | No | Microsoft Entra tenant ID to use for authentication. Also used when authenticating via Azure CLI. | |
| AZURE_CLIENT_SECRET | No | Azure client secret for service principal authentication. Avoid placing directly in committed MCP configuration; use the host's secret store or managed identity. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_workspacesA | List Azure Log Analytics workspaces accessible in a subscription. |
| search_tablesA | List or search tables in a Log Analytics workspace using ARM metadata. |
| describe_tableA | Get the canonical schema and retention metadata for a Log Analytics table. |
| query_workspaceA | Use for telemetry, logs, events, metrics, and time-series data stored in a Log Analytics workspace. Run bounded, read-only KQL against one workspace. Do not use for Azure resource inventory or configuration; use query_azure_resources for those. |
| query_azure_resourcesA | Use for Azure resource inventory, configuration, tags, policy, health, and cross-subscription discovery through Azure Resource Graph. Do not use for telemetry, logs, events, or time-series analysis; use query_workspace for those. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: workspace discovery, table exploration, schema inspection, Log Analytics queries, and Resource Graph queries. The two query tools explicitly cross-reference each other to prevent confusion.
All tool names follow a consistent verb_noun pattern (list_workspaces, search_tables, describe_table, query_workspace, query_azure_resources), making the API predictable and easy to navigate.
Five tools is well-scoped for an Azure query-oriented MCP server. Each tool addresses a necessary step in the workflow without bloat or redundancy.
The server covers the full lifecycle of querying Azure: discovering workspaces, exploring tables, understanding schemas, and running both telemetry and resource queries. No obvious gaps exist for its intended use case.