mem-context
Related Servers
Alternatives to mem-context
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides local vector-based semantic memory storage for AI assistants to persist context and decisions across sessions using local embeddings and LanceDB. It enables private semantic search and session handoff capabilities to maintain long-term project context.81 npm5MIT
- AlicenseAqualityBmaintenanceCognitive prosthetic for AI agents. Indexes conversation history from ChatGPT, Claude Code, Cursor, and Gemini CLI into searchable embeddings. 25 MCP tools including tunnel_state (resume where you left off), switching_cost (quantify context-switch penalty), thinking_trajectory (track idea evolution), and alignment_check (decisions vs principles). LanceDB + Parquet, 12ms recall, local-first.2546 PyPI74MIT
- AlicenseAqualityBmaintenanceProvides persistent cross-session memory and full-text search for AI coding assistants, storing project context, decisions, and preferences while enabling searchable access to conversation history via local SQLite.81MIT
- FlicenseNot gradedqualityBmaintenanceA fully-local AI memory system that saves notes, code, and terminal output to a vector database via Ollama and LanceDB, enabling context retrieval from terminal, API calls, or inside Claude Code.-
- AlicenseAqualityAmaintenancePersistent memory MCP server for AI coding agents (Claude Code, Codex, Gemini CLI). Hybrid retrieval (vector + BM25), cross-encoder reranking, knowledge graph, session checkpoint/resume, and multi-scope isolation. Local-first with LanceDB.3024 npm15MIT
- AlicenseNot gradedqualityCmaintenanceA local memory engine for AI agents. Stores conversation episodes, consolidates knowledge through a neuroscience-inspired lifecycle, and builds a personal knowledge graph — all in a local SQLite database.16MIT
TDQS
Scored across 10 tools
Most tools have clear distinct purposes like recall, remember, get, status. However, there is notable overlap between forget, delete_memory (soft-delete), and purge_memories, which all deal with removing or archiving memories, potentially causing confusion.
Naming conventions are mixed: some are single verbs (forget, recall, update), some are verb_noun (delete_memory, purge_memories), and one is a noun phrase (consolidation_candidates). This inconsistency may reduce predictability.
10 tools is well-scoped for a memory management server, covering creation, retrieval, search, updates, deletion, status, and consolidation. Each tool serves a necessary function without being excessive.
The toolset covers the full CRUD lifecycle plus consolidation and review. One minor gap is the lack of a direct 'list all memories' tool, though recall can approximate it with a broad query. Overall, no significant missing operations.