Azure Resource Graph Query MCP Server

When this API is exposed as a tool via the Model Context Protocol (MCP) to an AI coding assistant like Claude Desktop, Cursor, or Cline, it transforms from a static reference into a dynamic, interactive engine for cloud infrastructure automation. The AI agent can leverage the MCP server to not only read documentation but to actively execute lifecycle management operations. This provides immense value by bridging the gap between natural language intent and precise API calls. For instance, a developer can instruct the AI to "find all my unattached managed disks in the production subscription and delete them," and the AI can translate this into a sequence: first, formulate and execute a Resource Graph query via the MCP tool to identify the specific resources based on a defined criteria, and then potentially trigger a separate action or provide the results for approval. This turns the AI into a cloud operations copilot, capable of performing complex inventory analysis and resource management tasks through conversation.

Practical workflows enabled by this integration are numerous and highly dynamic. A developer can instruct the AI agent to "query all resources that are missing the mandatory 'Environment' tag and generate a list of their owners for a cleanup campaign." The AI would use the MCP tool to run the appropriate Resource Graph query, parse the results, and present a structured report. Another example is, "Update my saved query named 'High-Cost-VMs' to now include metrics for CPU utilization over the last 7 days." The AI agent would retrieve the current query definition via the GET endpoint, modify the KQL syntax in the query body, and then use the PUT endpoint to persist the updated version. It can also manage query lifecycle by creating new saved queries for recurring tasks or deleting obsolete ones, fully automating what would otherwise be manual, repetitive portal or script-based operations.

Critical to the security and proper configuration of this API is the authentication mechanism. The listed endpoints operate under Azure Resource Manager (ARM) authentication, typically using Azure Active Directory (now Microsoft Entra ID) tokens. However, the description's mention of "None" likely refers to the authentication for the MCP server itself, not the underlying API calls. Developers must ensure the MCP server is configured with a robust identity, such as a managed identity or a service principal, with the principle of least privilege applied. This identity requires the "Microsoft.Authorization/roleAssignments/read" and appropriate resource provider permissions, and should be granted the "Reader" or a custom role with "Microsoft.ResourceGraph/queries/read" permissions at the relevant scope (subscription or resource group) for read operations. For create/update/delete operations, the "Contributor" role or a more granular custom role with write permissions will be necessary. All interactions must be conducted over secure, authenticated channels, and the MCP server's endpoint must be protected to prevent unauthorized access to these powerful cloud management capabilities.