Azure Logs MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port | 3000 |
| NODE_ENV | No | Set to 'development' for debug logging | production |
| LOG_LEVEL | No | Override default log level (0=ERROR, 1=WARN, 2=INFO, 3=DEBUG) | |
| CORS_ORIGIN | No | Allowed CORS origins | * |
| TRANSPORT_MODE | No | 'sse' or 'stdio' | sse |
| AZURE_CLIENT_ID | Yes | Application (client) ID from your Service Principal | |
| AZURE_TENANT_ID | Yes | Directory (tenant) ID from your Azure AD | |
| AZURE_CLIENT_SECRET | Yes | Client secret value you created | |
| AZURE_MONITOR_WORKSPACE_ID | Yes | Workspace ID from your Application Insights resource |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| getRequestLogsByOrderNumberB | Retrieves request logs from Azure Application Insights by order number. Searches through request logs containing the order number in name, URL, or custom dimensions. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name follows a clear verb_noun pattern (getRequestLogsByOrderNumber).
One tool is too few for a server named 'Azure Logs MCP', which suggests a broader scope for interacting with Azure logs. This limits functionality to a single, specific query type, making the server feel incomplete for general log management.
The server is severely incomplete for its implied domain of Azure logs. It only supports retrieving logs by order number, with no tools for other common operations like querying by time range, filtering by other criteria, or managing log data.