MCP Obsidian vs Memory — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
MCP Obsidian vs Memory
In-depth architectural comparison of the MCP Obsidian and Memory MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Obsidian
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Memory
Knowledge & Memory · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Verdict Summary: Choose MCP Obsidian if you need specialized Knowledge & Memory tools running via a local process. Choose Memory if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Obsidian when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Local stdio MCP access to an Obsidian vault, Note reading, writing, patching, moving, and deletion, Multi-word search with BM25 reranking.
Universal AI bridge for Obsidian vaults using MCP. Provides safe read/write access to notes with 11 comprehensive methods for vault operations including search, batch operations, tag management, and frontmatter handling. Works with Claude, ChatGPT, and any MCP-compatible AI assistant.
MCP Obsidian is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Memory belongs to Knowledge & Memory using local stdio subprocess. Select MCP Obsidian when you need capabilities focused on knowledge & memory and Memory when you require tools for knowledge & memory.
Flagship.** One call returns everything needed to understand this user for a query — relevant memories + profile + confirmed facts + behavioral inferences (plus counterfactual & cross-domain hints). Drop straight into any LLM's context.
zhiji_memory_search
Lighter, recall-only: the 11-stage hybrid pipeline (trigram FTS + semantic + time-decay), returns scored snippets with sources.
zhiji_profile_get
7-layer / 37-dim user profile as an inject-ready natural-language summary.
zhiji_facts_get
Structured atomic facts (subject attribution, confidence, conflict status) — for exact names/dates/counts, not narrative.
zhiji_prospective_due
Due/upcoming intentions (todos, promises, plans) within a time window — for proactively nudging the user.
zhiji_memory_ingest
Write a conversation turn to long-term memory; async embedding + profile/fact extraction + importance scoring follow. **Text only.
zhiji_ingest_file
Multimodal ingest — audio / image / PDF / Word / Excel / video → Whisper transcribe / Tesseract OCR / doc parse → memory. Audio & video also get acoustic-emotion analysis.
zhiji_feedback
Thumbs up/down on the last recall/answer → feeds the self-evolution reward and reinforces (or penalizes) the Q-value of recently retrieved memories. The "gets better the more you use it" loop.
zhiji_status
Health & memory scale (files / chunks / FTS availability). Call first to verify connectivity.