Nuget
Let your coding agent search, inspect, and reason about NuGet packages while you wire .NET dependencies.
Overview
com.microsoft/nuget is a Build-phase MCP server that lets AI agents query and work with the NuGet package ecosystem via stdio.
What is this MCP server?
- MCP stdio server package NuGet.Mcp.Server v1.4.3 on nuget.org
- Connects agents to the public NuGet v3 API index
- Official Microsoft/NuGet.Home MCP subfolder implementation
- Useful for dependency audits, upgrade paths, and package metadata questions
- Server schema version 1.4.3
- Single stdio package: NuGet.Mcp.Server on registryType nuget
- Registry base URL: https://api.nuget.org/v3/index.json
Community signal: 1.5k GitHub stars.
What problem does it solve?
Agents guess at NuGet package names and versions instead of pulling live metadata from the registry.
Who is it for?
.NET or mixed-stack builders who use MCP daily and want package lookup inside the agent loop.
Skip if: Teams on npm-only or Python-only stacks with no NuGet surface area.
What do I get? / Deliverables
Your agent can ground dependency recommendations in NuGet.org data while you integrate .NET libraries.
- Live NuGet catalog queries from the agent
- Grounded package and version suggestions for .NET integrations
Recommended MCP Servers
Journey fit
How it compares
Registry MCP integration for NuGet—not a skill that teaches architecture or a marketplace of prompts.
Common Questions / FAQ
Who is com.microsoft/nuget for?
Solo builders and small teams shipping .NET who want their AI agent to reference real NuGet package data through MCP.
When should I use com.microsoft/nuget?
During Build when you are choosing packages, comparing versions, or explaining dependencies in a .NET solution.
How do I add com.microsoft/nuget to my agent?
Install NuGet.Mcp.Server from NuGet, configure stdio MCP in your host (e.g. Claude Code), and point transport at the published package entry.