In-depth architectural comparison of the MCP Obsidian and MCP Curiosity Engine 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
MCP Curiosity Engine
Knowledge & Memory · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Verdict Summary: Choose MCP Obsidian if you need specialized Knowledge & Memory tools running via a local process. Choose MCP Curiosity Engine 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.
Surface the notes you forgot you wrote — DMN replay for markdown vaults.
MCP Obsidian is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, MCP Curiosity Engine belongs to Knowledge & Memory using local stdio subprocess. Select MCP Obsidian when you need capabilities focused on knowledge & memory and MCP Curiosity Engine when you require tools for knowledge & memory.
List notes that are structurally dormant — low incoming wikilink count AND old mtime. These are the notes most at risk of being forgotten.
find_orphan_notes
List notes with zero incoming wikilinks — structurally isolated, the extreme case of dormancy.
suggest_replay_cycle
Run the full DMN-inspired replay cycle: sample dormant notes with bias (40% random / 30% least-linked / 30% orphans), extract their concepts, generate cross-domain bridge queries between them, return notes to revisit. The core moat.
find_cross_domain_bridges
Surface pairs of notes from DIFFERENT top-level directories that share concepts. These are the surprise connections — ideas that span your vault's silos.
random_deep_cut
Pull a single random dormant note for serendipitous rediscovery. Think of it as your vault's shuffle-play button.