Ext Ops Panel
Open dashboard
Comparison

@bitbonsai/mcpvault vs Notes Vault

@bitbonsai/mcpvault is an MCP server published by bitbonsai. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Notes Vault is an MCP server published by gronare. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-30. 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@bitbonsai/mcpvaultNotes Vault
npm registry (MCP servers) Listed
Version: 0.17.1
Downloads/month (npm): 41 143
Downloads/week (npm): 31 065
Forks (GitHub): 133
Stars (GitHub): 1 705
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.8.0
Downloads/month (PyPI): 1 663
Downloads/week (PyPI): 156
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.8.0
Downloads/month (PyPI): 1 663
Downloads/week (PyPI): 156
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

@bitbonsai/mcpvault vs Notes Vault
Fact@bitbonsai/mcpvaultNotes Vault
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)1 705 (better)0 (worse)
Forks (GitHub) (differs)133 (better)0 (worse)
Last release (differs)2026-10-23 (worse)2026-10-23 (better)
Where it runs (differs)On your machine (@bitbonsai/mcpvault)On your machine (notes-vault-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published11, secrets among them: 3
LicenceMITMIT
Repository (differs)github.com/bitbonsai/mcpvaultgithub.com/gronare/notes-vault-mcp
Changes in the last 7 days (differs)12
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

@bitbonsai/mcpvault

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

Universal AI bridge for Obsidian vaults - connect any MCP-compatible assistant

Notes Vault

In its own words, on Official MCP Registry:

Indexed search, schema-checked writes and session hooks for a markdown notes vault

How to run each

@bitbonsai/mcpvault

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

Notes Vault As a local MCP server: PyPI package

Claude Code
claude mcp add --env "S3_ACCESS_KEY=<YOUR_S3_ACCESS_KEY>" --env "S3_SECRET_KEY=<YOUR_S3_SECRET_KEY>" --env "VAULT_TOKEN=<YOUR_VAULT_TOKEN>" --transport stdio notes-vault-mcp -- uvx notes-vault-mcp

Requires: S3_ACCESS_KEY (secret), S3_SECRET_KEY (secret), VAULT_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

The marketplaces of @bitbonsai/mcpvault publish no settings it asks for, so we do not compare settings.

What it can do: @bitbonsai/mcpvault · What it can do: Notes Vault · 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. Package data comes from the Python Package Index (pypi.org). 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