NuGetMCP

NuGet MCP Server

A Model Context Protocol (MCP) server that provides NuGet package management capabilities through a standardized interface.

Features

• Get Package Information: Retrieve detailed information about specific NuGet packages
• Search Packages: Search the NuGet repository with query terms
• Publish Packages: Upload new packages to NuGet (requires API key)
• Publish Symbol Packages: Upload symbol packages (.snupkg or .symbols.nupkg) to NuGet symbol server (requires API key)
• Delete Packages: Delete entire packages or specific versions from NuGet (requires API key)
• User Package Retrieval: Get all packages for a specific user
• List Package Files: List all files contained within a NuGet package

Setup

Usage with VSCode

Use one of the methods below. Once you complete that flow, toggle Agent mode (located by the Copilot Chat text input) and the server will start.

Running from Source

1. Clone the project:

   git clone https://github.com/RiadGahlouz/NuGetMCP.git
   

2. (Optional) Set your NuGet API key as an environment variable for publishing:

   export NUGET_API_KEY=your_api_key_here
   

3. Setup your MCP host (e.g: through .vscode/mcp.json):

  { 
    "inputs": [
    {
      "type": "promptString",
      "id": "nuget_api_key",
      "description": "NuGet API Key",
      "password": true
    }],
    "servers": {
      "NuGetMCP": {
        "type": "stdio",
        "command": "dotnet",
        "args": [
          "run",
          "--project",
          "PATH/TO/THE/PROJECT/NuGetMCP/NuGetMCP.csproj"],
        "env": {
          "NUGET_API_KEY": "${input:nuget_api_key}"
        }
      }
    }
  }

Running as a docker container

Work in progress..

Available Tools

QueryPackage

Get detailed information about a specific NuGet package.

Parameters:

• packageId (required): The package ID to get information for
• version (optional): Specific version to get info for

SearchPackages

Search for NuGet packages using a query string.

Parameters:

• query (required): Search query
• skip (optional): Number of results to skip (default: 0)
• take (optional): Number of results to return (default: 20, max: 100)

PublishPackage

Publish a NuGet package (requires API key).

Parameters:

• packageFilePath (required): Path to the .nupkg file to publish
• apiKey (optional): NuGet API key for publishing

PublishSymbolPackage

Publish a symbol package to the NuGet symbol server (requires API key).

Parameters:

• symbolPackagePath (required): Path to the symbol package file (.snupkg or .symbols.nupkg) to publish
• apiKey (optional): NuGet API key for publishing symbols

DeletePackage

Delete all versions of a NuGet package (requires API key).

Parameters:

• packageId (required): The package ID to delete
• apiKey (optional): NuGet API key for package management

DeletePackageVersion

Delete a specific version of a NuGet package (requires API key).

Parameters:

• packageId (required): The package ID to delete
• version (required): The version to delete
• apiKey (optional): NuGet API key for package management

GetUserPackages

Retrieve all packages for a specific user.

Parameters:

• username (required): The username to query for packages

ListPackageFiles

List all files contained within a NuGet package.

Parameters:

• packageId (required): The package ID to list files for
• version (optional): Specific version to list files for (defaults to latest)

Configuration

The server can be configured through environment variables:

• NUGET_API_KEY: Your NuGet API key for publishing and managing packages
• ASPNETCORE_ENVIRONMENT: Set to Development for development mode

Requirements

• .NET 8.0 or later
• Internet connection for NuGet API access
• Valid NuGet API key for publishing/managing packages

Notes

• The server uses the official NuGet API endpoints
• Search functionality uses the Azure Search service provided by NuGet
• Publishing and deletion operations require a valid NuGet API key
• Symbol packages (.snupkg or .symbols.nupkg) are published to the NuGet symbol server
• All operations are performed asynchronously for better performance

Future Development

More toolsets will be added in the near future. Some ideas:

• User/Organisation metadata retrieval
• Symbol package publishing
• List files inside a package
• Get a specific file inside a package
• Get Package README
• Advanced package metadata retrieval