Azure / Azure/bicep

MCP Server Tool for getting schema for modules

Open
#18,918 0 comments 1 reaction 0 assignees View on GitHub
enhancement story: bicep MCP
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

**Is your feature request related to a problem? Please describe.**
With Bicep MCP Server we have tool for getting schema for Azure resource types. It will be good if there is a tool to get schema for module. Modules are either defined in bicepparam file with using statement or as modules in bicep file. When the module is located in Container registry or as template spec these modules are downloaded (cached) locally in a well known locations. When you have modules you can have schema (via user defined data types) and these schemas can be complex as for actual resources. The tool can get the schema and feed it to the agent. With such tool you can have the following scenario: Create empty bicepparam file and just define the using statement pointing to module in container registry. Let's say the module deploys storage account in resource group. Ask the agent to get he schema for the module and create your configuration for storage account with all security settings enabled. The tool in this case will find where the module was downloaded locally, read its schema and feed it to the agent. The agent will know the schema and provide valid configuration based on the parameters available in that schema.

Additionally would be good if there is a tool that can get the available Bicep modules from container registry.

**Describe the solution you'd like**
described.

Contributor guide

Open the contributing guide

Research direction

Start with the existing Bicep MCP Server tool for Azure resource schemas and trace how locally cached Container Registry and template-spec modules are found. Define the inputs and outputs for retrieving a module schema and discovering available registry modules, including modules referenced by bicepparam using statements and Bicep files. Done means an agent can retrieve a module's schema and enumerate available modules.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.