Ext Ops Panel
Open dashboard
Comparison

plugin-pilot vs Claude Code Explorer MCP

plugin-pilot is a plugin bundle for AI coding tools published by wion4. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Claude Code Explorer MCP is an MCP server published by divu2025. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplaceplugin-pilotClaude Code Explorer MCP
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.0
Downloads/month (npm): 145
Downloads/week (npm): 27
Forks (GitHub): 3 666
Stars (GitHub): 3 376
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

plugin-pilot vs Claude Code Explorer MCP
Factplugin-pilotClaude Code Explorer MCP
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)3 376 (better)
Forks (GitHub) (differs)0 (worse)3 666 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@divyesh2000/codemaster)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)5Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/wion4/plugin-pilotgithub.com/codeaashu/claude-code
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

plugin-pilot

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

AI-driven plugin lifecycle manager for Claude Code. Automatically detects which plugins, skills, and stacks are relevant to your current task based on project files, frameworks, and context. Searches official marketplace and GitHub for matching tools, tracks usage to suggest cleanup of unused plugins, and integrates into plan mode. Includes legal framework (TOS, Privacy Policy), trust scoring for community plugins, and system language detection

Claude Code Explorer MCP

In its own words, on Official MCP Registry:

Explore the Claude Code CLI source — browse tools, commands, search code, and more.

How to run each

plugin-pilot As a Claude Code plugin

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

Claude Code Explorer MCP As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio codemaster -- npx -y @divyesh2000/codemaster

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

Neither one's marketplaces publish the settings it asks for.

What it can do: plugin-pilot · What it can do: Claude Code Explorer MCP · 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