Ext Ops Panel
Open dashboard
Comparison

LINZA vs io.github.yuque/yuque-mcp

LINZA is an MCP server published by Semiotronika. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.yuque/yuque-mcp is an MCP server published by yuque. Marketplaces we read that list it: 1 (Official MCP Registry). 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
MarketplaceLINZAio.github.yuque/yuque-mcp
Official MCP Registry Listed
Version: 0.2.2
Downloads/month (PyPI): 128
Downloads/week (PyPI): 50
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen
Listed
Version: 0.1.4
Downloads/month (npm): 1 650
Downloads/week (npm): 572
Forks (GitHub): 28
Stars (GitHub): 263
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

LINZA vs io.github.yuque/yuque-mcp
FactLINZAio.github.yuque/yuque-mcp
Marketplaces that list it11
Stars (GitHub) (differs)4 (worse)263 (better)
Forks (GitHub) (differs)0 (worse)28 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (linza-mcp)On your machine (yuque-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)9, secrets among them: 13, secrets among them: 3
LicenceNot statedNot stated
Repository (differs)github.com/semiotronika/linza-mcpgithub.com/yuque/yuque-mcp-server
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

LINZA

In its own words, on Official MCP Registry:

Local-first MCP sidecar for Markdown artifacts, review intents, and supervised knowledge growth.

io.github.yuque/yuque-mcp

In its own words, on Official MCP Registry:

MCP server for Yuque — expose your knowledge base to AI assistants.

How to run each

LINZA As a local MCP server: PyPI package

Claude Code
claude mcp add --env "LINZA_EMBED_KEY=<YOUR_LINZA_EMBED_KEY>" --transport stdio linza-mcp -- uvx linza-mcp

Requires: LINZA_EMBED_KEY (secret)

io.github.yuque/yuque-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "YUQUE_GROUP_TOKEN=<YOUR_YUQUE_GROUP_TOKEN>" --env "YUQUE_PERSONAL_TOKEN=<YOUR_YUQUE_PERSONAL_TOKEN>" --env "YUQUE_TOKEN=<YOUR_YUQUE_TOKEN>" --transport stdio yuque-mcp -- npx -y yuque-mcp

Requires: YUQUE_GROUP_TOKEN (secret), YUQUE_PERSONAL_TOKEN (secret), YUQUE_TOKEN (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

Only LINZA asks for

  • LINZA_BRIDGE_THRESHOLD
  • LINZA_DEFAULT_PROFILE
  • LINZA_EMBED_KEY (secret)
  • LINZA_EMBED_MODEL
  • LINZA_EMBED_PROVIDER
  • LINZA_EMBED_URL
  • LINZA_LANGUAGE
  • LINZA_MAX_BRIDGE_PAIRS
  • LINZA_VAULT

Only io.github.yuque/yuque-mcp asks for

  • YUQUE_GROUP_TOKEN (secret)
  • YUQUE_PERSONAL_TOKEN (secret)
  • YUQUE_TOKEN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: LINZA · What it can do: io.github.yuque/yuque-mcp · Compare two other plugins

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