Over the past 6 months, I've built a fully featured MCP Server that wraps the .NET 10 SDK, with a lot of help from GitHub Copilot. It lets you do give commands like "Create a server-side web app and minimal API, orchestrated by .NET Aspire, with unit tests for the API using xunit. Use slnx format for the solution." and get high-quality, repeatable results because it actually executes the correct dotnet CLI commands.

But this isn't just a vibe-coded #yolo experiment - I wanted to really practice building a quality MCP server. I've made over 800 commits and every PR runs over 1000 tests; I've worked to dial in things like MCP conformance tests and support for the latest features in the C# MCP SDK. Along the way I've helped find edge cases in the SDK and gotten a few upstream PRs merged.

I think the two main things you'll get out of this talk are:
- Some deeper technical info on how to build and publish an MCP server, including testing (unit, conformance, release-gate, performance) and full publishing with GitHub actions to NuGet and the MCP Registry.
- Lessons learned on leveraging GitHub Copilot on a one-person project while maintaining high quality through specifications, testing, and workflows.