Azure MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| list-role-assignmentsC | List role assignments for the subscription or resource group |
| get-role-definitionsC | List available role definitions |
| get-user-permissionsC | Get detailed user permissions by combining role assignments and role definitions |
| run-azure-codeC | Run Azure code |
| list-tenantsB | List all available Azure tenants |
| select-tenantC | Select Azure tenant and subscription |
| list-resource-groupsB | List all resource groups in the selected subscription |
| get-resource-detailsC | Get detailed information about a specific resource |
| create-resource-groupC | Create a new resource group |
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 9 tools
Most tools have distinct purposes targeting different Azure resources (resource groups, roles, tenants, code execution), but 'get-resource-details' is ambiguous—it could overlap with other specific getters if not clarified. The descriptions help differentiate, but this one tool creates minor confusion.
Tools mostly follow a consistent verb_noun pattern (e.g., create-resource-group, list-resource-groups, get-role-definitions), with all using kebab-case. However, 'run-azure-code' deviates slightly by including 'azure' in the noun, breaking the pure resource-focused naming seen elsewhere.
With 9 tools, this server is well-scoped for Azure management, covering core areas like resource groups, roles, tenants, and code execution. Each tool earns its place by addressing a specific aspect of Azure operations without being overly broad or sparse.
The toolset provides good coverage for Azure management, including CRUD-like operations (create/list for resource groups) and key administrative functions (roles, tenants). Minor gaps exist, such as missing update/delete for resource groups or more granular resource operations, but agents can likely work around these for common workflows.