MCP server · Cloud and DevOps

Azure MCP server

Lets an assistant work with more than 45 Azure services, from Storage and Key Vault to AKS, Cosmos DB and Monitor, using your Azure sign-in.

Maintainer: Microsoft (official)
Licence: MIT
Runs: Locally (npx)
Sign-in: OAuth sign-in in the app
Registry version: 3.0.0-beta.48 (updated 2026-09-30)
Last activity: 2026-10-14
Source: github.com/microsoft/mcp Official docs

Overview

What it does

The Azure MCP Server is Microsoft’s single server for Azure. It runs locally over stdio and authenticates through the Azure Identity SDK, so it uses whatever you are already signed in with, such as the Azure CLI, and never stores tokens itself. It is published on npm (@azure/mcp, Node.js 22 or newer), NuGet and PyPI, and as a Docker image and MCPB bundle. Claude Code users can install it through the azure plugin in the official plugin marketplace.

Tools cover more than 45 Azure service areas, including Microsoft Foundry, AI Search, App Service, Compute, Container Apps, Container Registry, Cosmos DB, PostgreSQL, Event Grid, Event Hubs, Key Vault, AKS, Monitor and Storage, plus best-practice guidance and Azure CLI command generation. By default tools are grouped by service namespace. Start options let you expose all tools, a single tool, or only chosen namespaces, and a --read-only flag blocks write operations.

Tools

What the assistant can do

Storage, Key Vault and App Configuration operations
Compute, App Service, Container Apps and AKS management
Cosmos DB, Azure Database for PostgreSQL and Data Explorer queries
Azure Monitor and Insights logs and metrics
Microsoft Foundry model and deployment management
Azure best-practice guidance and Azure CLI command generation

Install

Install Azure MCP server in your app

You need:

Node.js 22 or newer
An Azure account, signed in with the Azure CLI, Azure PowerShell or another Azure Identity method

Run in your project. --scope local keeps the servers private to you in this project; use user for every project.

Terminal

claude mcp add --scope local azure -- npx -y @azure/mcp@latest server start

Native Windows (PowerShell)

claude mcp add --scope local azure -- cmd /c npx -y '@azure/mcp@latest' server start

Project root. Commit it to share the servers with your team; each person sets the variables in their own shell.

.mcp.json

{
  "mcpServers": {
    "azure": {
      "command": "npx",
      "args": [
        "-y",
        "@azure/mcp@latest",
        "server",
        "start"
      ]
    }
  }
}

On native Windows (not WSL), the reference servers’ READMEs start npx through `cmd /c`: if a server won’t start, use "command": "cmd" with "args": ["/c", "npx", …].

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json (Settings → Developer → Edit Config). Restart Claude after saving.

claude_desktop_config.json

{
  "mcpServers": {
    "azure": {
      "command": "npx",
      "args": [
        "-y",
        "@azure/mcp@latest",
        "server",
        "start"
      ]
    }
  }
}

In your project, or ~/.cursor/mcp.json for every project.

mcp.json

{
  "mcpServers": {
    "azure": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@azure/mcp@latest",
        "server",
        "start"
      ]
    }
  }
}

In your workspace. VS Code asks for each secret the first time a server starts and stores it securely.

mcp.json

{
  "servers": {
    "azure": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@azure/mcp@latest",
        "server",
        "start"
      ]
    }
  }
}

macOS/Linux: ~/.config/devin/mcp_config.json · Windows: %APPDATA%\devin\mcp_config.json. Read by the default Devin Local agent and by the legacy Cascade agent.

mcp_config.json

{
  "mcpServers": {
    "azure": {
      "command": "npx",
      "args": [
        "-y",
        "@azure/mcp@latest",
        "server",
        "start"
      ]
    }
  }
}

Want it alongside other servers? Open Azure MCP Server in the MCP config generator and add the rest; it writes one file per app. The snippets follow the setup in the server’s README, checked on 2026-10-14.

Before you install

Tools act with your Azure RBAC permissions and can create, change or delete resources; Microsoft advises least-privilege roles.
Add --read-only to the server start arguments to block write operations, and --namespace to expose only the services you need.
A local MCP server runs with your user account’s permissions. Install it only from the source linked above. See how to choose a safe server.

Why it’s listed

Why we list it

Microsoft’s own, very actively developed server with the broadest Azure coverage and a documented read-only mode.

All MCP servers MCP config generator Guide: MCP servers in Claude Code Guide: what is MCP?

What it does

What the assistant can do

Install Azure MCP server in your app

Before you install

Why we list it

More MCP servers