dotnet-setup vs Packkit
dotnet-setup is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
dotnet-setup is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. Packkit is an MCP server published by DanMat. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Packkit | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.2 Downloads/month (npm): 536 Downloads/week (npm): 86 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | dotnet-setupno longer listed · | Packkit |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | On your machine (packkit-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/danmat/create-packkit |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of dotnet-setup
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
47 skills (incl. 16 slash-command workflows), 10 agents, 10 rules, 5 templates, 22-tool Roslyn MCP server for .NET 10 / C# 14
-
Agent skills for writing efficient .NET code with the .NEXT libraries
-
Essential prompts, instructions, and agents for C# and .NET development including testing, documentation, and best practices.
-
Essential prompts, instructions, and chat modes for C# and .NET development including testing, documentation, and best practices.
-
openapi-to-application-csharp-dotnet
Generate production-ready .NET applications from OpenAPI specifications. Includes ASP.NET Core project scaffolding, controller generation, entity framework integration, and C…
-
Spec-driven development orchestrator for .NET — pipeline planning, agent delegation, quality gates, and .NET-aware hooks
What each says it does
dotnet-setup
Generate .NET project setup with solutions
Packkit
Scaffold modern npm packages, CLIs, services and apps as a native tool for AI agents.
How to run each
dotnet-setup
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Packkit As a local MCP server: npm package
claude mcp add --transport stdio packkit-mcp -- npx -y packkit-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: dotnet-setup · What it can do: Packkit · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.