YourMemory vs Being — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
YourMemory vs Being
In-depth architectural comparison of the YourMemory and Being 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
YourMemory
Knowledge & Memory · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Being
Knowledge & Memory · Remote HTTP/SSE
Quality: 45/100 (Fair) | Auth: API Key required
Verdict Summary: Choose YourMemory if you need specialized Knowledge & Memory tools running via a local process. Choose Being if your workspace requires Knowledge & Memory integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose YourMemory 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: 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 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
Personality Runtime for AI agents — persistent memory, identity (SOUL), and relationships that travel across Claude, OpenClaw, Mistral, and any MCP client.
Category & Scope
Tools & Capabilities Breakdown
YourMemory Tools (6)
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
Tamper-evident hash-chained audit trail of memory operations
Role-based team memory pools with privacy controls
Local-first operation with zero API key requirement
Being Tools (6)
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).
YourMemory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Being belongs to Knowledge & Memory using remote streaming HTTP/SSE transport. Select YourMemory when you need capabilities focused on knowledge & memory and Being when you require tools for knowledge & memory.