0CompactMem vs YourMemory — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
0CompactMem vs YourMemory
In-depth architectural comparison of the 0CompactMem and YourMemory 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
0CompactMem
Knowledge & Memory · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
YourMemory
Knowledge & Memory · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose 0CompactMem if you need specialized Knowledge & Memory tools running via a local process. Choose YourMemory 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 0CompactMem 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).
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: Ebbinghaus forgetting-curve memory decay and pruning, Hybrid retrieval combining BM25, vector embeddings, and entity graph, Consolidation of related facts into summaries to reduce bloat.
Persistent memory MCP server with OS-style demand paging, kswapd-style eviction, and mlock pinning. Multi-agent shared SQLite store with BM25 + FTS5 retrieval, importance scoring, and capacity-aware reclaim. 5 tools: memorylookup, pinmemory, unpinmemory, memorystats, listpinned. uvx --from git+https://github.com/soolaugust/0CompactMem memory-os
Persistent memory for AI agents with Ebbinghaus forgetting-curve decay, hybrid BM25+vector retrieval, and entity graph for multi-hop reasoning. Memories auto-prune by importance and recall rate. Built-in browser dashboard, multi-agent support, and yourmemory ask for zero-API-call local queries. pip install yourmemory
Tools & Capabilities Breakdown
0CompactMem Tools (6)
SQLite WAL-backed persistent storage
BM25 and FTS5 memory retrieval
Importance-based scoring
Capacity-aware memory reclaim
Memory pinning and unpinning
Five MCP tools for lookup, pinning, statistics, and listing
YourMemory Tools (6)
Ebbinghaus forgetting-curve memory decay and pruning
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
0CompactMem is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, YourMemory belongs to Knowledge & Memory using local stdio subprocess. Select 0CompactMem when you need capabilities focused on knowledge & memory and YourMemory when you require tools for knowledge & memory.