Perseus Vault vs Mnemos — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Perseus Vault vs Mnemos
In-depth architectural comparison of the Perseus Vault and Mnemos 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
Perseus Vault
Knowledge & Memory · Local stdio
Quality: 35/100 (Fair) | Auth: No auth required
Mnemos
Knowledge & Memory · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Perseus Vault if you need specialized Knowledge & Memory tools running via a local process. Choose Mnemos 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 Perseus Vault 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: Embedded SQLite storage, BM25 and dense-vector hybrid recall, Bi-temporal history and lifecycle management.
Local-first, MCP-native persistent memory for AI agents — a single Rust binary with embedded SQLite, hybrid FTS5 + dense-vector search, and optional AES-256-GCM encryption. Fully offline, no cloud.
Persistent memory engine for AI coding agents. Stores architecture decisions, bug root causes, and project conventions across sessions. Single Go binary with embedded SQLite, FTS5 search, context assembly within token budgets, and autopilot setup for Claude Code, Kiro, and Cursor.
Category & Scope
Tools & Capabilities Breakdown
Perseus Vault Tools (6)
Embedded SQLite storage
BM25 and dense-vector hybrid recall
Bi-temporal history and lifecycle management
AES-256-GCM encryption at rest
MCP over standard input and output
Optional client hooks and rules
Mnemos Tools (9)
mnemos_store
Store a memory (full auto-pipeline runs transparently)
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).
Perseus Vault is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Mnemos belongs to Knowledge & Memory using local stdio subprocess. Select Perseus Vault when you need capabilities focused on knowledge & memory and Mnemos when you require tools for knowledge & memory.