Ext Ops Panel
Open dashboard
Comparison

dotnet-pilot vs .NET MCP Server

dotnet-pilot is a plugin bundle for AI coding tools published by zdanovichnick. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). .NET MCP Server is an MCP server published by jongalloway. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacedotnet-pilot.NET MCP Server
Claude Code: claude-plugins-community Listed
Version: 2.5.3
Forks (GitHub): 0
Stars (GitHub): 5
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.2
Forks (GitHub): 4
Stars (GitHub): 36
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

dotnet-pilot vs .NET MCP Server
Factdotnet-pilot.NET MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)5 (worse)36 (better)
Forks (GitHub) (differs)0 (worse)4 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (Community.Mcp.DotNet)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for2, secrets among them: 02, secrets among them: 0
Hooks it runs (differs)11Not published
Parts of the bundle (differs)35Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/zdanovichnick/dotnet-pilotgithub.com/jongalloway/dotnet-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

dotnet-pilot

In its own words, on Claude Code: claude-plugins-community:

Spec-driven development orchestrator for .NET — pipeline planning, agent delegation, quality gates, and .NET-aware hooks

.NET MCP Server

In its own words, on Official MCP Registry:

AI assistant access to .NET SDK for projects, packages, building, testing, and development tools.

How to run each

dotnet-pilot As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install dotnet-pilot@claude-community

.NET MCP Server

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands 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

Only dotnet-pilot asks for

  • DNP_ROSLYN_LOG_LEVEL
  • DNP_ROSLYN_MIN_VERSION

Only .NET MCP Server asks for

  • DOTNET_NOLOGO
  • DOTNET_SKIP_FIRST_TIME_EXPERIENCE

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: dotnet-pilot · What it can do: .NET MCP Server · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built