Engram MCP vs Memory Os Cli — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Engram MCP vs Memory Os Cli
In-depth architectural comparison of the Engram MCP and Memory Os Cli 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
Engram MCP
Knowledge & Memory · Local stdio
Quality: 42/100 (Fair) | Auth: No auth required
Memory Os Cli
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: other
Verdict Summary: Choose Engram MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Memory Os Cli 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 Engram 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: ENGRAM_DB, ENGRAM_EMBEDDING_URL.
Persistent semantic memory for AI agents. SQLite-backed, local-first, zero config. Semantic search via Ollama embeddings (nomic-embed-text) with keyword fallback. remember, recall, history, forget, and stats tools. Works with Claude Desktop, Cursor, and any MCP client.
XMemo is user-owned memory for AI agents over a hosted Streamable HTTP MCP endpoint. Save, search, recall, and manage scoped memories across Copilot, Claude, ChatGPT, IDEs, and CLIs. https://xmemo.dev/mcp
Category & Scope
Tools & Capabilities Breakdown
Engram MCP Tools (11)
remember
Store a new memory with automatic entity extraction, theme detection, and relationship mapping.
recall
Retrieve relevant memories with entity, theme, and emotional context. Returns 360° relational intelligence around the query.
search
Raw hybrid search with pagination and filtering. Use for precise control over results.
context
Get 360° context around a specific entity, theme, or memory. Returns timeline, relationships, emotional arc, and key memories.
impact
Analyze how a new piece of information would affect existing memory structure. Detects conflicts, affected entities, and themes before storing.
detect_changes
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).
Engram MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Memory Os Cli belongs to Knowledge & Memory using local stdio subprocess. Select Engram MCP when you need capabilities focused on knowledge & memory and Memory Os Cli when you require tools for knowledge & memory.
Compare recent memory activity against a baseline period to identify new entities, theme shifts, emotional changes, and anomalies.
consolidate
Consolidate working memories into long-term storage. Archives old memories beyond the keep threshold.
process_detect
Identify recurring conversation and behavior patterns: decision loops, planning sessions, learning moments, and conflict patterns.
forget
Delete memories matching criteria. Requires confirm: true. This is irreversible.
stats
Get memory statistics for a session: counts by role/tier, embeddings coverage, importance scores, and graph metrics.
graph
Query the entity relationship graph. Find connections, relationships, and paths between entities.
Memory Os Cli Tools (20)
get_mcp_identity
Check XMemo connection status and the connected account/agent.
remember
Save a memory so it can be recalled in future conversations.
recall
Recall the most relevant saved memories before answering.
recall_context
Read a multi-memory context pack. Requires memory:read and does not change content. Use when many memories need explicit budgets; use recall for lightweight answer or get_project_context for project snapshot. max_items/max_tokens bound rendered output.
memory_stats
Show aggregate statistics for XMemo memories.
update_memory
Update the content or metadata of an existing memory.
explain_memory
Explain why a memory exists or matched a query.
restore_memory
Restore a previously deleted memory.
add_expense
Create one XMemo Ledger transaction and backing memory. Requires memory:write; it records a new transaction or reuses a semantic duplicate, and never deletes Ledger records. Use it for a purchase, income, refund, or transfer; use list_ledger_transactions or get_monthly_ledger_summary for reads. amount must be positive; transaction_type defaults to expense; blank transaction_date uses today's UTC date.