Summary

The first question about any Azure estate — which tenant, which subscription — answered in chat.

It covers the navigation layer rather than the whole Azure surface: which tenants you can see, what is in them, what is running in a resource group. Because it never holds a credential of its own, whatever you can reach with `az login` is exactly what the agent can reach.

What it is

An MCP server that connects Claude Desktop to Azure Resource Management, so tenants, subscriptions and the resources under them can be listed and inspected in conversation. Authentication runs through DefaultAzureCredential, which tries environment variables, managed identity, Azure CLI, Visual Studio Code and interactive browser in turn until one works.

What you get

Tenant and subscription discovery — ask which Azure accounts and subscriptions are reachable, then pick one with the `select-tenant` tool
Resource queries through the Azure Resource Management client — resource groups, virtual machines in a group, and similar reads
Transient failures are retried rather than surfaced as a dead end, and responses come back formatted for the chat window

Requirements

Node.js (v18 or higher), Claude Desktop, and an Azure account with the right permissions. Clone the repo, `npm install`, then register the launcher in `claude_desktop_config.json`. Sign in with `az login`, or set service-principal environment variables. Package version 0.0.4.

Setup effort

One command — npx -y @modelcontextprotocol/server-sequential-thinking