Agent Recall vs Cognee
A side-by-side look at the Agent Recall and Cognee 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 Cognee for knowledge & memory. 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 Cognee when
- You need dedicated capabilities in the Knowledge & Memory domain.
- Its auth model fits you: No auth required.
- You have the keys it needs:
LLM_API_KEY. - You want tools like
remember, recall, forget.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 69/100 · Great | 53/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | LLM_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 371 | 32,674 |
| Directory activity | 3 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 5 | 4 |
| Full listing | View Agent Recall | View Cognee |
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.
Cognee tools 4
rememberStore data in memory. Pass `data` for text, or `filename` + `content_base64` to ingest an uploaded file (up to 10 MB). With `session_id`: fast session cache (text only). Without `session_id`: permanent graph memoryrecallSearch memory with auto-routing. Searches session cache first when `session_id` is provided, then falls through to the permanent graphforgetDelete memory by dataset name or id, a single data item by `data_id` (paired with its `dataset_id`, both shown by `recall` with `include_references=True`), or delete all owned memory with `everything=True`cognify_statusCheck the progress of background ingestion started by `remember(background=True)`. Unadvertised by default; discoverable via `search_tools` and callable by name
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"
]
}
}
}
Cognee
No confirmed install command for Cognee yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Agent Recall is categorized under Knowledge & Memory and uses a local stdio subprocess. Cognee belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick Agent Recall for knowledge & memory work and Cognee 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. Cognee has no confirmed install command yet — follow its own setup instructions.
Agent Recall is listed as free. Auth: no auth required. Cognee 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 topoteretes-cognee 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 3 views, 0 installs and 371 GitHub stars. Cognee has 53/100 (Good) with 5 views, 0 installs and 32,674 GitHub stars.