Extract Azure.Bicep.McpServer.Core library to enable building custom remote MCP servers

[gary-x-li]

Description

Summary

This PR extracts shared Bicep MCP tool logic into a new Azure.Bicep.McpServer.Core NuGet library, enabling consumers to build their own remote MCP servers (e.g., with HTTP transport) without depending on the tool package or building from source. The existing stdio-based Azure.Bicep.McpServer tool remains unchanged for VS Code and local use.

Architecture

Project	Published as	Purpose
Bicep.McpServer.Core (new)	NuGet library (Azure.Bicep.McpServer.Core)	Shared SDK — AddBicepMcpServer(), tool classes, embedded resources
Bicep.McpServer (existing)	NuGet tool (Azure.Bicep.McpServer)	stdio entry point for VS Code / local use

Why a separate library?

The existing Azure.Bicep.McpServer is published as a NuGet tool (PackAsTool=true), which cannot be consumed as a library via PackageReference (NuGet returns error NU1212). Extracting shared code into Azure.Bicep.McpServer.Core allows consumers — including internal teams — to reference it as a standard library and build custom MCP servers with any transport.

Checklist

• I have read and adhere to the contribution guide.

Microsoft Reviewers: Open in CodeFlow

[github-actions]

Test this change out locally with the following install scripts (Action run 24736610153)

VSCode

• Mac/Linux

  bash <(curl -Ls https://aka.ms/bicep/nightly-vsix.sh) --run-id 24736610153

• Windows

  iex "& { $(irm https://aka.ms/bicep/nightly-vsix.ps1) } -RunId 24736610153"

Azure CLI

• Mac/Linux

  bash <(curl -Ls https://aka.ms/bicep/nightly-cli.sh) --run-id 24736610153

• Windows

  iex "& { $(irm https://aka.ms/bicep/nightly-cli.ps1) } -RunId 24736610153"

[anthony-c-martin]

LGTM

[shenglol]