Obsidian vs @bitbonsai/mcpvault
Obsidian is an MCP server published by MarkusPfundstein. Marketplaces we read that list it: 1 (Docker MCP Catalog). @bitbonsai/mcpvault is an MCP server published by bitbonsai. Marketplaces we read that list it: 1 (npm registry (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
| Marketplace |   Obsidian |  @bitbonsai/mcpvault |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:0eba4c05742a Forks (GitHub): 507 Pulls (Docker Hub): 147 854 Stars (Docker Hub): 31 Stars (GitHub): 4 508 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | 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 |
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
| Fact | Obsidian | @bitbonsai/mcpvault |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 508 (better) | 1 705 (worse) |
| Pulls (Docker Hub) (differs) | 147 854 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 507 (better) | 133 (worse) |
| Last release (differs) | Not published | 2026-10-23 |
| Where it runs (differs) | On your machine (mcp/obsidian) | On your machine (@bitbonsai/mcpvault) |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 12 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | MIT | MIT |
| Repository (differs) | github.com/markuspfundstein/mcp-obsidian | github.com/bitbonsai/mcpvault |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-12 |
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
Obsidian
MCP server that interacts with Obsidian via the Obsidian rest API community plugin.
@bitbonsai/mcpvault
Universal AI bridge for Obsidian vaults - connect any MCP-compatible assistant
How to run each
Obsidian As a local MCP server: Docker image
claude mcp add --env "OBSIDIAN_API_KEY=<YOUR_OBSIDIAN_API_KEY>" --transport stdio obsidian -- docker run -i --rm -e OBSIDIAN_API_KEY mcp/obsidianRequires: OBSIDIAN_API_KEY (secret)
@bitbonsai/mcpvault
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of @bitbonsai/mcpvault publish no list of tools, so we do not compare tools.
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: Obsidian · What it can do: @bitbonsai/mcpvault · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.