CLOUD OPERATIONS / Microsoft
Azure MCP Server
Brings Azure service tools into one MCP server, with namespace selection and a read-only option for scoped use.
“All Azure MCP tools in a single server.”
01 / THE REASONING
Why this made the selection.
- Provides Azure-specific operations through one maintained implementation rather than unrelated adapters.
- Namespace and read-only options allow a smaller task-oriented tool surface.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- servers/Azure.Mcp.Server/README.md (installation, capability and permission sections)
- servers/Azure.Mcp.Server/src/Azure.Mcp.Server.csproj
- servers/Azure.Mcp.Server/src/Program.cs
- docs/Authentication.md
- LICENSE
Our findings
- Program.cs routes logs to stderr for stdio protocol use; the project manifest establishes the C# implementation.
- The authentication guide documents Azure CLI/developer credentials and other identity paths; authentication must precede tool use.
- The README’s Node.js block registers azure-mcp-server under mcpServers and launches npx -y @azure/mcp@latest server start.
- The README’s service sections include Microsoft Foundry, Azure Advisor, AI Search, App Service, Backup, Compute, Container Apps, Cosmos DB, Key Vault, AKS, Monitor, SQL Database, Storage and Terraform, among others.
- At this commit Program.cs comments out the Azure Data Manager for Energy area with the note “disabling for GA release”, while the README still lists ADME prompts. ADME tools were not established as registered. The csproj version is 4.0.0-beta.1 (3.0.0-beta.46 at the previous pin).
- The README’s VS Code extension settings expose azureMcp.serverMode (single, namespace by default, or all), azureMcp.enabledServices and azureMcp.readOnly, shown as false.
- Program.cs comments describe stdio and http transport modes, and the README’s Remote Setup self-hosts an HTTP endpoint through azd templates. Only the stdio client launch was reviewed here.
Not established by this review
- Server startup, authentication and tool execution were not tested.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
DOCUMENTED COMMAND
npx -y @azure/mcp@latest server start Copying does not execute this command. It may retrieve a newer version than the reviewed source.
- Authenticate to the intended Azure tenant/subscription using the official authentication guide.
- Select namespaces and enable read-only mode when the task is inspection.
Before you start
- Node.js for the launcher and an Azure identity with appropriate RBAC permissions.
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"azure-mcp-server": {
"command": "npx",
"args": [
"-y",
"@azure/mcp@latest",
"server",
"start"
]
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Official documentation ↗Checked
https://github.com/microsoft/mcp/blob/81ee5a8ba2a3406722f579f7b3895e5dbc78e09d/servers/Azure.Mcp.Server/README.md
Supports: summary, whySelected, bestFor, limitations, install, access, compatibility, transports, configExample, review
- Applicable source licence ↗Checked
https://github.com/microsoft/mcp/blob/81ee5a8ba2a3406722f579f7b3895e5dbc78e09d/LICENSE
Supports: license
https://github.com/microsoft/mcp/blob/81ee5a8ba2a3406722f579f7b3895e5dbc78e09d/servers/Azure.Mcp.Server/src/Azure.Mcp.Server.csproj
Supports: language, review
https://github.com/microsoft/mcp/blob/81ee5a8ba2a3406722f579f7b3895e5dbc78e09d/servers/Azure.Mcp.Server/src/Program.cs
Supports: language, review
https://github.com/microsoft/mcp/blob/81ee5a8ba2a3406722f579f7b3895e5dbc78e09d/docs/Authentication.md
Supports: language, review