Skip to directory

Azure MCP

Microsoft

stdio (local); remote HTTP for separately self-hosted deployments4+ documented tools18

About Azure MCP

Microsoft's Azure MCP Server lets AI clients inspect and manage Azure resources using Azure service tools and the caller's Azure identity and role permissions.

What you can use it for

  • Discover Azure resources and configurations
  • Query Azure Monitor data and service-specific information
  • Deploy and manage resources when granted sufficient RBAC roles
  • Use Azure Developer CLI, Azure SQL, Cosmos DB, Storage, and other documented service tools
Connection and setup
Hosting
Local package-based stdio; separately documented self-hosted remote deployments
Transport
stdio (local); remote HTTP for separately self-hosted deployments
Endpoint
Local process; no hosted endpoint documented
Authentication
Microsoft Entra ID via Azure Identity credential chain. The server can discover credentials from Azure CLI, Azure Developer CLI, Visual Studio, or VS Code. The user needs Azure RBAC permissions for target resources.

Requirements

  • Azure account and active subscription
  • Node.js LTS or .NET 10/package runner depending on chosen installation
  • Azure CLI/Developer CLI/IDE sign-in or another documented Entra credential
  • GitHub Copilot subscription for the documented Copilot host workflow; other compatible MCP clients may impose separate requirements

Setup steps

  1. Add the local stdio server using the official package command. Microsoft documents npm: `npx -y @azure/mcp@latest server start` (NuGet is also available as `dnx Azure.Mcp ... azmcp server start`).
  2. Authenticate locally with `az login` or another supported Azure developer tool; check the intended account/subscription with `az account show`.
  3. Grant only the RBAC roles required for the specific resources. Do not store Azure passwords or tokens in MCP config.
  4. Enable Azure MCP tools in the host if tools are disabled by default, then review each requested action/permission prompt.
  5. Verify with a read-only request such as listing resource groups before attempting modifications.
Tools 4+

Microsoft documents a broad and evolving service catalog. Namespace, server mode, tool filters, local requirements, identity and RBAC shape availability. Stored identifiers are exact documented examples rather than a complete inventory.

  • azmcp_storage_account_get
    01
  • azmcp_storage_container_get
    02
  • azmcp_subscription_list
    03
  • azmcp_group_list
    04

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Limitations and notes
  • Tool availability reflects active host configuration, subscription permissions, installed optional tools, and Azure roles.
  • The server can modify or deploy Azure resources. Review tool calls and consent prompts; begin in read-only mode.
  • Sensitive responses such as Key Vault secrets may trigger user consent/elicitation.
  • Do not confuse the Microsoft Azure MCP Server with community wrappers or the separately hosted Azure DevOps server.
Original sources
  • official tool reference

    Microsoft documents a very large service catalog. Startup mode, namespace and tool filters, local execution, Azure identity and RBAC affect which operations can be called; these four rows are examples, not the full Azure inventory.

  • official documentation or source

    Microsoft documents a very large service catalog. Startup mode, namespace and tool filters, local execution, Azure identity and RBAC affect which operations can be called; these four rows are examples, not the full Azure inventory.

Documentation checked 2026-10-28T12:38:00.000Z. Connection has not been runtime tested.

Similar tools