Azure MCP Server

Add to your client

Copy the config for your MCP client and paste it into its config file.

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

Before you start

• Node.js LTS (20 or later) to run via npx — or .NET 10 (`dnx`) / `uv` (uvx) as alternative runtimes
• The Azure CLI installed and signed in with `az login`, or DefaultAzureCredential configured (managed identity / environment credentials)
• An Azure subscription with appropriate RBAC roles on the resources you want to access (e.g. Storage Blob Data Reader/Contributor for blob operations)

About Azure MCP Server

Tools & capabilities (7)

When to use it

• Use it when you want an agent to inspect Azure Storage — listing storage accounts, blob containers, and blobs — in natural language.
• Use it when you need to read a specific blob's properties or upload a local file into a container from your IDE.
• Use it when you're already working across many Azure services and want one MCP server that covers storage plus 40+ others.
• Use it when you want safe access via read-only mode and per-tool destructive annotations.
• Use it when you operate in a sovereign cloud (Azure China or US Government) and need MCP tooling that supports it.

Quick setup

1. 1Install Node.js LTS and the Azure CLI.
2. 2Sign in with `az login` (or configure DefaultAzureCredential / a managed identity).
3. 3Add the server to your MCP client with command `npx` and args `-y @azure/mcp@latest server start`.
4. 4Optionally enable read-only mode or scope which tool namespaces are exposed.
5. 5Restart the client and verify the Azure Storage tools appear, then try listing your storage accounts.

Azure MCP Server FAQ