A
licenseNot graded
qualityD
maintenanceAn MCP server that exposes core Azure services as read-mostly tools any MCP client can call, including Blob Storage, Key Vault, Service Bus, and Resource Manager.
1
MIT
azure-utils-mcp
by BrianDeacon
Related Servers
Alternatives to azure-utils-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for Azure Cosmos DB enabling listing accounts, databases, containers, running SQL queries, and reading/writing/deleting documents.10MIT
- AlicenseBqualityCmaintenanceAn MCP server for managing Azure infrastructure from AI assistants, supporting subscriptions, VMs, storage, networking, identity, and more through natural language commands.992MIT
- FlicenseNot gradedqualityDmaintenanceMCP server that provides tools to interact with Azure DevOps, including querying work items, repositories, pull requests, builds, commits, and creating work items via a standardized interface.-
- AlicenseNot gradedqualityBmaintenanceMCP server that enables AI assistants to manage Azure DevOps resources including Work Items, Git repositories, pipelines, and user identities.15MIT
- 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
A3.9/5.0
Scored across 31 tools
Disambiguation5/5
Tools are clearly disambiguated by service prefix (authorization_, cosmosdb_, servicebus_) and distinct verbs. Even similar operations like peek across different targets (queue, subscription, DLQ) are precisely named, leaving no ambiguity.
Naming Consistency5/5
All tools follow a consistent pattern: service_verb_noun (e.g., cosmosdb_list_databases, servicebus_send_batch). The naming is uniform across all three services, making it predictable for agents.
Tool Count3/5
31 tools is high but justifiable given coverage of three distinct Azure services. However, the PIM portion only has 2 tools, which feels thin compared to the 11 for Cosmos DB and 18 for Service Bus, indicating slight over-scoping on the latter.
Completeness4/5
Cosmos DB covers essential operations (list, read, write, query, delete) with container info and count; Service Bus covers listing, peeking (with file variants for large payloads), purging, requeueing, and sending. Missing: ability to consume/receive messages from Service Bus (only peek), but that may be by design to avoid destructive operations. Minor gap but overall solid.
Maintenance
ActivityInactive
ResponsivenessNo issues