Compared · obsidian
14 Obsidian MCP servers. Which one to use.
Every Obsidian server we index, with whether its source is still reachable and whether we hold a screening verdict. None currently carry a source-liveness flag.
Scope: 14 servers, mostly mirrored from the MCP registry as of 2026-08-13. Most servers whose authors never published to the registry are absent, so treat this as close to the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| Obsidian Everywhere | io.github.junnnnnw00 | no flag | REVIEW | 95 | npm obsidian-everywhere |
| Obsidian Vault MCP | io.github.luffysolution-svg | no flag | REVIEW | 95 | pypi zotero-obsidian-mcp |
| Obsidian Brain | io.github.sweir1 | no flag | REVIEW | 91 | npm obsidian-brain |
| Obsidian Hybrid Search | io.github.flowing-abyss | no flag | REVIEW | 90 | npm obsidian-hybrid-search |
| Obsidian Regulatory MCP | io.github.richbile | no flag | REVIEW | 88 | remote endpoint |
| Obsidian Vault MCP Server | io.github.OleksandrKucherenko | no flag | REVIEW | 87 | npm @oleksandrkucherenko/mcp-obsidian |
| io.github.cyanheads/obsidian-mcp-server | io.github.cyanheads | no flag | REVIEW | 85 | npm obsidian-mcp-server |
| io.github.stonematt/mcp-obsidian-cli | io.github.stonematt | no flag | REVIEW | 85 | npm mcp-obsidian-cli |
| Obsidian Semantic Search | io.github.DalecB | no flag | REVIEW | 82 | npm @dalecb/obsidian-semantic-mcp |
| Obsidian MCP | io.github.seynurmammad0v | no flag | REVIEW | 81 | npm @smammadov/obsidian-mcp |
| io.github.dewtech-technologies/obsidian-mcp-secure | io.github.dewtech-technologies | no flag | REVIEW | 79 | npm obsidian-mcp-secure |
| io.github.es617/obsidian-sync-mcp | io.github.es617 | no flag | REVIEW | 72 | npm obsidian-sync-mcp |
| ai.smithery/sunub-obsidian-mcp-server | ai.smithery | no flag | REVIEW | 63 | remote endpoint |
| ai.smithery/Hint-Services-obsidian-github-mcp | ai.smithery | no flag | REVIEW | 57 | remote endpoint |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.