select-tenantLABSCO 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-tenanttool - 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
Build from source — git clone https://github.com/kalivaraprasad-gonapa/azure-mcp.git
USE CASES
01
Working out which Azure account you are actually in
List the available tenants and subscriptions, then fix the session to the right one before asking anything else.
02
Looking over a resource group
Ask for the resource groups in a subscription and then the virtual machines inside the one you care about.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- Node.js 18 or later
- tsx on PATH (the Claude Desktop entry runs it)
- Azure CLI for az login (optional: service-principal environment variables work instead)
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/kalivaraprasad-gonapa/azure-mcp.git
cd azure-mcp
npm install
# sign in to Azure (or set service-principal environment variables)
az loginMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"azure": {
"command": "tsx",
"args": [
"C:/Users/<YOUR_USERNAME><YOUR_PATH_TO_AZURE_MCP>/src/launcher.ts"
]
}
}
}C:/Users/<YOUR_USERNAME><YOUR_PATH_TO_AZURE_MCP> is the full path of the folder you cloned. tsx has to be on your PATH. The entry runs it directly and npm install does not add it.
