Azure Verified Modules (AVM) MCP Server
概览
MCP Server for discovering and exploring Azure Verified Modules (AVM) from the Bicep Public Registry. This MCP server enables AI agents and tools to search, discover, and retrieve detailed information about Azure Verified Modules (AVM) via the Model Context Protocol (MCP). It connects directly to the Microsoft Container Registry (MCR) and GitHub to provide up-to-date module information, versions, parameters, and usage examples. Azure Verified Modules (AVM) are a collection of standardized, validated, and well-documented Infrastructure as Code (IaC) modules for deploying Azure resources using Bicep.
README
以下为原文 README 节选，完整内容请查看原文。
🏗️ avm-mcp-server
MCP Server for discovering and exploring Azure Verified Modules (AVM) from the Bicep Public Registry.
🎯 Overview
This MCP server enables AI agents and tools to search, discover, and retrieve detailed information about Azure Verified Modules (AVM) via the Model Context Protocol (MCP). It connects directly to the Microsoft Container Registry (MCR) and GitHub to provide up-to-date module information, versions, parameters, and usage examples.
❓ Why AVM MCP Server?
Azure Verified Modules (AVM) are a collection of standardized, validated, and well-documented Infrastructure as Code (IaC) modules for deploying Azure resources using Bicep. However, discovering the right module and understanding its parameters can be challenging:
- Discovery Challenge: With hundreds of AVM modules available, finding the right module for your use case requires searching through documentation
- Parameter Complexity: Each module has numerous parameters with specific requirements and defaults
- Version Management: Keeping track of module versions and updates across the registry
- Documentation Access: Module documentation is scattered across GitHub repositories
This MCP server solves these challenges by:
- Providing fast, intelligent search across all AVM modules
- Retrieving module versions directly from the registry
- Extracting detailed parameter information and usage examples
- Enabling AI agents to help you find and use the right modules
Comparison with Microsoft Bicep MCP Server
Microsoft provides an official Bicep MCP Server that includes a ListAvmMetadata tool. So why create a separate AVM MCP Server?
Key Differences
| Feature | Microsoft Bicep MCP Server | AVM MCP Server (This Project) |
|---|---|---|
| Primary Focus | Bicep language tools & Azure resource schemas | AVM module discovery & documentation |
| AVM Module Search | Lists all modules (no filtering) | Intelligent search with multiple query formats |
| Module Details | Basic metadata (name, description, versions) | Deep documentation extraction (parameters, resource types, examples) |
| Installation | Requires .NET runtime & Bicep CLI | Lightweight Python with minimal dependencies |
| Response Format | Newline-separated text summary | Structured JSON with rich metadata |
| Documentation Access | External links only | Extracted and formatted markdown from module READMs |
Why This Server Exists
While the official Bicep MCP Server is excellent for authoring Bicep templates and accessing Azure resource type schemas, it provides limited functionality for discovering and understanding AVM modules:
安装
uvx --from git+https://github.com/stefanstranger/avm-mcp-server avm-mcp-server配置
{
"mcpServers": {
"avm-mcp-server": {
"type": "stdio",
"command": "uvx",
"args": [
"--from",
"git+https://github.com/stefanstranger/avm-mcp-server",
"avm-mcp-server"
]
}
}
}