What problem does it solve? Building a Model Context Protocol server in .NET involves many failure points: choosing the wrong transport, polluting stdout in stdio mode, missing tool attributes, and packaging mistakes. This Skill provides a complete engineering playbook for creating, debugging, testing, and publishing C# MCP servers with Microsoft's official ModelContextProtocol SDK. ## Core Features & Use Cases - Server Scaffolding & Transport Selection: Guides project creation for stdio console hosts versus ASP.NET Core Streamable HTTP hosts, with DI registration and tool contract rules ([McpServerToolType], [McpServerTool], [Description]). - Debugging & Protocol Verification: Enforces Inspector-first verification with npx @modelcontextprotocol/inspector, stdout safety invariants, and IDE client configuration for VS Code, Visual Studio, and Claude Desktop. - Testing & Evaluations: Covers direct tool unit tests, McpClient protocol integration tests asserting ListToolsAsync and CallToolAsync, WebApplicationFactory HTTP tests, and LLM tool evaluation suites. - Publishing & Deployment: Walks through NuGet tool packaging (PackAsTool), chiseled multi-stage Dockerfiles, Azure Container Apps deployment, and MCP Registry publishing via server.json. - Use Case: You need to expose your company's internal API as MCP tools for AI assistants. Use this Skill to scaffold a stdio server, verify it in the MCP Inspector, write protocol integration tests, and publish it as a NuGet tool listed on the MCP Registry. ## Quick Start Ask the AI to scaffold a new C# MCP server with stdio transport using the official ModelContextProtocol SDK and verify it with the MCP Inspector.