Th Memory MCP vs Shodh Memory
A side-by-side look at the Th Memory MCP 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 Th Memory MCP 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 Th Memory MCP 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 have the keys it needs:
MEMORY_DB_PATH. - You want tools like
remember, recall, get_profile.
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 | 64/100 · Good | 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 | MEMORY_DB_PATH | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 322 |
| Directory activity | 3 views 0 installs 0 upvotes | 8 views 0 installs 0 upvotes |
| Tools | 16 | 38 |
| Full listing | View Th Memory MCP | View Shodh Memory |
Tools & capabilities
Th Memory MCP tools 16
rememberSave or update a user preference (category+key upsert). Re-saving the same key increases confidence by 0.1 (cap 1.0). Returns the row id for forget().recallSearch preferences + lessons via full-text index, plus recent matching interactions. Use before starting a new task.get_profileGet the distilled user profile: profile sections, top preferences by confidence (max 15), and the 5 most recent lessons. Optional userId/sessionId/projectId scope the auto-projected memories; without them only GLOBAL memories are included.save_lessonRecord a lesson learned from a correction: what situation, what mistake, what is the correct way. Call immediately after the user corrects your work.search_historySearch past user prompts (kind='prompt') by keyword. Returns timestamped snippets truncated to 200 chars each.forgetDelete one memory row (preference, lesson or interaction) by id and sync the search index. Pass type when you know it (ids from remember are preference ids, from save_lesson are lesson ids).memory_statsSummarize memory usage: interaction counts by kind, preference/lesson totals, DB file size, oldest/newest interaction timestamps, and profile sections.get_recent_interactionsList recently captured raw interactions (newest first) as [id] ts [kind] content lines. Optionally filter by kind. Use for auditing history or before distilling memory.export_memoryExport preferences, lessons, profile (and optionally raw interactions) to a JSON file under data/exports/. Only writes inside that directory. Returns the file path, size in bytes and a JSON preview.get_contextAssemble relevant memories for the current task via hybrid retrieval (+ optional memory-graph expansion), with token budgeting. Use to load memory into context before a task.consolidateCluster similar memories via embedding similarity and optionally create derived/consolidated memories linked via 'derived_from'. Use during periodic consolidation.link_memoryCreate a typed relationship between two memories in the graph (supports/contradicts/supersedes/derived_from/related_to/caused_by/depends_on).- +4 more on the listing page
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.
Th Memory MCP
{
"mcpServers": {
"th-memory-mcp": {
"command": "npx",
"args": [
"-y",
"th-memory-mcp"
],
"env": {
"MEMORY_DB_PATH": "YOUR_MEMORY_DB_PATH_HERE"
}
}
}
}
Shodh Memory
{
"mcpServers": {
"varun29ankus-shodh-memory": {
"command": "npx",
"args": [
"-y",
"@shodh/memory-mcp"
]
}
}
}
Frequently asked questions
Th Memory MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. Shodh Memory belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Th Memory MCP 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.
Th Memory MCP 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 th-memory-mcp and varun29ankus-shodh-memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Th Memory MCP has a quality signal of 64/100 (Good) with 3 views, 0 installs and 3 GitHub stars. Shodh Memory has 69/100 (Great) with 8 views, 0 installs and 322 GitHub stars.