Ext Ops Panel
Open dashboard
Comparison

Plugin Management vs mcpgawk

Plugin Management is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). mcpgawk is an MCP server published by gawk-dev. Marketplaces we read that list it: 2 (Official MCP Registry, 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 Managementmcpgawk
Claude: knowledge-work-plugins Listed
Version: 0.2.2
Forks (GitHub): 3 317
Stars (GitHub): 29 279
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.78
Downloads/month (PyPI): 4 766
Downloads/week (PyPI): 1 072
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 mcpgawk
FactPlugin Managementmcpgawk
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)29 279 (better)0 (worse)
Forks (GitHub) (differs)3 317 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mcpgawk)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle22
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/anthropics/knowledge-work-pluginsgithub.com/gawk-dev/mcpgawk
Changes in the last 7 days (differs)02
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.

mcpgawk

In its own words, on Official MCP Registry:

Measure MCP servers, pin the approved tool surface, refuse calls to tools that changed. Local-first.

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

mcpgawk As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio mcpgawk -- uvx mcpgawk 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: mcpgawk · 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 Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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