wingetCollections
  • Auto
  • Search
  • Awesome Collections
  • Awesome Programs
  • My Favorite Collections
  • My Collections
  • Account / Settings
  • Terms of Service
  • Privacy
  • About

© 2026 winget.ragerworks.com

Loading...
Install DimonSmart.NugetMcpServer using Winget - wingetCollections
  1. Go back
  2. Packages
  3. DimonSmart.NugetMcpServer
DimonSmart.NugetMcpServer logo

DimonSmart.NugetMcpServer DimonSmart

ai-tools developer-tool mcp mcp-server nuget
Use this command to install DimonSmart.NugetMcpServer:
winget install --id=DimonSmart.NugetMcpServer -e

DimonSmart.NugetMcpServer is a Model Context Protocol (MCP) server designed to enable communication between language models and external tools. It provides functionality for searching interfaces and their methods within NuGet packages, facilitating seamless integration between AI-driven applications and existing codebases.

Key Features:

  • MCP server implementation supporting STDIO transport for client communication.
  • Sample tool (TimeTool) that demonstrates basic functionality by returning the current server time in ISO 8601 format.
  • InterfaceLookupService for extracting interface definitions from NuGet packages, including support for listing all public interfaces within a package.
  • Built using .NET 9.0, ensuring compatibility with modern development environments.

Audience & Benefit: Ideal for developers working with NuGet packages, AI-driven applications, or MCP protocol implementations. The server enables efficient integration of external tools and services into language model workflows, reducing the complexity of tool interaction while maintaining scalability.

The software can be installed via winget, ensuring straightforward setup and deployment across compatible environments.

README

NugetMcpServer

NuGet Install via Docker

Bad NuGet API guesses are expensive.

NugetMcpServer gives your AI assistant access to real NuGet package metadata. Instead of guessing which classes, interfaces, methods, properties, or enum values exist, the assistant can inspect the actual package version.

Certified by MCPHub.

Why this exists

LLMs often know popular libraries, but they do not reliably know the exact API surface of every package version. Small mistakes show up as:

  • a method name from another version;
  • an overload that does not exist;
  • a property with the wrong type;
  • a class from a different package;
  • a migration suggestion based on outdated API.

NugetMcpServer connects the assistant to NuGet packages directly, including private feeds and local package folders.

What it gives to your assistant

  • Package search by name or task.
  • Exact public types from a package.
  • Interface, class, struct, record, and enum definitions.
  • API comparison between package versions.
  • Access to files inside the package.
  • Support for nuget.org, private feeds, and local package folders.

Typical use cases

Generate code against the real API

Ask your assistant to inspect the exact package version before writing code.

> Use Dapper and check the real public API before suggesting the implementation.

Check package migrations

Compare two package versions before upgrading.

> Compare Some.Package 1.8.0 and 2.0.0 and show breaking API changes.

Work with private packages

Point the server to your internal feed and let the assistant inspect packages that are not visible on the public internet.

Quick start

Recommended: VS Code via NuGet

Open the NuGet package page, select the MCP Server tab, and copy the generated VS Code configuration.

Versions
1.1.7
1.1.5
1.0.18
1.0.12
1.0.11
1.0.10
1.0.9
1.0.8
1.0.7
1.0.6
show 4 more
Website
github.com
License
Last updated
6/15/2026
Download latest version

For manual VS Code configuration, add this to mcp.json and replace `` with the package version you want to use:

{
  "servers": {
    "nuget": {
      "type": "stdio",
      "command": "dnx",
      "args": ["DimonSmart.NugetMcpServer@", "--yes"]
    }
  }
}

Docker

Use Docker when the MCP client environment does not have the .NET SDK available.

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

VS Code mcp.json:

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

Install in VS Code with Docker

Claude Desktop

Add the server to the Claude Desktop MCP configuration and replace `` with the package version you want to use:

{
  "mcpServers": {
    "nuget": {
      "command": "dnx",
      "args": ["DimonSmart.NugetMcpServer@", "--yes"]
    }
  }
}

Other MCP clients

Use the client-specific MCP configuration format. For clients that use the common mcpServers shape:

{
  "mcpServers": {
    "nuget": {
      "command": "dnx",
      "args": ["DimonSmart.NugetMcpServer@", "--yes"]
    }
  }
}

Private and local NuGet sources

Use NUGET_SOURCES or NUGET_CONFIG to point the server at local package folders or private NuGet feeds.

{
  "servers": {
    "nuget": {
      "type": "stdio",
      "command": "dnx",
      "args": ["DimonSmart.NugetMcpServer@", "--yes"],
      "env": {
        "NUGET_SOURCES": "C:\\NuGet\\LocalFeed;https://pkgs.dev.azure.com/ORG/_packaging/Feed/nuget/v3/index.json"
      }
    }
  }
}

More configuration options: Technical details

Available tools

  • search_packages: search packages by query and keywords.
  • search_packages_fuzzy: use AI-assisted fuzzy package search.
  • get_package_info: get package metadata, dependencies, and package shape.
  • list_interfaces: list public interfaces.
  • list_classes_records_structs: list public classes, records, and structs.
  • get_interface_definition: return a C# interface definition.
  • get_class_or_record_or_struct_definition: return a C# class, record, or struct definition.
  • get_enum_definition: return a C# enum definition.
  • compare_package_versions: compare public API changes between versions.
  • list_package_files: list files inside a package.
  • get_package_file: read a file from a package.
  • get_current_time: return the current server time.

Detailed parameters and development notes: Technical details

Version

The release version is assigned by the GitHub Actions pipeline from the Git tag.

Check the installed version:

NugetMcpServer --version

Publishing

NuGet releases are published from version tags on main:

.\publish-next-version.ps1

The script creates and pushes the next vMAJOR.MINOR.PATCH tag. GitHub Actions builds, tests, updates the MCP manifest version, packs the NuGet MCP server package, and publishes it to NuGet.

WinGet publishing is also tag-driven after the GitHub release exists:

.\publish-winget-version.ps1

By default, the WinGet script uses the latest vMAJOR.MINOR.PATCH release tag. Pass -Version 1.2.3 to publish a specific release.

License

MIT