Ext Ops Panel
Open dashboard
Comparison

VeyraX vs Plugin Management

VeyraX is an MCP server published by VeyraX. Marketplaces we read that list it: 1 (Docker MCP Catalog). Plugin Management is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). As of our marketplace pass on 2026-10-14. 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
MarketplaceVeyraXPlugin Management
Docker MCP Catalog Listed
Version: sha256:257d91533072
Forks (GitHub): 19
Pulls (Docker Hub): 18 325
Stars (Docker Hub): 4
Stars (GitHub): 48
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Not listed Listed
Version: 0.2.2
Forks (GitHub): 3 345
Stars (GitHub): 29 497
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

VeyraX vs Plugin Management
FactVeyraXPlugin Management
Marketplaces that list it11
Stars (GitHub) (differs)48 (worse)29 497 (better)
Pulls (Docker Hub) (differs)18 325No figure on Docker Hub
Forks (GitHub) (differs)19 (worse)3 345 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/veyrax)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)3Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle2
LicenceNot statedNot stated
Repository (differs)github.com/veyrax/veyrax-mcpgithub.com/anthropics/knowledge-work-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

VeyraX

In its own words, on Docker MCP Catalog:

VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.

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.

How to run each

VeyraX As a local MCP server: Docker image

Claude Code
claude mcp add --env "VEYRAX_API_KEY=<YOUR_VEYRAX_API_KEY>" --transport stdio veyrax -- docker run -i --rm -e VEYRAX_API_KEY mcp/veyrax

Requires: VEYRAX_API_KEY (secret)

Plugin Management As a Claude Code plugin

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

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of Plugin Management publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Plugin Management publish no settings it asks for, so we do not compare settings.

What it can do: VeyraX · What it can do: Plugin Management · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/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