AI Memory MCP Server
Related Servers
Alternatives to AI Memory MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to maintain a private, local-first persistent memory by automatically saving, searching, and retrieving structured project memories through MCP, with hybrid keyword and embedding search, feedback-driven ranking, and no cloud dependency.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to store and retrieve durable per-project codebase memories through budgeted briefings, hybrid semantic and keyword search, and linked memories over MCP.MIT
- AlicenseAqualityBmaintenanceMCP-native persistent memory layer for AI agents across Claude Code, Cursor, VS Code, and OpenClaw. Powered by hybrid vector search, BM25, and cross-encoder reranking with a published 73.1% LoCoMo benchmark accuracy.41Apache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides a local-first persistent memory layer for AI coding agents through MCP, enabling them to save, search, retrieve, update, and consolidate project context, technical decisions, debugging solutions, and developer preferences across sessions.MIT
- AlicenseAqualityCmaintenanceLocal-first persistent memory for coding agents and MCP clients. It keeps important project context across sessions and reduces wasted tokens by retrieving only relevant memories instead of replaying unnecessary history.8MIT
- AlicenseNot gradedqualityCmaintenancePersistent project memory and task management for AI coding agents through MCP. Lets Claude Code, Cursor, Codex and other MCP clients save decisions and bug fixes, search relevant context, and reuse it across sessions.1MIT
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: forget (delete), get_memory (by id), list_memories (filtered browsing), recall (semantic search), remember (create), search_memories (structured filter), update_memory (modify), who_am_i (identity). Despite some overlap between list and search, descriptions differentiate them well.
Naming conventions are mixed: three tools are single verbs (forget, recall, remember), four are verb_noun (get_memory, list_memories, search_memories, update_memory), and one is a phrase (who_am_i). This inconsistency, while readable, lacks a uniform pattern.
With 8 tools, the set is well-scoped for a memory server. Each tool serves a distinct CRUD or auxiliary role, covering creation, retrieval (multiple methods), update, deletion, and system info. No tool seems superfluous or missing.
The tool surface provides full lifecycle coverage: remember (create), get_memory/list/recall/search/who_am_i (read), update_memory (update), forget (delete). It also supports linking via recall. No obvious gaps for the intended personal memory domain.