M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
B

Bicep MCP Server

Official
An MCP server for the Bicep language used to describe and deploy Azure resources
How to install ↓ Compare GitHub source repository ↗
Category
Dev Tools #243 of 438
Stars
★ 3.7k Very popular
Transport
stdio (local process)
Runtime
.NET
Credentials
No credential needed
License
MIT
Last commit
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.

Strongest · Maintenance 16/20 Weakest · Reliability 8/20

Reliability
8/20
Security and permissions
9/20
Maintenance
16/20
Documentation
9/20
Setup experience
9/20
Why each score
Reliability 8/20
Static review is limited to server.json and the README. The repository is a large, mature project and the README shows CI badges for build.yml and test-azure-cli-integration.yml, indicating continuous build and testing, but no tool list, init-handshake detail, or test evidence specific to the MCP server is provided. The version is '0.0.0-placeholder' for both the server and the package, so no real publishable version can be confirmed and manifest/implementation consistency is unverifiable. No committed source or tests under src/Bicep.McpServer were supplied as evidence; the static calibration caps reliability at 12, and the placeholder versions plus unverifiable tool behavior lower it further.
Security and permissions 9/20
No malware, credential theft, covert exfiltration, or unconfirmed destructive default was found; the manifest declares an empty environmentVariables array, requires no injected tokens, and uses local stdio transport, so the network surface is small. However, the evidence does not establish the tools' actual privilege boundaries, whether any deploy or write operations exist, whether dangerous operations require explicit confirmation, or any data-flow disclosure. Missing evidence is itself a deduction, so this sits moderately above mid-range but well below full marks.
Maintenance 16/20
Clear MIT license (except a few SVG icons), maintained by Microsoft/Azure with public issue tracking, a GitHub project, community calls, and contribution guidelines; README shows active CI badges and a large open-issue count (1060), consistent with a long-lived maintained project. Deductions: the manifest carries placeholder 0.0.0 versions and the publication/versioning path for the MCP subpackage is not evidenced, so release cadence and dependency-update policy cannot be confirmed.
Documentation 9/20
The README documents the Bicep language itself well (getting started, migration, modules, community resources), but there is essentially no MCP-server-specific documentation: no client install command, no tool list or parameter descriptions, no auth/permission requirements, no limits, and no troubleshooting. The manifest description is only 'Bicep MCP Server' with registryType nuget and runtimeHint dnx, and no example configuration. There is no reviewable correspondence between docs and the server's real capability, hence the deduction.
Setup experience 9/20
A potentially clear install path exists: a NuGet package Azure.Bicep.McpServer run over stdio via dnx would be only a few steps. But the version is a placeholder pointing at no real installable release, and the README gives no MCP client configuration example, runtime prerequisites, or platform-compatibility notes. The path is plausible but must be inferred and is manual/fragile; the static calibration keeps setup at or below 15, and the missing client examples and real version number lower it further.

Static review · not runListed 2026-09-18

Read the FMRS scoring method →

Fit and risk

What it can accessReads local files

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

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

Setup

Before you start

Runtime：.NET

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.

Check that it works

Connect the Bicep MCP Server in your MCP client and ask it to read a .bicep file and report its resource types; if the client can invoke the server's tools and returns correct results, the installation works.

Troubleshooting

  1. Confirm the client connects using stdio transport
  2. Verify that the Azure.Bicep.McpServer version is available on NuGet
  3. Confirm the runtime environment supports the dnx runtime hint
  4. If problems persist, consult the official repository https://github.com/Azure/bicep and its issue tracker

Things to try

Once connected, you can ask your AI assistant things like:

  • Check my main.bicep file for syntax or validation errors
  • Decompile this ARM template JSON into Bicep format
  • Explain the parameters and outputs of this Bicep module

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 Desktop

Listed from the project's documentation, not tested by this site.

Overview

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.

Similar servers

Context7 80 · B

Upstash's official server providing up-to-date third-party library docs for AI coding assistants

★ 64.1k · Tools 2 Compare with this →
Compare with other MCP servers

Source revision 986738365471 Data synced 2026-11-02 Read the FMRS scoring method