Mnemo MCP vs Mnemos — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mnemo MCP vs Mnemos
In-depth architectural comparison of the Mnemo MCP 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
Mnemo MCP
Knowledge & Memory · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Mnemos
Knowledge & Memory · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Mnemo MCP 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 Mnemo MCP 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 have access to required keys: MNEMO_MCP_RCLONE_REMOTE, MNEMO_MCP_SYNC_PASSPORT_KEY, MNEMO_MCP_DB_PATH, MNEMO_MCP_LOG_LEVEL.
Persistent AI memory with SQLite hybrid search (FTS5 + semantic). Built-in Qwen3 embedding, rclone sync across machines. Zero config, no cloud, no limits.
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
Mnemo MCP Tools (3)
config
Server status, trigger sync, update settings, pre-download embedding model, authenticate sync provider, manage HTTP setup form lifecycle, passport export/import
help
Full documentation for any tool
config__open_relay
Open the zero-config relay setup form (registered via mcp-core)
Mnemos Tools (9)
mnemos_store
Store a memory (full auto-pipeline runs transparently)
mnemos_search
Hybrid FTS + semantic + file-overlap search
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).
Mnemo MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Mnemos belongs to Knowledge & Memory using local stdio subprocess. Select Mnemo MCP when you need capabilities focused on knowledge & memory and Mnemos when you require tools for knowledge & memory.