Agent Recall vs Total Agent Memory

A side-by-side look at the Agent Recall and Total Agent Memory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Agent Recall logoAgent RecallKnowledge & Memory · Local subprocess (stdio)Correction-first agent memory. Precision KPI tracks if agents heed warnings. 5 layers, local-only.69GreatAuth: no auth requiredTotal Agent Memory logoTotal Agent MemoryKnowledge & Memory · Local subprocess (stdio)Persistent local memory for coding agents: temporal knowledge graph, procedural and episodic recall44FairAuth: not declared

Verdict: choose Agent Recall for knowledge & memory work as a local process; choose Total Agent 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?

Agent Recall logoChoose 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.
Explore Agent Recall

Total Agent Memory logoChoose Total Agent Memory when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: TAM_MEMORY_DIR.
Explore Total Agent Memory

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAgent Recall logoAgent RecallTotal Agent Memory logoTotal Agent Memory
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal69/100 · Great44/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedTAM_MEMORY_DIR
Verified ownerCommunity listingCommunity listing
GitHub stars37173
Directory activity 3 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools5Not listed

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.

Total Agent Memory tools

No tool names declared yet. Check the project README from 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.

Agent Recall

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "agent-recall": {
      "command": "npx",
      "args": [
        "-y",
        "agent-recall-mcp"
      ]
    }
  }
}

Total Agent Memory

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "total-agent-memory": {
      "command": "uvx",
      "args": [
        "total-agent-memory"
      ],
      "env": {
        "TAM_MEMORY_DIR": "YOUR_TAM_MEMORY_DIR_HERE"
      }
    }
  }
}

Frequently asked questions

Agent Recall is categorized under Knowledge & Memory and uses a local stdio subprocess. Total Agent Memory belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Agent Recall for knowledge & memory work and Total Agent 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.

Agent Recall is listed as free. Auth: no auth required. Total Agent 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 agent-recall and total-agent-memory 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. Total Agent Memory has 44/100 (Fair) with 2 views, 0 installs and 73 GitHub stars.