Ext Ops Panel
Open dashboard
Comparison

@bilig/headless vs Bilig WorkPaper

@bilig/headless is an MCP server published by @bilig. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Bilig WorkPaper is an MCP server published by proompteng. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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
Marketplace@bilig/headlessBilig WorkPaper
npm registry (MCP servers) Listed
Version: 0.164.11
Downloads/month (npm): 59 801
Downloads/week (npm): 7 723
Forks (GitHub): 18
Stars (GitHub): 35
Not marked · First seen
Listed
Version: 1.1.2
Downloads/month (npm): 936
Downloads/week (npm): 226
Forks (GitHub): 18
Stars (GitHub): 35
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 1.1.0
Downloads/month (npm): 936
Downloads/week (npm): 226
Forks (GitHub): 18
Stars (GitHub): 35
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

@bilig/headless vs Bilig WorkPaper
Fact@bilig/headlessBilig WorkPaper
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)3535
Forks (GitHub)1818
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@bilig/headless)Remote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceMITMIT
Repositorygithub.com/proompteng/biliggithub.com/proompteng/bilig
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 16 h 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

@bilig/headless

In its own words, on npm registry (MCP servers):

Lower-level WorkPaper formula runtime for Node services with JSON persistence and verified formula readback.

Bilig WorkPaper

In its own words, on Official MCP Registry:

Formula-backed WorkPaper tools for workbook readback, input edits, and JSON persistence.

How to run each

@bilig/headless

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Bilig WorkPaper As a remote MCP server

Claude Code
claude mcp add --transport http bilig-workpaper https://bilig.proompteng.ai/mcp

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

Only Bilig WorkPaper 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: @bilig/headless · What it can do: Bilig WorkPaper · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). 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