Demo

What is Demo?

Demo is a Model Context Protocol (MCP) server that provides access to Azure Resource Graph queries. It allows you to retrieve information about Azure resources across your subscriptions using Resource Graph queries. It is intended for developers working with Azure who want to query resources through MCP‑compatible tools like Cursor IDE or VS Code.

How to use Demo?

Clone the repository, run npm install && npm run build, then configure the server in your IDE’s MCP settings. Set the SUBSCRIPTION_ID environment variable (and optionally AZURE_TENANT_ID, AZURE_CLIENT_ID, AZURE_CLIENT_SECRET). The server exposes one tool, query-resources, which accepts an optional subscriptionId and a query parameter (default: Resources | project id, name, type, location).

Key features of Demo

• Query Azure resources using Resource Graph queries
• Default query returns resource ID, name, type, and location
• Supports custom Resource Graph queries
• Uses Azure DefaultAzureCredential for authentication

Use cases of Demo

• Retrieve a list of all resources across Azure subscriptions
• Run custom Resource Graph queries from an MCP client
• Integrate Azure resource discovery into AI‑assisted workflows

FAQ from Demo

What are the prerequisites to use Demo?

You need Node.js installed, an Azure subscription, and the Azure CLI (or other credentials supported by DefaultAzureCredential).

How does Demo authenticate with Azure?

It uses Azure DefaultAzureCredential, which supports Azure CLI login, Managed Identity, Visual Studio Code credentials, and environment variables.

What environment variables are required?

The key environment variable is SUBSCRIPTION_ID. Optional ones are AZURE_TENANT_ID, AZURE_CLIENT_ID, and AZURE_CLIENT_SECRET.

What transport does Demo use?

Demo uses stdio transport, configured in the IDE’s MCP settings with a command of node and the path to the built index.js.

What license is Demo released under?

MIT License.