memory
Related Servers
Alternatives to memory
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to search their own and other agents' sessions and existing Markdown memories locally through MCP, returning provenance-tagged fragments while keeping source files read-only. Indexing, embeddings, and reranking all run locally behind a single daemon with a SQLite index.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to query a unified local index of all their sessions through native tools, supporting session summaries, full-text search, listing, message timelines, and handoff context packages for another agent.5MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and MCP hosts to search and ask questions across a local hybrid-retrieval index of scattered notes, documents, PDFs, and chat logs, returning section-level citations and agent-usable tools, resources, and prompts.-
- AlicenseNot gradedqualityBmaintenanceProvides AI agents with persistent, local, and shareable project memory by storing decisions and code context in a searchable SQLite index, supporting keyword and semantic search via MCP.3MIT
- AlicenseBqualityBmaintenanceEnables coding agents to incrementally index project text and code, persist decisions and constraints with clear sources, and assemble focused project context across sessions via MCP.3424 npm9MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to search local repositories through hybrid keyword and embedding retrieval, read matched chunks, and list indexed repos via MCP, without API keys or cloud services.MIT
TDQS
Scored across 3 tools
Each tool maps to a distinct memory operation: inspection (stats), retrieval (search), and storage (write). There is no plausible way to confuse them, and the descriptions reinforce the boundary between reading and writing.
All three names follow the identical memory_<verb> pattern (memory_stats, memory_search, memory_write), with short, predictable verbs. Naming is fully consistent and self-documenting.
Three tools is a tight, well-scoped surface for a memory service where each tool clearly earns its place. It sits at the thin edge of the ideal range, though the narrow scope justifies it.
Read (search), write, and introspection (stats) are covered, but there is no way to delete, correct, or update a stored memory, and stats gives only counts rather than per-collection detail. Agents that wrote a wrong or stale fact have no lifecycle operation to fix it, which is a notable gap for a shared memory store.