packages_upgrade
Scan a project/solution/folder for outdated NuGet versions and report or apply upgrades (CPM-aware)
How to use it
packages_upgrade is exposed by the Dotnet Template MCP MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the packages_upgrade tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
FULL DOTNET TEMPLATE MCP LISTINGOther tools in Dotnet Template MCP (16)
5 core tools
Analyze a solution/workspace — project structure, frameworks, CPM status
Compare 2+ templates side by side — parameters, features, frameworks
Execute a sequence of templates (project + items) in one workflow
Analyze a .csproj → generate a reusable template matching repo conventions
Preview files without touching disk
"web API with auth" → webapi + auth=Individual — no LLM needed
Parameters, constraints, post-actions — all in one shot
Install a package (idempotent — skips if already there)
Create a project. Not installed? Auto-resolves from NuGet. Elicits missing params interactively
List what's installed, filter by language/type/classification
Search locally and on NuGet.org — one call, ranked results
Suggest parameter values with rationale based on cross-parameter relationships
Remove a template package
Validate a local template directory for authoring issues before publishing
Inventory of everything installed