Ext Ops Panel
Open dashboard
Comparison

vault-pkm vs WhyNote

vault-pkm is a plugin bundle for AI coding tools published by AdrianV101. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). WhyNote is an MCP server published by Coooolinz. 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
Marketplacevault-pkmWhyNote
Claude Code: claude-plugins-community Listed
Version: 3.10.1
Forks (GitHub): 3
Stars (GitHub): 14
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Downloads/month (npm): 111
Downloads/week (npm): 20
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

vault-pkm vs WhyNote
Factvault-pkmWhyNote
Marketplaces that list it11
Stars (GitHub) (differs)14 (better)0 (worse)
Forks (GitHub) (differs)3 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (obsidian-pkm)On your machine (why-note-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 02, secrets among them: 1
Hooks it runs (differs)2Not published
Parts of the bundle (differs)14Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/adrianv101/obsidian-pkm-plugingithub.com/coooolinz/why-note-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

vault-pkm

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

Personal knowledge management for Claude Code. Connect to your Obsidian vault with 20 MCP tools, semantic search, wikilink graph traversal, template-based note creation, link health audits, and cross-session activity logging. Includes 3 autonomous agents and hooks for proactive knowledge capture.

WhyNote

In its own words, on Official MCP Registry:

Read-only search, todo listing, and daily note access for a WhyNote account

How to run each

vault-pkm As a Claude Code plugin

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

WhyNote As a local MCP server: npm package

Claude Code
claude mcp add --env "NOTE_TOKEN=<YOUR_NOTE_TOKEN>" --env "NOTE_URL=<YOUR_NOTE_URL>" --transport stdio why-note -- npx -y why-note-mcp

Requires: NOTE_TOKEN (secret), NOTE_URL

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 vault-pkm asks for

  • VAULT_PATH

Only WhyNote asks for

  • NOTE_TOKEN (secret)
  • NOTE_URL

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

What it can do: vault-pkm · What it can do: WhyNote · 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