Shodh Memory vs Memory Os Cli — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Shodh Memory vs Memory Os Cli
In-depth architectural comparison of the Shodh Memory 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
Shodh Memory
Knowledge & Memory · Local stdio
Quality: 69/100 (Great) | Auth: No auth required
Memory Os Cli
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: other
Verdict Summary: Choose Shodh Memory 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 Shodh Memory 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).
Cognitive memory for AI agents with Hebbian learning, 3-tier architecture, and knowledge graphs. Single 15MB binary, runs offline on edge devices.
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
Shodh Memory Tools (38)
remember
Store a memory for future recall. Use this to remember important information, decisions, user preferences, project context, or anything you want to recall later.
recall
Search memories AND todos using semantic similarity. Returns both relevant memories and matching todos. Use this to find past experiences, decisions, context, or pending work. Modes: 'semantic' (vector similarity), 'associative' (graph traversal), 'temporal' (time-based retrieval), 'hybrid' (combined), 'spatial' (geo-location based), 'mission' (mission context), 'action_outcome' (reward-based learning).
recall_by_tags
Find memories by tags. Returns memories matching ANY of the provided tags. Useful for finding memories by category (e.g., 'tool:Edit', 'file:src/main.rs', 'source:hook', 'error', 'session-summary').
context_summary
Get a condensed summary of recent learnings, decisions, and context. Use this at the start of a session to quickly understand what you've learned before.
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).
Shodh Memory 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 Shodh Memory when you need capabilities focused on knowledge & memory and Memory Os Cli when you require tools for knowledge & memory.
Verify vector index integrity - diagnose orphaned memories that are stored but not searchable. Returns health status and count of orphaned memories.
repair_index
Repair vector index by re-indexing orphaned memories. Use this when verify_index shows unhealthy status. Returns count of repaired memories.
backup_create
Create a backup of all memories. Returns backup metadata including ID, size, and checksum. Backups are stored locally and can be restored later.
backup_list
List all available backups for this user. Returns backup history with IDs, timestamps, and sizes.
backup_verify
Verify backup integrity using SHA-256 checksum. Use to check if a backup is corrupted before restoring.
+26 more tools listed on main page
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.