原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。评价和账户功能将在后续阶段推出。
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

NuGet API Inspector

作者:DimonSmart版本 1.1.10i★ –i在你的电脑上运行
注册名称io.github.DimonSmart/NugetMcpServer

安装

概览

作者提供的说明(英文原文)

Inspect NuGet package APIs, dependencies, metadata, and breaking changes across versions.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

  • 连接方式: 在你的电脑上运行
  • 传输方式: stdio
  • 分类: 其他

安装

选择你使用的 AI 应用,然后复制设置。

安装之前

  • 基础检查:1 项中通过 1 项
  • 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
  • 需要你自己填写: NUGET_CONFIG, NUGET_SOURCES

你用的是哪个应用?

在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "nugetmcpserver": {
      "command": "dnx",
      "args": [
        "DimonSmart.NugetMcpServer",
        "--yes"
      ],
      "env": {
        "NUGET_CONFIG": "your-value",
        "NUGET_SOURCES": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add nugetmcpserver --env NUGET_CONFIG=your-value --env NUGET_SOURCES=your-value -- dnx DimonSmart.NugetMcpServer --yes

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "nugetmcpserver": {
      "command": "dnx",
      "args": [
        "DimonSmart.NugetMcpServer",
        "--yes"
      ],
      "env": {
        "NUGET_CONFIG": "your-value",
        "NUGET_SOURCES": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "nugetmcpserver": {
      "type": "stdio",
      "command": "dnx",
      "args": [
        "DimonSmart.NugetMcpServer",
        "--yes"
      ],
      "env": {
        "NUGET_CONFIG": "your-value",
        "NUGET_SOURCES": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。

这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上,无需账户。

需要你填写的值

  • NUGET_CONFIG env
    Optional path to a NuGet.Config file for private feeds and custom package sources.
  • NUGET_SOURCES env
    Optional semicolon-separated NuGet feed URLs or local package directories.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

它能做什么

它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 DimonSmart 验证,该账户拥有此仓库

  • … 尚未检查

    仍在维护

    我们还没有从 GitHub 读取这个仓库

  • … 尚未检查

    有许可证

    我们还没有从 GitHub 读取这个仓库

  • – 不适用

    端点有响应

    它在你的电脑上运行,没有互联网端点

  • – 不适用

    使用 OAuth 登录

    在你的电脑上运行,改用本地设置

  • … 尚未检查

    工具描述中没有隐藏指令

    它在你的电脑上运行;我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

  • 星标数多于此分类中其他 32537 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 32537 个服务器的 60% 更新
  • 基础检查结果等于或优于此分类中其他 32537 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

NuGet API Inspector 安全吗?

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。

它还在维护吗?

GitHub 仓库最后更新于–,最新版本(1.1.10)于26天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 .NET。

有什么可以替代它?

同一分类中有:Spec Driven Development, Remote Desktop Commander, TF Rooms

替代选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者:formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新
安装

Remote Desktop Commander

作者:desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新
安装

TF Rooms

作者:tfrooms.com

Live room availability, rates and stay quotes for 12 New Leaf motels in Twin Falls, Idaho.

在云端运行今天更新
安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

NugetMcpServer

Bad NuGet API guesses are expensive.

NugetMcpServer lets Codex, Claude Code, VS Code, Claude Desktop, and other MCP clients inspect real NuGet package metadata and public APIs before generating code. It is most useful when package version details matter or when the package lives in a private feed.

Fastest path: install it with codex mcp add or claude mcp add, then ask your assistant to use the NuGet MCP server before writing package-dependent code.

Why this exists

LLMs often know popular libraries, but they do not reliably know the exact API surface of every package version. NugetMcpServer gives the assistant a way to check the package first instead of filling gaps from memory.

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

What it gives to your assistant

  • Search NuGet packages and inspect package metadata.
  • Read public API definitions for real package versions.
  • Compare versions, inspect package files, and use nuget.org, private feeds, or local package folders.

Quick start

These commands use the current published NuGet package version, 1.1.7. dnx downloads and runs the .NET tool from NuGet, so you do not need a separate dotnet tool install step.

1. Install via Codex CLI
codex mcp add nuget -- dnx DimonSmart.NugetMcpServer@1.1.7 --yes

Check available MCP commands:

codex mcp --help

Inside the Codex TUI, run:

/mcp

Codex CLI and the Codex IDE extension share MCP configuration, so configuring the server once should make it available in both clients.

2. Install via Claude Code CLI
claude mcp add --transport stdio nuget -- dnx DimonSmart.NugetMcpServer@1.1.7 --yes

Everything after -- is the actual MCP server command and arguments.

Manage and verify the server:

claude mcp list

claude mcp get nuget

Inside Claude Code, run:

/mcp
3. Install in VS Code

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

For manual VS Code configuration, add this to mcp.json. Replace with the package version you want to pin:

{

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

4. Install via Docker

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

Codex:

codex mcp add nuget-docker -- docker run -i --rm ghcr.io/dimonsmart/nugetmcpserver:latest

Claude Code:

claude mcp add --transport stdio nuget-docker -- docker run -i --rm ghcr.io/dimonsmart/nugetmcpserver:latest

Run the container directly:

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

5. Manual configuration

Codex config.toml:

[mcp_servers.nuget]

command = "dnx" args = ["DimonSmart.NugetMcpServer@ ", "--yes"]

Codex Docker variant:

[mcp_servers.nuget]

command = "docker" args = ["run", "-i", "--rm", "ghcr.io/dimonsmart/nugetmcpserver:latest"]

Claude Desktop and generic MCP clients that use the mcpServers JSON shape:

{

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

6. Private/local NuGet sources

Use NUGET_SOURCES for one or more source URLs or local package folders. Separate sources with semicolons. Use NUGET_CONFIG when you want NuGet to read a specific NuGet.Config, for example when credentials or source names are already configured there.

Codex with NUGET_SOURCES:

codex mcp add nuget-private \

--env NUGET_SOURCES="C:\NuGet\LocalFeed;https://pkgs.dev.azure.com/ORG/_packaging/Feed/nuget/v3/index.json" \ -- dnx DimonSmart.NugetMcpServer@ --yes

Claude Code with NUGET_SOURCES:

claude mcp add --transport stdio \

--env NUGET_SOURCES="C:\NuGet\LocalFeed;https://pkgs.dev.azure.com/ORG/_packaging/Feed/nuget/v3/index.json" \ nuget-private \ -- dnx DimonSmart.NugetMcpServer@ --yes

Codex with NUGET_CONFIG:

codex mcp add nuget-config \

--env NUGET_CONFIG="/path/to/NuGet.Config" \ -- dnx DimonSmart.NugetMcpServer@ --yes

Claude Code with NUGET_CONFIG:

claude mcp add --transport stdio \

--env NUGET_CONFIG="/path/to/NuGet.Config" \ nuget-config \ -- dnx DimonSmart.NugetMcpServer@ --yes

Use Windows paths such as C:\path\to\NuGet.Config on Windows. Use Unix-style paths such as /path/to/NuGet.Config on Linux and macOS. Keep paths quoted when they contain spaces.

VS Code mcp.json with private sources:

{

"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" } } } }

Codex config.toml with private sources:

[mcp_servers.nuget]

command = "dnx" args = ["DimonSmart.NugetMcpServer@ ", "--yes"]

[mcp_servers.nuget.env] NUGET_SOURCES = "C:\\NuGet\\LocalFeed;https://pkgs.dev.azure.com/ORG/_packaging/Feed/nuget/v3/index.json"

More configuration options: Technical details

Verify it works

After the MCP client shows the server as connected, ask your assistant to use it explicitly:

Use the NuGet MCP server to inspect Dapper 2.1.66 and show the public extension methods for IDbConnection.
Before writing code, use the NuGet MCP server to inspect the real API of Microsoft.Extensions.DependencyInjection.Abstractions and use only existing public types and methods.
Use the NuGet MCP server to compare public APIs of Some.Package 1.8.0 and 2.0.0 and summarize breaking changes.

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

Troubleshooting

  • dnx is not found: install a current .NET SDK and make sure the .NET tools path is available in your shell, or use the Docker install path.
  • Docker is not running: start Docker Desktop or your Docker daemon, then retry the MCP client command.
  • The MCP client shows the server but no tools: restart the client, check the client logs, and verify the server command starts successfully outside the client.
  • Private feed authentication fails: check the active NuGet.Config, credential provider setup, feed URL, and whether the same user account can restore from that feed with normal NuGet tooling.
  • Package restore or search is slow on first run: the server and NuGet client may need to download package metadata and package files before later cached reads are faster.
  • Windows path quoting fails: keep paths in quotes, escape backslashes in JSON/TOML strings, and prefer NUGET_CONFIG when complex source paths or credentials are involved.
  • Claude Code or Codex CLI command fails unexpectedly: make sure the command includes the -- separator before dnx or docker; the MCP client options must appear before that separator.

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

问 PopNx