RE-call MCP Memory Server
Related Servers
Alternatives to RE-call MCP Memory Server
- AlicenseAqualityAmaintenanceSelf-hosted MCP server for Obsidian with semantic + full-text search over PostgreSQL/pgvector, wikilink graph traversal, atomic note CRUD, OAuth 2.0, and a self-describing vault guide.2514MIT
- AlicenseAqualityBmaintenanceA personal memory MCP server that ingests AI agent conversation logs from multiple platforms into a searchable PostgreSQL+pgvector database, enabling cross-session recall of past reasoning and decisions.6MIT
Related Servers
- AlicenseNot gradedqualityAmaintenanceMCP server that adds a trust layer to AI agent memory, enforcing independent review and tamper-evident audit chains for any memory store. It provides tools to search, get, propose, and promote memories under governance rules.MIT

yantrikdb-mcpofficial
AlicenseNot gradedqualityAmaintenanceMCP server providing cognitive memory tools (remember, recall, think, etc.) for AI agents, enabling forgetting, consolidation, and contradiction detection.174Apache 2.0- AlicenseNot gradedqualityAmaintenanceMCP server for brainmem, providing memory search, write, outcome, explain, and status tools to give LLM agents auditable long-term memory. It prioritizes failures, gates writes on surprise, and supports validity intervals for beliefs.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceSelf-hosted MCP server that gives coding agents persistent, code-aware memory with structural graph recall and blast-radius planning. It links experiential decisions to code locations and provides honest measurement instruments.Apache 2.0
- AlicenseAqualityCmaintenanceMCP server providing persistent memory for AI agents, enabling them to read, write, and query memories across sessions.97 npmMIT
- -licenseNot gradedqualityNot gradedmaintenanceA sophisticated MCP server providing advanced memory capabilities with RAG, hallucination detection, and enterprise-grade AI infrastructure for intelligent agent ecosystems.-
TDQS
Scored across 5 tools
recall_search and recall_evidence both retrieve memory, but the descriptions clearly separate them: search is for consulting and guidance, evidence is specifically for answering with citations. The other tools (index, stats, forget) are distinct. Some initial confusion between search and evidence is possible, though the explicit 'use this instead of' note mitigates it.
All tools share the consistent `recall_` prefix with lowercase snake_case. The second part is mostly a verb (search, index, forget) with a couple of nouns (evidence, stats), but the uniform prefix and style make the pattern highly predictable. There is no mixed casing or arbitrary naming.
Five tools form a well-scoped set for a memory server: create (index), read (search, evidence, stats), and delete (forget). This is within the ideal 3-15 range and every tool serves a distinct lifecycle need without bloat.
The memory lifecycle is fully covered: index ingests files, search and evidence retrieve with different output formats, stats checks freshness, and forget handles deletion (with re-indexing providing update semantics). There are no obvious gaps for the stated purpose of a personal memory server.