Azure MCP Server

Microsoft's official Azure server, exposing Azure services such as Storage, Cosmos DB, Key Vault, Monitor and AKS as namespace tools. Runs locally through npx and signs in with your Azure CLI credentials.

Local (stdio)Credential

Set up Azure MCP Server

Configuration examples, not tested connections. Replace placeholders and review the upstream documentation before use.

Claude Code

Run in your terminal.

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

Cursor

Merge into ~/.cursor/mcp.json

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

Codex

Run in your terminal.

codex mcp add azure -- npx -y @azure/mcp@latest server start

Gemini CLI

Merge into ~/.gemini/settings.json

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

OpenCode

Merge into ~/.config/opencode/opencode.jsonc

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "azure": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@azure/mcp@latest",
        "server",
        "start"
      ],
      "enabled": true
    }
  }
}

VS Code

Merge into .vscode/mcp.json

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

Using more than one server?Add to a config with other servers

Step-by-step setup guides: Claude Code and Codex CLI, Cursor and VS Code. In Claude Desktop, the Cursor JSON goes in claude_desktop_config.json. This is a local server that runs on your machine; see remote vs local servers and authentication and security basics.

Overview

The Azure MCP Server is Microsoft's official server for Azure, now maintained in the microsoft/mcp repository. The older Azure/azure-mcp repository is archived. Builds ship often; version 3.0.0-beta.50 was published on 6 October 2026. It gives an agent one place to query and manage resources across many Azure services.

In its default namespace mode, each Azure service appears as a single tool that routes to individual operations. This keeps the tool count manageable for clients with limits. When we started the server on 11 October 2026, it listed tools such as storage, cosmos, keyvault, monitor, aks, sql and postgres, alongside subscription_list and group_list, plus helpers for Azure best practices and Bicep schemas. An all mode exposes every operation as its own tool, and a single mode exposes one routing tool.

The example runs npx -y @azure/mcp@latest server start over stdio, so you need Node.js LTS. The server does not take a key in its configuration. It uses your existing Azure sign-in, so run az login with the Azure CLI first. Everything the agent does runs with that identity's Azure role assignments. Use an account or subscription scoped to the work, especially before letting it run operations that create or delete resources.

Example tools

  • subscription_list
  • group_list
  • storage
  • cosmos
  • keyvault
  • monitor

Tool names are upstream examples. The server's live tool list can differ.

Browse Cloud servers

Sources

This page was written from the upstream documentation below and last reviewed on 11 October 2026. Listing is not a security or compatibility endorsement. Report a correction through the contact page.