Microsoft 365 & Azure MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PORT | No | Port for SSE or OpenAPI mode. | 8001 |
| TENANTID | No | Alternative to GRAPH_APP_TENANT_ID (for backward compatibility). | |
| LOG_LEVEL | No | Logging level (DEBUG, INFO, WARNING, ERROR, CRITICAL). | INFO |
| CLIENT_SECRET | No | Alternative to GRAPH_APP_CLIENT_SECRET (for backward compatibility). | |
| MCP_TRANSPORT | No | Transport mode: stdio, sse, or openapi. | stdio |
| COMMAND_TIMEOUT | No | Timeout for Azure CLI commands in seconds. | 300 |
| OPERATION_TIMEOUT | No | Timeout for Graph API operations in seconds. | 300 |
| AZURE_APP_CLIENT_ID | No | Your service principal client ID for Azure CLI. | |
| AZURE_APP_TENANT_ID | No | Your Azure AD tenant ID for Azure CLI. | |
| GRAPH_APP_CLIENT_ID | No | Your app registration client ID for Microsoft Graph (read/write). | |
| GRAPH_APP_TENANT_ID | No | Your app registration tenant ID for Microsoft Graph. | |
| USE_APP_REG_CLIENTID | No | Alternative to GRAPH_APP_CLIENT_ID (for backward compatibility). | |
| AZURE_SUBSCRIPTION_ID | No | Your Azure subscription ID (optional). | |
| SHARE_APP_REGISTRATION | No | Use same app registration for Azure CLI and Graph API (true/false). | false |
| AZURE_APP_CLIENT_SECRET | No | Your service principal client secret for Azure CLI. | |
| GRAPH_APP_CLIENT_SECRET | No | Your app registration client secret for Microsoft Graph. | |
| MAX_CONCURRENT_COMMANDS | No | Maximum concurrent Azure CLI commands. | 5 |
| MAX_CONCURRENT_OPERATIONS | No | Maximum concurrent Graph API operations. | 5 |
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": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_azure_cli_commandB | Execute an Azure CLI command. Commands must begin with 'az' and are subject to the configured execution policy. |
| graph_commandA | Call a Microsoft Graph v1.0 endpoint with GET, POST, PUT, PATCH, or DELETE. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Azure CLI Help | Authentication, policy, and Azure CLI examples |
| Microsoft Graph Help | Authentication, policy, and Graph request examples |
TDQS
Scored across 2 tools
The two tools target completely different APIs: Azure CLI vs Microsoft Graph, with no overlap in functionality.
One uses a verb_noun pattern ('execute_azure_cli_command') while the other is just noun ('graph_command'), lacking a consistent action prefix.
Only 2 tools for a broad domain like Microsoft 365 & Azure is insufficient; the server feels skeletal and under-scoped.
The server lacks any domain-specific operations; generic command execution leaves massive gaps for any practical use.