What problem does it solve? Publishing a C# MCP server involves choosing between NuGet tool packaging for stdio servers and Docker containerization for HTTP servers, then deploying to Azure or listing in the MCP Registry, with strict version consistency requirements across .csproj and server.json files. ## Core Features & Use Cases - NuGet Tool Packaging: Configure .csproj with PackAsTool, build and pack the server, test locally with dotnet tool install, and push to NuGet.org for dnx-based distribution. - Docker and Azure Deployment: Create multi-stage Dockerfiles with non-root users and health checks, push to Azure Container Registry, 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 the server at registry.modelcontextprotocol.io with enforced version consistency. - Use Case: You have a working stdio MCP server and want users to run it with dnx. The skill walks you through .csproj packaging properties, local testing, NuGet push, and optional MCP Registry listing. ## Quick Start Publish my C# MCP server project as a NuGet tool package and list it in the MCP Registry.