mcp-memory
Related Servers
Alternatives to mcp-memory
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to store and recall durable facts, decisions, and lessons over MCP using hybrid semantic and keyword search, typed memories, graph relations, sessions, and time-travel queries. Runs locally with no server process or API key, persisting everything to files that both agents and a CLI can share.392 npmMIT
- AlicenseAqualityDmaintenanceA lightweight, local-first MCP server and CLI that helps developers and AI coding agents store and retrieve lessons learned during development, using SQLite and context-aware filtering.6MIT
- AlicenseAqualityBmaintenanceProvides persistent, searchable memory for AI agents across any MCP-compatible client, storing project context, user preferences, and session learnings locally in SQLite with tools to save, retrieve, search, and manage them.126 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to store, search, and recall persistent project and cross-project memories locally over MCP, keeping architectural decisions, conventions, and error patterns available across sessions. Also optionally exposes a task server for autonomous task execution driven by that same memory store.-
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to read and write persistent, local-first memory through MCP, storing decisions, preferences, and error patterns per project while surfacing cross-project guidelines, with semantic search over on-disk SQLite and an optional queue for autonomous task execution.-
- AlicenseNot gradedqualityCmaintenancePersistent memory for AI coding agents. Enables agents to save and recall decisions, patterns, bugs, and context across sessions via an MCP server with local SQLite storage.21 npm2MIT
TDQS
Scored across 6 tools
Each tool targets a distinct operation: search (find), get (read by ID), add (create), archive (soft delete), supersede (atomic replace), feedback (rate). The main adjacency is archive vs supersede, since supersede also archives, but the descriptions clarify the atomic-replace semantics. Minor overlap only, so an agent can reliably disambiguate.
Every tool follows a strict memory_<verb> pattern (memory_search, memory_get, memory_add, memory_archive, memory_supersede, memory_feedback). Verb style is consistent and snake_case is used throughout with no deviations.
Six tools is well-scoped for a memory store, covering the full lifecycle without redundancy. Each tool earns its place and no thin or bloated surface is apparent.
The surface covers the full lifecycle: search/list, get, add, archive (soft delete), supersede (update via atomic replace), and feedback. Coverage is strong, with only minor gaps such as hard deletion or bulk operations that agents can work around.