Best for
- Developers who write and deploy Azure resources with Bicep
- Teams that want support from the official Azure toolchain
- Users who prefer declaratively managing Azure infrastructure
B
Bicep MCP Server
Official
An MCP server for the Bicep language used to describe and deploy Azure resources
GitHub source repository ↗
51FMRS · D
Bicep MCP Server comes from Microsoft's official Azure Bicep repository with a clear purpose: providing MCP access for developers who deploy Azure resources with the Bicep declarative language. It is published as a NuGet package over stdio transport. The source does not list specific tools, permissions, or authentication details, so installation guidance must come from official channels. It suits Azure infrastructure-as-code users and is not aimed at non-Azure scenarios.
Bicep MCP Server comes from Microsoft's official Azure Bicep repository and ships alongside the Bicep project. Bicep is a declarative infrastructure-as-code (IaC) language for describing and deploying Azure resources. The MCP server is distributed as the NuGet package Azure.Bicep.McpServer and communicates over stdio transport. It targets developers who want to work with Bicep templates and Azure resource deployment from an MCP client. Note that the source material only provides the server manifest and repository documentation; it does not list specific tools, authentication methods, or client compatibility details.
Setup
The source material does not include a client configuration example, so an exact install configuration cannot be provided. The manifest shows the server is published as the NuGet package Azure.Bicep.McpServer, with a runtime hint of dnx and stdio transport, and no environment variables declared. Refer to the official repository and NuGet page for the latest instructions.
Fit and risk
Not for
- Use cases unrelated to Azure or infrastructure as code
- Users who need support for non-Azure cloud providers
- Users expecting Bicep to replace a general-purpose programming language for arbitrary tasks
Required permissions
- The source material does not declare any specific permissions or environment variables requested by this server
Risks and side effects
- The manifest version is the placeholder 0.0.0-placeholder, so the concrete release and behavior may change
- Authentication method and permission scope are not described in the source, so the real blast radius of deployment actions must be verified independently
- Running a NuGet package via dnx introduces a dependency on the upstream package, so source and version trustworthiness matters
Troubleshooting
- Confirm the client connects using stdio transport
- Verify that the Azure.Bicep.McpServer version is available on NuGet
- Confirm the runtime environment supports the dnx runtime hint
- If problems persist, consult the official repository https://github.com/Azure/bicep and its issue tracker
Use cases
Working on Bicep template tasks from an MCP client
Assisting Azure-oriented declarative infrastructure-as-code workflows
Scenarios related to migrating or converting between ARM templates and Bicep
Supported clients
Claude DesktopFull support