AgentRecall vs SMRITI Memory
A side-by-side look at the AgentRecall and SMRITI Memory 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 SMRITI 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 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 SMRITI Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- You want tools like
smriti_encode, smriti_recall, smriti_get_context.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 68/100 · Great | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 372 | 3 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | 12 |
| Full listing | View AgentRecall | View SMRITI Memory |
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
SMRITI Memory tools 12
smriti_encodeIngests a new memory. Accept `private=True` to exclude from team syncs.smriti_recallRetrieves memories using semantic and graph-based retrieval.smriti_get_contextHelper to inject the current active working memory slots into the context window.smriti_how_well_do_i_knowPerforms a meta-memory confidence check on a given topic.smriti_knowledge_gapsIdentifies topics the agent has identified it needs more information on.smriti_pinMarks a memory as permanent (protects it from strength decay).smriti_forgetSoft-deletes/archives a memory, leaving a cryptographic tombstone.smriti_consolidateTriggers a background System 2 consolidation run.smriti_statsReturns system-wide statistics (total memories, rooms, private counts).smriti_create_private_roomSpawns a private room. All memories inside this room are visibility-isolated.smriti_open_uiLaunches the interactive visual D3.js memory graph in your default browser.smriti_sync_obsidianExports the Semantic Palace graph structures to markdown files in an Obsidian Vault.
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"
]
}
}
}
SMRITI Memory
{
"mcpServers": {
"smriti-memory": {
"command": "uvx",
"args": [
"smriti-memcore"
]
}
}
}
Frequently asked questions
AgentRecall is categorized under Knowledge & Memory and uses a local stdio subprocess. SMRITI Memory belongs to Knowledge & Memory and uses a local stdio subprocess. Pick AgentRecall for knowledge & memory work and SMRITI 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.
AgentRecall is listed as free. Auth: no auth required. SMRITI Memory has no declared pricing — check the project's own site. 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 smriti-memory 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 5 views, 0 installs and 372 GitHub stars. SMRITI Memory has 53/100 (Good) with 0 views, 0 installs and 3 GitHub stars.