Ext Ops Panel
Open dashboard
Comparison

Plugin Management vs Kineticist

Plugin Management is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). Kineticist is an MCP server published by kineticist.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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 ManagementKineticist
Claude: knowledge-work-plugins Listed
Version: 0.2.2
Forks (GitHub): 3 885
Stars (GitHub): 35 186
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.5.0
Downloads/month (npm): 1 097
Downloads/week (npm): 100
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.5.0
Downloads/month (npm): 1 097
Downloads/week (npm): 100
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 Kineticist
FactPlugin ManagementKineticist
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)35 186No figure on GitHub
Forks (GitHub) (differs)3 885No figure on GitHub
Last release (differs)Not published2026-10-24
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/anthropics/knowledge-work-pluginsgithub.com/colinize/kineticist
Changes in the last 7 days (differs)01
First seen (differs)2026-10-112026-10-17
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 38 h ago returned HTTP 405

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.

Kineticist

In its own words, on Official MCP Registry:

Pinball news, games and editions, designers, places to play and the Hype Index from Kineticist.

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

Kineticist As a remote MCP server

Claude Code
claude mcp add --transport http kineticist https://www.kineticist.com/api/mcp

Requires: KINETICIST_API_KEY (secret)

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

Only Kineticist has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of Plugin Management nor its endpoint list any 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: Plugin Management · What it can do: Kineticist · 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. Package data comes from the public npm registry (registry.npmjs.org). 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