Ext Ops Panel
Open dashboard
Comparison

clawket vs io.github.Gammell53/clawwork

clawket is a plugin bundle for AI coding tools published by Seungwoo321. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.Gammell53/clawwork is an MCP server published by Gammell53. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
Marketplaceclawketio.github.Gammell53/clawwork
Claude Code: claude-plugins-community Listed
Version: 3.2.3
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.3
Downloads/month (npm): 177
Downloads/week (npm): 27
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

clawket vs io.github.Gammell53/clawwork
Factclawketio.github.Gammell53/clawwork
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@clawwork/mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Hooks it runs (differs)8Not published
Parts of the bundle (differs)15Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/seungwoo321/clawketgithub.com/gammell53/clawwork-mcp
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

clawket

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

LLM-native work management plugin for Claude Code. 10 lifecycle hooks auto-track your entire workflow — PreToolUse blocks code changes unless a task is registered. Includes 6 dashboard views (Kanban, Timeline, Wiki, Backlog, Plans, Summary), sub-agent task binding, and auto-cascade completion. All data stored locally in SQLite.

io.github.Gammell53/clawwork

In its own words, on Official MCP Registry:

AI agent project management — task boards, progress tracking, and cost reporting.

How to run each

clawket As a Claude Code plugin

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

io.github.Gammell53/clawwork As a local MCP server: npm package

Claude Code
claude mcp add --env "CLAWWORK_API_KEY=<YOUR_CLAWWORK_API_KEY>" --transport stdio clawwork -- npx -y @clawwork/mcp

Requires: CLAWWORK_API_KEY (secret)

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

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

What it can do: clawket · What it can do: io.github.Gammell53/clawwork · 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