Agent Recall vs Shodh Memory
A side-by-side look at the Agent Recall and Shodh Memory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agent Recall for knowledge & memory work as a local process; choose Shodh Memory for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agent Recall when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
session_start, session_end, remember.
Choose Shodh Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
remember, recall, recall_by_tags.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 71/100 · Great | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 373 | 322 |
| Directory activity | 8 views 0 installs 0 upvotes | 8 views 0 installs 0 upvotes |
| Tools | 5 | 38 |
| Full listing | View Agent Recall | View Shodh Memory |
Tools & capabilities
Agent Recall tools 5
session_start[ENTRY — call FIRST, before acting] Use when the user asks to start, load, continue, resume, or open memory for a project. Set mode='lite' for a ≤500-token briefing (good for fresh conversations where the agent will pull memory on demand via recall()).session_end[ON SAVE/EXIT — YOU must call this; nothing auto-saves] Use when the user asks to save, checkpoint, summarize, end, retain, or persist the current session. Optionally pass close_phase / open_phase to update the project pipeline narrative spine in the same call.remember[MID-SESSION WRITE — single fact/decision; saying it is not saving it] Use when the user asks to remember, store, note, or save a specific decision, fact, or insight.recall[RETRIEVE — use freely, any time] Use when the user asks to recall, search, find, or look up previous memory, context, or decisions.check[MID-SESSION — safe any time; for alignment, before risky decisions] Use when the user asks to validate understanding, verify alignment, or check if their interpretation matches the human's intent. Also call BEFORE a high-risk action — publish, deploy, delete, credential exposure, external send/message, or any other irreversible write — passing `action_description` (one sentence, what you're about to do). Returns matching corrections/rules/insights plus a `verdict`: `blocked` means an authoritative correction OVERRIDES the plan — read it before proceeding. To RECORD a durable human correction, pass `human_correction` as the STRUCTURED object {rule, why, applies_when} — a plain string is only STAGED for later review, never activated.
Shodh Memory tools 38
rememberStore a memory for future recall. Use this to remember important information, decisions, user preferences, project context, or anything you want to recall later.recallSearch 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_tagsFind 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_summaryGet 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.list_memoriesList all stored memoriesforgetDelete a specific memory by IDmemory_statsGet statistics about stored memoriesverify_indexVerify vector index integrity - diagnose orphaned memories that are stored but not searchable. Returns health status and count of orphaned memories.repair_indexRepair vector index by re-indexing orphaned memories. Use this when verify_index shows unhealthy status. Returns count of repaired memories.backup_createCreate a backup of all memories. Returns backup metadata including ID, size, and checksum. Backups are stored locally and can be restored later.backup_listList all available backups for this user. Returns backup history with IDs, timestamps, and sizes.backup_verifyVerify backup integrity using SHA-256 checksum. Use to check if a backup is corrupted before restoring.- +26 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Agent Recall
{
"mcpServers": {
"agent-recall": {
"command": "npx",
"args": [
"-y",
"agent-recall-mcp"
]
}
}
}
Shodh Memory
{
"mcpServers": {
"varun29ankus-shodh-memory": {
"command": "npx",
"args": [
"-y",
"@shodh/memory-mcp"
]
}
}
}
Frequently asked questions
Agent Recall is categorized under Knowledge & Memory and uses a local stdio subprocess. Shodh Memory belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Agent Recall for knowledge & memory work and Shodh Memory for knowledge & memory.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Agent Recall is listed as free. Auth: no auth required. Shodh Memory is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add agent-recall and varun29ankus-shodh-memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agent Recall has a quality signal of 71/100 (Great) with 8 views, 0 installs and 373 GitHub stars. Shodh Memory has 69/100 (Great) with 8 views, 0 installs and 322 GitHub stars.