Add support for .NET / NuGet based MCP servers

[joelverhagen]

Is your feature request related to a problem? Please describe.

I am on the NuGet team. I would like to provide a contribution enabling NuGet support on the MCP server, but I'd like to have an open discussion about this before just firing off a PR :D

I have a NuGet + .NET + VS Code focused proposal here:
NuGet/Home#14344

No need to read that unless you want to (all feedback is welcome!), but I would like to understand the process of getting support for NuGet on the MCP registry. AFAIK, we need a single-shot command experience and then the OpenAPI definition updated.

registry/docs/openapi.yaml

Line 174 in 6b22cf0

enum: [npm, docker, pypi, homebrew]

(this needs nuget)

The single-shot experience will be available in the next month or two, under the name dnx shipping inside the .NET SDK. At which point I'd like to light up support on the Registry and in VS Code as a "reference client implementation".

Describe the solution you'd like

Add support for nuget as a supported page type, similar to npm and pypi.

Describe alternatives you've considered

.NET packages could be bundled in npm packages (@azure/mcp does this) or in Docker containers. This can technically work but is not ideal since .NET has a robust (if I do say so myself 😅) packaging solution analogous to npm and PyPI.

Additional context

An "new package registry" checklist would be great. I am connecting the dots somewhat and have spoken to VS Code folks about NuGet support so I have a generally idea of the gaps to fill, but I want to be sure.

[tadasant]

This all makes sense to me! Contributions like this is exactly how we'd want to expand that list :)

Also I think we can remove homebrew, didn't mean to include that at first pass.

Agree a generalized checklist for this would be helpful.

A bit of a blocker on this is #96 (which I know you've already commented on). If someone is keen to really drive that issue and propose a solution that will work across the ecosystem, a contribution there would be very much appreciated.

[joelverhagen]

I am proposing that all NuGet MCP servers have the server.json embedded in the root of the package artifact (.nupkg file, a ZIP). I have NuGet UI enrichment in mind when I considered this, but I wonder if this provides a generalized solution for #96. I will follow and participate in the discussion on that issue and leave this issue to truly NuGet / .NET specific things.