The MCP server discovers and explores Azure Verified Modules from the Bicep Public Registry, providing a focused interface for navigating AVMs and their contextual metadata.
🛠️ Key Features
- Discover Azure Verified Modules (AVMs) via the Bicep Public Registry
- Explore module details and relationships through the MCP protocol
- Lightweight server optimizing for catalog-style exposition
🚀 Use Cases
- Cataloging AVMs for quick reference in developer dashboards
- Integrating AVM metadata into CI/CD or IaC tooling
- Browsing module descriptions, provenance, and availability
⚡ Developer Benefits
- Simple, standards-aligned server exposing AVM data
- Clear, scannable README excerpts and metadata for SEO indexing
- Reusable MCP protocol endpoints for module discovery
⚠️ Limitations
- Description and features derived from AVM registry metadata; may require registry access for full details
- Limited to modules present in the Bicep Public Registry as described by MCP server data