@bitbonsai/mcpvault vs io.github.cyanheads/obsidian-mcp-server
@bitbonsai/mcpvault is an MCP server published by bitbonsai. Marketplaces we read that list it: 1 (npm registry (MCP servers)). io.github.cyanheads/obsidian-mcp-server is an MCP server published by cyanheads. Marketplaces we read that list it: 2 (Official MCP Registry, 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 |  @bitbonsai/mcpvault |  io.github.cyanheads/obsidian-mcp-server |
|---|---|---|
| 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 |
Listed Version: 3.7.2 Downloads/month (npm): 24 610 Downloads/week (npm): 1 597 Forks (GitHub): 108 Stars (GitHub): 700 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 3.7.2 Downloads/month (npm): 24 610 Downloads/week (npm): 1 597 Forks (GitHub): 108 Stars (GitHub): 700 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 | @bitbonsai/mcpvault | io.github.cyanheads/obsidian-mcp-server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 705 (better) | 700 (worse) |
| Forks (GitHub) (differs) | 133 (better) | 108 (worse) |
| Last release (differs) | 2026-10-23 (worse) | 2026-10-26 (better) |
| Where it runs (differs) | On your machine (@bitbonsai/mcpvault) | On your machine (obsidian-mcp-server) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 16, secrets among them: 0 |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/bitbonsai/mcpvault | github.com/cyanheads/obsidian-mcp-server |
| Changes in the last 7 days (differs) | 1 | 4 |
| First seen (differs) | 2026-10-12 | 2026-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
Universal AI bridge for Obsidian vaults - connect any MCP-compatible assistant
io.github.cyanheads/obsidian-mcp-server
Read, write, search, and surgically edit Obsidian notes, tags, and frontmatter via MCP.
How to run each
@bitbonsai/mcpvault
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.cyanheads/obsidian-mcp-server As a local MCP server: npm package
claude mcp add --env "OBSIDIAN_API_KEY=<YOUR_OBSIDIAN_API_KEY>" --transport stdio obsidian-mcp-server -- npx -y obsidian-mcp-serverRequires: OBSIDIAN_API_KEY
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: io.github.cyanheads/obsidian-mcp-server · 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.