What problem does it solve? Publishing a C# MCP server involves several distinct paths—NuGet tool packaging for stdio servers, Docker containerization for HTTP servers, Azure deployment, and MCP Registry listing—and getting any step wrong (like version mismatches or missing PackAsTool settings) causes failures that are hard to diagnose. ## Core Features & Use Cases - NuGet Tool Packaging: Configure .csproj with PackAsTool, build, pack, test locally, and push stdio MCP servers to NuGet.org for dnx-based distribution. - Docker & Azure Deployment: Create production Dockerfiles for HTTP MCP servers and deploy to Azure Container Apps or App Service with secrets management. - MCP Registry Publishing: Generate server.json metadata, authenticate with mcp-publisher, and list servers on registry.modelcontextprotocol.io. - Use Case: You have finished building a stdio MCP server in C# and want users to run it via dnx YourPackage@1.0.0—this Skill walks you through packaging, testing, pushing to NuGet, and optionally listing it in the official MCP Registry. ## Quick Start Use the mcp-csharp-publish skill to package my stdio MCP server project as a NuGet tool and publish it to NuGet.org.