Ext Ops Panel
Open dashboard
Comparison

Plugin Management vs mcpd

Plugin Management is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). mcpd is a plugin bundle for AI coding tools published by yn01. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-15. 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 Managementmcpd
Claude: knowledge-work-plugins Listed
Version: 0.2.2
Forks (GitHub): 3 361
Stars (GitHub): 29 647
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: b99b1bb
Forks (GitHub): 0
Stars (GitHub): 0
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 Management vs mcpd
FactPlugin Managementmcpd
Marketplaces that list it11
Stars (GitHub) (differs)29 647 (better)0 (worse)
Forks (GitHub) (differs)3 361 (better)0 (worse)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not published
LicenceNot statedNot stated
Repository (differs)github.com/anthropics/knowledge-work-pluginsgithub.com/yn01/claude-plugins
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 Management

In its own words, on Claude: knowledge-work-plugins:

Create, customize, and manage plugins tailored to your organization's tools and workflows. Configure MCP servers, adjust plugin behavior, and adapt templates to match how your team works.

mcpd

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

Diagnose MCP server configuration, connectivity, and available tools — all in one command. mcpd reads your global and project-level MCP config files, checks that required environment variables are set, verifies server connectivity (stdio and SSE/HTTP), and lists all available tools. Get a clear picture of your entire MCP setup in seconds.

How to run each

Plugin Management As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install cowork-plugin-management@knowledge-work-plugins

mcpd As a Claude Code plugin

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

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 Management · What it can do: mcpd · Compare two other plugins

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