Loading...
This MCP server provides read-only access to Azure Resource Graph, enabling querying and retrieval of Azure resource metadata across subscriptions.
Boost this tool
Subscribe to listing upgrades or segmented pushes.
This MCP server provides read-only access to Azure Resource Graph, enabling querying and retrieval of Azure resource metadata across subscriptions.
This MCP server is generally safe for querying Azure Resource Graph data. The primary risk lies in crafting queries that expose sensitive information, which is mitigated by proper Azure RBAC and credential management. Ensure users understand the scope of their permissions and avoid overly broad queries.
Performance depends on the complexity of the Resource Graph queries and the size of the Azure environment. Complex queries may take longer to execute. Consider optimizing queries for better performance.
Cost is primarily associated with Azure Resource Graph usage, which is generally low for simple queries but can increase with complex queries and large environments. Monitor Azure Resource Graph costs to avoid unexpected charges.
npm install
npm{
"mcpServers": {
"azure-resource-graph-mcp-server": {
"command": "node",
"args": [
"C:\\YOUR_WORKSPACE\\azure-resource-graph-mcp-server\\build\\index.js"
],
"env": {
"SUBSCRIPTION_ID": "xxxxxx-xx-xx-xx-xxxxxx"
},
}
}
}AZURE_SUBSCRIPTION_IDAZURE_TENANT_IDAZURE_CLIENT_IDAZURE_CLIENT_SECRETquery-resourcesRetrieves Azure resources and their details based on a Resource Graph query.
Read-only operation; retrieves resource metadata without modifying resources.
Environment Variable
hybrid
This MCP server is generally safe for querying Azure Resource Graph data. The primary risk lies in crafting queries that expose sensitive information, which is mitigated by proper Azure RBAC and credential management. Ensure users understand the scope of their permissions and avoid overly broad queries.
The server operates in read-only mode, limiting autonomy to data retrieval. No destructive actions are possible.
Production Tip
Monitor query performance and optimize queries to minimize latency and resource consumption in production environments.
The user needs Azure RBAC permissions to read resource metadata in the target subscriptions. The 'Reader' role is typically sufficient.
Pass the query as a parameter to the `query-resources` tool. Ensure the query is valid Kusto Query Language (KQL).
The server will return an error message indicating the reason for the failure, such as an invalid query or insufficient permissions.
Set the `SUBSCRIPTION_ID` environment variable to the desired Azure subscription ID.
Yes, but the server is configured for a single subscription via the `SUBSCRIPTION_ID` environment variable. To query across multiple subscriptions, you would need to modify the code to iterate through multiple subscription IDs.
No, the server does not cache the data. Each query retrieves the latest information from Azure Resource Graph.
Ensure proper Azure RBAC is configured to limit access to sensitive resource data. Use strong credentials and protect the `SUBSCRIPTION_ID` environment variable.