Mneme vs MarsNMe — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mneme vs MarsNMe
In-depth architectural comparison of the Mneme and MarsNMe 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
Mneme
Knowledge & Memory · Local stdio
Quality: 48/100 (Fair) | Auth: No auth required
MarsNMe
Knowledge & Memory · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Mneme if you need specialized Knowledge & Memory tools running via a local process. Choose MarsNMe 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 Mneme 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).
FTS5 BM25 retrieval over the vault with Turkish casefold normalization, plus date, memory-type, and scope filters. Returns ranked hits and EvidenceCards carrying content hashes, trust, confidence, and the backend that actually ran.
mneme_recall
Retrieves indexed documents by session identifier, date range, and scope. Returns paths, titles, modification times, memory types, and optionally the full markdown body.
mneme_write
Atomically appends or replaces a markdown section in a vault file. Enforces vault path containment and redacts private spans before storage.
mneme_summarize
Groups FTS5 matches for a topic by vault directory within optional date and scope filters. Graphiti enrichment appears only when that optional local graph integration is configured.
mneme_timeline
Returns scope-restricted references for a subject in chronological order. Graphiti facts and bi-temporal filtering appear only when the optional local graph integration is available.
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).
Mneme is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, MarsNMe belongs to Knowledge & Memory using local stdio subprocess. Select Mneme when you need capabilities focused on knowledge & memory and MarsNMe when you require tools for knowledge & memory.
Builds a token-budgeted preflight context bundle from recent sessions and topic-relevant matches. A caller session identifier enables per-session injection deduplication and full, keypoints, or reference formatting.
mneme_propose
Queues a redacted memory-edit proposal for the policy drain. The server does not apply the edit directly; durable categories always require human approval.
mneme_checkpoint_list
Lists recent Context Continuity Engine checkpoints from the active scope, newest first. Missing checkpoint state returns an empty list.
mneme_working_set_load
Loads salience-ranked working-set items from a Context Continuity Engine checkpoint. Unknown and out-of-scope anchors return the same neutral not-found result.
MarsNMe Tools (16)
insert_memory
Store short-term memory
list_memories
List recent memories
search_memories
Semantic search via Jina embeddings
recall
Long-term chunk recall — ~80-char preview per match
get_summary
Medium excerpt (~300 chars) of a chunk by ID
get_full
Complete text of a long-term chunk by ID
memory_ingest
Ingest long-term insight chunks
dream_ingest
Dream-mode long-term ingestion
session_boot
Start a session with context pre-load
session_close
Close session, summarize, auto-promote expiring memories