This MCP (Model Context Protocol) server provides access to Azure Resource Graph queries, allowing you to retrieve information about Azure resources across your subscriptions. It leverages the Azure Resource Graph API to execute queries and return structured data about your Azure resources.
npm install
npm run build
Before using the server, ensure you have proper Azure authentication:
az login
The server uses DefaultAzureCredential which supports multiple authentication methods:
Set up your environment variables:
.env.example
to .env
AZURE_SUBSCRIPTION_ID
in your .env
file with your actual subscription IDAZURE_TENANT_ID
AZURE_CLIENT_ID
AZURE_CLIENT_SECRET
{
"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"
},
}
}
}
{
"mcp": {
"servers": {
"azure-resource-graph": {
"type": "stdio",
"command": "node",
"args": [
"C:\\YOUR_WORKSPACE\\azure-resource-graph-mcp-server\\build\\index.js"
],
"env": {
"SUBSCRIPTION_ID": "xxxxxx-xx-xx-xx-xxxxxx"
},
}
}
}
}
The server provides a tool called query-resources that retrieves resources and their details from Azure Resource Graph.
subscriptionId
(optional): Azure subscription ID (defaults to configured ID)query
(optional): Custom Resource Graph query (defaults to "Resources | project id, name, type, location")The default query returns basic resource information:
Resources | project id, name, type, location
You can customize queries to filter for specific resource types:
Resources
| where type =~ 'Microsoft.Compute/virtualMachines'
| project id, name, location, properties.hardwareProfile.vmSize
Or to find resources with specific tags:
Resources
| where tags.Environment == 'Production'
| project name, type, location, tags
The server includes error handling for:
If you encounter errors, verify your Azure authentication is working correctly and that your subscription ID is properly configured.
To add this MCP server to Claude Code, run this command in your terminal:
claude mcp add-json "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"}}'
See the official Claude Code MCP documentation for more details.
There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json
file so that it is available in all of your projects.
If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json
file.
To add a global MCP server go to Cursor Settings > Tools & Integrations and click "New MCP Server".
When you click that button the ~/.cursor/mcp.json
file will be opened and you can add your server like this:
{
"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"
}
}
}
}
To add an MCP server to a project you can create a new .cursor/mcp.json
file or add it to the existing one. This will look exactly the same as the global MCP server example above.
Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.
The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.
You can also explicitly ask the agent to use the tool by mentioning the tool name and describing what the function does.
To add this MCP server to Claude Desktop:
1. Find your configuration file:
~/Library/Application Support/Claude/claude_desktop_config.json
%APPDATA%\Claude\claude_desktop_config.json
~/.config/Claude/claude_desktop_config.json
2. Add this to your configuration file:
{
"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"
}
}
}
}
3. Restart Claude Desktop for the changes to take effect