In-depth architectural comparison of the Mcp Obsidian and Mcp Agent 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: 67/100 (Great) | Auth: No auth required
Mcp Agent Memory
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Mcp Obsidian if you need specialized Knowledge & Memory tools running via a local process. Choose Mcp Agent 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: Safe YAML frontmatter parsing and AST-aware updates, File operations: read, write, patch, delete, move notes/files, Partial reads: get note outlines and specific line ranges.
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.
Persistent agent memory via filesystem-native consolidation daemon. Agents read/write/search memory through MCP; a background daemon handles consolidation and extraction. Works with Kiro, Claude Desktop, Cursor, and any MCP client. npx mcp-agent-memory --setup
Category & Scope
Tools & Capabilities Breakdown
Mcp Obsidian Tools (6)
Safe YAML frontmatter parsing and AST-aware updates
Mcp Obsidian is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Mcp Agent Memory belongs to Knowledge & Memory using local stdio subprocess. Select Mcp Obsidian when you need capabilities focused on knowledge & memory and Mcp Agent Memory when you require tools for knowledge & memory.
Read the agent memory index (MEMORY.md) and optionally specific topic files. Call with no arguments to load only the lightweight index (cheap). Pass `topics` only when you need the full content of a specific topic file.
memory_append_session
Append a session summary to the sessions directory. The daemon will later extract durable memories from it. Call this at the end of meaningful exchanges. Keep summaries focused on durable findings and decisions (target 300-800 tokens), not play-by-play — longer summaries cost more during consolidation.
memory_search
Search memory files for a substring. Use this to recall specific facts without loading everything.
memory_daemon_status
Check whether the memory consolidation daemon is running. Reports if the daemon is not installed or not available on this platform.