AgentRecall vs Th Memory MCP
A side-by-side look at the AgentRecall and Th Memory MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AgentRecall for knowledge & memory work as a local process; choose Th Memory MCP 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 AgentRecall 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, remember, recall.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 68/100 · Great | 64/100 · Good |
| 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 | MEMORY_DB_PATH |
| Verified owner | Community listing | Community listing |
| GitHub stars | 373 | 3 |
| Directory activity | 6 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 5 | 16 |
| Full listing | View AgentRecall | View Th Memory MCP |
Tools & capabilities
AgentRecall tools 5
session_startLoads corrections, insights and `watch_for` warnings for the projectrememberSaves one fact; auto-routes to journal / palace room / corrections / awarenessrecallRanked search across every store (RRF), with `useful` feedback that re-weights future rankingcheckMatches the plan against known corrections; returns `verdict: "blocked"` when one overrides itsession_endWrites the journal, promotes insights, records trajectory, optionally opens/closes a pipeline phase
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
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.
AgentRecall
{
"mcpServers": {
"goldentrii-agentrecall": {
"command": "npx",
"args": [
"-y",
"agent-recall-mcp"
]
}
}
}
Th Memory MCP
{
"mcpServers": {
"th-memory-mcp": {
"command": "npx",
"args": [
"-y",
"th-memory-mcp"
],
"env": {
"MEMORY_DB_PATH": "YOUR_MEMORY_DB_PATH_HERE"
}
}
}
}
Frequently asked questions
AgentRecall is categorized under Knowledge & Memory and uses a local stdio subprocess. Th Memory MCP belongs to Knowledge & Memory and uses a local stdio subprocess. Pick AgentRecall for knowledge & memory work and Th Memory MCP 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.
AgentRecall is listed as free. Auth: no auth required. Th Memory MCP 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 goldentrii-agentrecall and th-memory-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AgentRecall has a quality signal of 68/100 (Great) with 6 views, 0 installs and 373 GitHub stars. Th Memory MCP has 64/100 (Good) with 3 views, 0 installs and 3 GitHub stars.