nuget-packages

This MCP server provides tools to interact with NuGet package data via the MCP protocol. It exposes three primary tools: GetPackageVersions to list all available package versions (including prereleases) from a configured NuGet v3 feed, GetPackageDependencies to fetch the dependencies for a specific package version, and GetPackageContracts to generate a markdown document describing the public API surface of a package. Configure the NuGet feed (default is nuget.org) using the NugetFeed:FeedUrl setting in your MCP client configuration. Once running, you can invoke each tool with the required parameters and receive structured responses or generated Markdown contracts that you can display in your editor or assistant workflow.

Prerequisites:\n- .NET 8.0 SDK or later\n- Node.js (only required if you plan to run MCP Inspector locally)\n- An MCP-compatible client (e.g., Claude Desktop, Cline VS Code extension)\n\nInstallation steps:\n1) Clone the repository and navigate to it:\n git clone https://github.com/oshvartz/nuget-packages-mcp-server.git\n cd nuget-packages-mcp-server\n\n2) Build the project in Release configuration:\n dotnet build -c Release\n\n3) Locate the built DLL (example path):\n src/NugetPackagesMcpServer/bin/Release/net8.0/NugetPackagesMcpServer.dll\n\n4) Run the server (example):\n dotnet src/NugetPackagesMcpServer/bin/Release/net8.0/NugetPackagesMcpServer.dll\n\n5) Optional: Install and run MCP Inspector for testing:\n - Ensure Node.js and npm are installed.\n - Run the provided PowerShell test script to launch Inspector and the server:\n .\test-mcp-inspector.ps1\n\n6) Configure MCP client settings to point to the server (example shown in the README): use the server name nuget-packages-mcp-server with command dotnet and the appropriate DLL path.

Tips and considerations:\n- The NuGet feed URL can be overridden with NugetFeed:FeedUrl in your MCP client settings. If left unspecified, it defaults to the NuGet.org v3 feed.\n- Prerelease versions can be included by setting includePrerelease when calling GetPackageVersions or by configuring the feed accordingly.\n- If you encounter startup issues, verify that the .NET 8.0 SDK is installed and that the path to NugetPackagesMcpServer.dll matches your build output.\n- MCP Inspector (when used) helps validate tool schemas and protocol compliance and can be run via the included test script.\n- The server is designed to be fed by MCP clients; ensure your client’s settings use type: stdio and pass the correct arguments for the selected tool.\n- For large feeds or complex packages, consider increasing the timeout in your MCP client settings.