Agent Recall vs Agentcairn — MCP Server Comparison | AllMCPs
Agent Recall vs Agentcairn
A side-by-side look at the Agent Recall and Agentcairn 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 Agentcairn 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.
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.
Agentcairn tools 5
searchHybrid search over memory; returns a compact id+snippet index.
Reranks by default (set CAIRN_RERANK=0 to disable, or pass rerank=false).
Recall prefers your current project's memories (boosted, non-lossy): pass
`project` (a repo name) to target another project, else the server's working
directory is used. `scope="project"` hard-limits results to that project.
recall
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 is categorized under Knowledge & Memory and uses a local stdio subprocess. Agentcairn belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Agent Recall for knowledge & memory work and Agentcairn 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. Agentcairn 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 ccf-agentcairn 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 69/100 (Great) with 2 views, 0 installs and 371 GitHub stars. Agentcairn has 63/100 (Good) with 3 views, 0 installs and 65 GitHub stars.
Search then hydrate the top-k notes' full text.
Reranks by default (set CAIRN_RERANK=0 to disable, or pass rerank=false).
Recall prefers your current project's memories (boosted, non-lossy): pass
`project` (a repo name) to target another project, else the server's working
directory is used. `scope="project"` hard-limits results to that project.
build_contextReturn a note plus its 1-hop linked neighbors.
recentList the most-recently-modified notes.
rememberPersist a distilled memory (redacted, non-lossy) into the vault.