Ext Ops Panel
Open dashboard
Comparison

Plugin Management vs extension-mcp

Plugin Management is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). extension-mcp is a plugin bundle for AI coding tools published by Cezar Augusto. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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 Managementextension-mcp
Claude: knowledge-work-plugins Listed
Version: 0.2.2
Forks (GitHub): 3 345
Stars (GitHub): 29 497
Not marked · First seen
Not listed
Community marketplace extensiondev/mcp Not listed Listed
Version: 10.11.6
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 extension-mcp
FactPlugin Managementextension-mcp
Marketplaces that list it11
Stars (GitHub) (differs)29 497 (better)0 (worse)
Forks (GitHub) (differs)3 345 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@extension.dev/mcp)
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)25
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/anthropics/knowledge-work-pluginsgithub.com/extensiondev/mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-13

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.

extension-mcp

In its own words, on Community GitHub marketplaces:

MCP tools for browser extension development: scaffold from 50+ templates, run the dev server with HMR, inspect the live DOM and logs, and build store-ready bundles for Chrome, Edge, and Firefox.

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

extension-mcp As a Claude Code plugin

Claude Code
/plugin marketplace add extensiondev/mcp
/plugin install extension-mcp@extensiondev-mcp

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: extension-mcp · 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 public marketplace files in GitHub repositories of their authors. 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