Ext Ops Panel
Open dashboard
Comparison

Workfile vs Pride

Workfile is an MCP server published by illodev. Marketplaces we read that list it: 1 (Official MCP Registry). Pride is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
MarketplaceWorkfilePride
Official MCP Registry Listed
Version: 0.13.2
Downloads/month (npm): 1 508
Downloads/week (npm): 272
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 0.1.2
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

Workfile vs Pride
FactWorkfilePride
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@illodev/workfile)Remote server (gateway.pipeworx.io/pride/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/illodev/workfilegithub.com/pipeworx-io/mcp-pride
Changes in the last 7 days (differs)40
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago

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

Workfile

In its own words, on Official MCP Registry:

Repository-native protocol and local MCP server for Work, Docs, History and durable project Memory.

Pride

In its own words, on Official MCP Registry:

EBI PRIDE Archive MCP — proteomics (mass-spectrometry) data repository.

How to run each

Workfile As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio workfile -- npx -y @illodev/workfile mcp

Pride As a remote MCP server

Claude Code
claude mcp add --transport http pride https://gateway.pipeworx.io/pride/mcp

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

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

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: Workfile · What it can do: Pride · Compare two other plugins

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.

Where the data comes from: how the catalog is built