NugetMcpServer

NugetMcpServer is an MCP server that lets AI assistants inspect NuGet packages in real time. It connects to the NuGet ecosystem and lets clients query for exact package metadata, interfaces, classes, enums, and type definitions across versions. This enables accurate code suggestions and reduces guesswork when working with NuGet APIs. The server exposes a set of tools to search for packages, fetch package information, and retrieve specific type definitions, all accessible through any MCP-compatible client (e.g., VS Code Copilot, Claude Desktop, OllamaChat, or other MCP clients).

To use it, run the server (via Docker, .NET tool, or other supported methods) and point your MCP client at the running instance. Once connected, you can perform operations such as searching for packages, inspecting interfaces or classes, listing package contents, and comparing versions. Tools are designed to accept optional source parameters to target specific feeds or local NuGet sources, and you can configure environment variables to point to private feeds or config files.

Prerequisites:

• Docker installed and running (recommended for quick setup)
• Optional: .NET 9.0 SDK if you prefer the .NET tool native approach

Option A: Run with Docker (Recommended)

1. Install Docker from https://www.docker.com/
2. Run the MCP server:

docker run -i --rm ghcr.io/dimonsmart/nugetmcpserver:latest

Option B: Install via .NET Tool (Local)

1. Install the .NET 9.0 SDK from https://dotnet.microsoft.com/download
2. Install the tool globally:

dotnet tool install -g DimonSmart.NugetMcpServer

3. Run the server (the tool name is NugetMcpServer):

NugetMcpServer

Option C: Install via Smithery for Claude Desktop (optional)

npx -y @smithery/cli install @dimonsmart/nugetmcpserver --client claude

Option D: Manual Configuration (JSON) for MCP clients

{
  "mcpServers": {
    "nuget": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "ghcr.io/dimonsmart/nugetmcpserver:latest"]
    }
  }
}

Notes and tips:

• The server can connect to private NuGet feeds by providing --source values or by setting environment variables like NUGET_SOURCES and NUGET_CONFIG in client configurations.
• Availability of specific tools (search_packages, get_package_info, list_interfaces, etc.) is described in the README under Available Tools. Each tool may accept an optional source parameter to target a feed or local path.
• If you run behind proxies or corporate networks, ensure Docker or your host tool can access NuGet feeds. For local feeds, provide local paths or URLs as sources when invoking CLI tools.
• When using private feeds, you may need to set NUGET_CONFIG to point to your nuget.config and expose NUGET_SOURCES as needed.
• The MCP client configuration (VS Code / Claude / etc.) mirrors the server’s mcpServers entry and can include env vars to point to private feeds.