obsidian-mcp-plugin
Provides an MCP (Model Context Protocol) server for Obsidian that exposes semantic, graph-aware tools for an AI assistant to read, search, and modify content in an Obsidian vault over HTTP transport (optionally with HTTPS).
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Based on provided documentation only: authentication is an API key sent via Authorization: Bearer header. README mentions HTTPS and 'Path validation and permissions' and a read-only mode, but the supplied content does not detail TLS enforcement behavior, credential storage, logging/telemetry redaction, authorization model granularity, or explicit rate-limiting. Given the plugin enables vault write/edit, additional validation of tool-level authorization and server exposure is important.
⚡ Reliability
Best When
You want local/offline-style, AI tool access to your own Obsidian vault with graph traversal and semantic operations via MCP-compatible clients.
Avoid When
You cannot safely expose vault access (write/edit) to an AI client, or you cannot validate/contain the MCP server’s HTTP exposure and credentials.
Use Cases
- • Ask questions over an Obsidian knowledge graph with semantic search and link traversal
- • Summarize or synthesize notes across related topics and backlinks
- • Find connections between notes and map multi-hop paths in the vault graph
- • Execute note queries via Dataview integration (if installed)
- • Query and export data from Obsidian Bases (if available)
- • Create or edit notes with structure-aware operations (read-only mode available)
Not For
- • Use where you need strong enterprise-grade API governance (RBAC, audit logging) without further review
- • Environments where local vault file access must be strictly minimized or isolated
- • Use cases requiring guaranteed backward/forward compatibility of the exposed tool contracts across versions without testing
Interface
Authentication
README indicates an API key is used for the MCP server over HTTP headers. It does not clearly document fine-grained permissions/scopes at the client level.
Pricing
No pricing information is provided in the supplied content; this appears to be a local/community plugin.
Agent Metadata
Known Gotchas
- ⚠ Write/edit tools can modify vault content; use read-only mode when validating agent behavior
- ⚠ HTTP exposure of the local MCP server requires careful network binding and credential handling
- ⚠ Graph traversal and semantic search may be computationally heavy on large vaults; agents may need to limit traversal depth
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for obsidian-mcp-plugin.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.