Ext Ops Panel
Open dashboard
Comparison

cowork-plugin-management vs VMware Pilot

cowork-plugin-management is a plugin bundle for AI coding tools published by anthropics. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). VMware Pilot is an MCP server published by vmware-skills. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
Marketplacecowork-plugin-managementVMware Pilot
Claude Code: claude-plugins-community Listed
Version: not stated
Forks (GitHub): 347
Stars (GitHub): 4 786
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.4.0
Downloads/month (PyPI): 1 303
Downloads/week (PyPI): 420
Forks (GitHub): 0
Stars (GitHub): 4
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

cowork-plugin-management vs VMware Pilot
Factcowork-plugin-managementVMware Pilot
Marketplaces that list it11
Stars (GitHub) (differs)4 786 (better)4 (worse)
Forks (GitHub) (differs)347 (better)0 (worse)
Last release (differs)Not published2026-10-18
Where it runs (differs)Installs as a plugin bundleOn your machine (vmware-pilot)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/anthropics/claude-plugins-communitygithub.com/vmware-skills/vmware-pilot
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

cowork-plugin-management

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

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.

VMware Pilot

In its own words, on Official MCP Registry:

Multi-step workflow orchestration for VMware MCP skills with approval gates and rollback.

How to run each

cowork-plugin-management As a Claude Code plugin

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

VMware Pilot As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio vmware-pilot -- uvx vmware-pilot 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: cowork-plugin-management · What it can do: VMware Pilot · 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