MCP100 verdict
Give MCP clients scoped access to a local Obsidian vault.
MCP100 Assessment
Editorial verdict
Give MCP clients scoped access to a local Obsidian vault.
Reviewed 2026-07-24 · Next review 2026-10-24
Task Fit
Mapped
Local files and knowledge
Trust
Reviewed
A dated editorial review is published on the MCP detail page.
Maintenance
Activity observed
A dated repository or package update is available; editorial maintenance review is still pending.
Popularity
Signals available
Visible usage signals are shown for discovery only, not as proof of safety.
Best for
- Obsidian users who want local search and supervised note maintenance
- Vaults protected by version control or reliable backups
- Users able to expose only a dedicated, bounded vault
Not ideal for
- Unbacked-up personal knowledge bases
- Read-only research where a simpler filesystem search is sufficient
- Enterprise knowledge requiring centralized authorization and audit controls
Avoid if
- The vault contains secrets, regulated data, or material that cannot reach the selected AI provider
- Write, move, and delete tools cannot be confirmed by a human
- The vault path cannot be narrowed to a dedicated directory
Trade-offs
- Local stdio avoids a hosted MCP service, but note contents still enter the MCP host and model context.
- Frontmatter-aware writes are more useful than generic file access but increase integrity risk.
- npx makes setup simple, while stricter environments may prefer a pinned and reviewed package version.
Evidence scope
Evidence
Popularity
1.6k MCP repository stars
64.1k package downloads
Stars observed 2026-08-14T18:46:26.000Z · Downloads observed 2026-08-14T18:46:26.000Z
Exact implementation repository metric.
Exact implementation package metric.
Maintenance
Publisher activity observed 2026-08-13T12:45:44Z
Current source snapshot
Trust review
Source relationship: Community implementation
Reviewed 2026-07-24 · Next review 2026-10-24