Plur vs YourMemory — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Plur vs YourMemory
In-depth architectural comparison of the Plur 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
Plur
Knowledge & Memory · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
YourMemory
Knowledge & Memory · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Plur 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 Plur 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).
Plur is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, YourMemory belongs to Knowledge & Memory using local stdio subprocess. Select Plur when you need capabilities focused on knowledge & memory and YourMemory when you require tools for knowledge & memory.
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP.
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