-
licenseNot graded
qualityC
maintenanceAn MCP server that exposes Azure resource management tools, allowing AI assistants to list resource groups, list resources in a group, and retrieve subscription information.
-
Azure Infrastructure MCP Server
Related Servers
Alternatives to Azure Infrastructure MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceAn MCP server that exposes 41 Azure DevOps tools to AI assistants, enabling management of pipelines, repositories, pull requests, releases, work items, test management, and wikis through natural language.41MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides Azure DevOps integration for AI assistants, enabling them to list projects, run pipelines, analyze failures, view logs, and troubleshoot builds directly from chat interfaces.MIT
- AlicenseAqualityBmaintenanceMCP server for Azure resource management, AI Foundry, and Entra ID — inspect and operate Azure infrastructure through AI agents.3MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI assistants to manage Azure DevOps resources including Work Items, Git repositories, pipelines, and user identities.11 npmMIT
- FlicenseBqualityDmaintenanceAn MCP server that enables AI assistants to interact with Azure DevOps projects, work items, repositories, pipelines, wikis, and more via 21 tools.21-
TDQS
B3/5.0
Scored across 99 tools
Disambiguation4/5
Tools are largely disambiguated by service-specific prefixes (aad_, acr_, webapp_, etc.), making it clear which service each tool targets. However, some generic tools like 'get_system_metrics' and 'check_service_health' could overlap with each other or with service-specific health tools, causing occasional ambiguity.
Naming Consistency3/5
Most tools follow a 'prefix_verb_noun' pattern (e.g., aad_create_user), but there are inconsistencies: some tools lack a prefix (list_vms, auth_status), verbs vary (list, show, get, view), and some names are not verb-noun (billing_budgets, account_clear). This mixed pattern reduces predictability.
Tool Count2/5
With 99 tools, the server is overly expansive, covering many small operations that could be combined (e.g., multiple subnet tools, separate list/show for nearly every resource). The large surface makes it harder for agents to select the right tool and increases cognitive load without clear benefit.
Completeness3/5
The server covers many Azure services (AAD, ACR, App Configuration, App Service, networking, RBAC), but has notable gaps: no tools for VM creation/deletion, storage account creation, or SQL databases. While core workflows for some services (e.g., ACR) are complete, missing fundamental operations in others limit overall coverage.
Maintenance
ActivityInactive
ResponsivenessNo issues