humwork vs Workfile
humwork is a plugin bundle for AI coding tools published by humworkai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Workfile is an MCP server published by illodev. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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
| Marketplace |  humwork |  Workfile |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: c93539e Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.13.2 Downloads/month (npm): 1 620 Downloads/week (npm): 266 Forks (GitHub): 0 Stars (GitHub): 3 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
| Fact | humwork | Workfile |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 (worse) | 3 (better) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@illodev/workfile) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | Not published | 3 |
| Parts of the bundle (differs) | Not published | 9 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/humworkai/humwork-mcp | github.com/illodev/workfile |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-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
humwork
Real-time consultation with verified human domain experts (software, design, law, finance, medical, product). When your AI agent is stuck — after multiple failed approaches, on a high-stakes decision, or working in unfamiliar territory — Humwork matches it with a vetted human in under 60 seconds and feeds the expert's response back into your conversation. Five MCP tools cover the full session lifecycle: open, send messages, read replies, close, rate.
Workfile
Repository-native protocol and local MCP server for Work, Docs, History and durable project Memory.
How to run each
humwork As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install humwork@claude-communityWorkfile As a local MCP server: npm package
claude mcp add --transport stdio workfile -- npx -y @illodev/workfile mcpCommands 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: humwork · What it can do: Workfile · 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. 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.