mcp-csharp-publish

# C# MCP Server Publishing Publish and deploy MCP servers to their target platforms. stdio servers are distributed as NuGet tool packages. HTTP servers are containerized and deployed to Azure or other container hosts. Both can optionally be listed in the official MCP Registry. ## When to Use - Packaging a stdio MCP server for NuGet distribution - Creating a Docker container for an HTTP MCP server - Deploying to Azure Container Apps or App Service - Publishing to the official MCP Registry for discoverability - Setting up `server.json` metadata for the MCP Registry ## Stop Signals - **Server not tested yet?** → Use `mcp-csharp-test` first - **Server not working locally?** → Use `mcp-csharp-debug` - **No server project yet?** → Use `mcp-csharp-create` - **Publishing a non-MCP NuGet package?** → Use `nuget-trusted-publishing` instead ## Inputs | Input | Required | Description | |-------|----------|-------------| | Transport type | Yes | `stdio` → NuGet path, `http` → Docker/Azure path | | Target destination | Yes | NuGet.org, Docker registry, Azure Container Apps, Azure App Service, MCP Registry | | Project path | Yes | Path to the `.csproj` file | | Package ID / server name | Required for publishing | NuGet `PackageId` or MCP Registry name | ## Workflow ### Step 1: Choose the publishing path | Transport | Primary Destination | Users Run With | |-----------|-------------------|----------------| | **stdio** | NuGet.org | `dnx YourPackage@version` | | **HTTP** | Docker → ...