
Azure
io.github.asklokeshPublished by GitHub account asklokeshv0.1.0Updated Oct 24, 2026
MCP server for Azure API integration
Overview
Local MCP server that connects an assistant to Microsoft Azure cloud services through the Azure API.
- What you can do
- Connect an assistant to Microsoft Azure cloud services via the Azure API
- Reported to cover a broad range of Azure APIs, with rate limiting, retry logic and async support
- Authenticate with Azure using several supported methods
- Configure through environment variables or a .env file
- When to use it
- Worth considering when you want an assistant to work with Microsoft Azure resources from a desktop MCP client and you already have Azure service principal credentials to supply.
- Requirements
- Runs as a local process, installed from PyPI (azure-mcp-server) or from source with pip; the manifest suggests running it with uvx. Requires the environment variables AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_SUBSCRIPTION_ID and AZURE_TENANT_ID, plus network access to Azure. Desktop client only.
Installation
In SourceWeft
- Open Azure in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Azure MCP Server
Azure Mcp Server
[GitHub stars] [GitHub forks] [GitHub watchers]
A Model Context Protocol (MCP) server for integrating Azure with GenAI applications.
Overview
Microsoft Azure cloud services integration
Features
- Comprehensive Azure API coverage
- Multiple authentication methods
- Enterprise-ready with rate limiting
- Full error handling and retry logic
- Async support for better performance
Installation
Or install from source:
Configuration
Create a .env file or set environment variables according to Azure API requirements.
Quick Start
License
MIT License - see LICENSE file for details
Source: README.md at commit 136c13a
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.