Can AI agents automate NuGet?

NuGet is automatable today through the NuGet V3 HTTP API. This record is NuGet package feeds and the NuGet MCP server shipped as NuGet.Mcp.Server. It is not JFrog Artifactory, GitHub Packages, or npm. The nuget.org service index is https://api.nuget.org/v3/index.json. Microsoft Learn documents resources for package content, metadata, search, and publish. On nuget.org, only the PackagePublish resource requires authentication, and it uses the X-NuGet-ApiKey header for push, unlist, and relist. Reads of public packages do not use that header. nuget.exe installs, creates, publishes, and manages packages. The pack, restore, delete, locals, and push commands are also available on macOS and Linux through the dotnet CLI. Some nuget.exe commands are limited under Mono. The MCP server is local stdio through dnx. Microsoft Learn requires the .NET 10 SDK or later. NuGet.Mcp.Server 1.4.16 lists fix_vulnerable_packages, upgrade_packages_to_latest, get_latest_package_version, get_package_context, update_package_version, and review_supply_chain_security. Visual Studio 2026 includes the server and it must be enabled. Visual Studio 2022 17.14 or later uses a manual stdio config aimed at the nuget.org service index. The package page for 1.4.16 still says .NET 10 Preview 6 or later. Webhooks and an llms.txt index were not established. iPaaS catalogs were not opened. Computer-use viability is unassessed. The API scores 8, the CLI scores 7, and MCP scores 7. API is the best path because an HTTP client can search, download, and publish without the .NET 10 SDK.

Best path today: api · Overall automatability: 8/10