Unified Memory MCP
Related Servers
Alternatives to Unified Memory MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceProvides a drop-in MCP memory server over stdio using a local SQLite store, enabling agents to store, search, and audit memory with provenance, scoped access, and contradiction tracking without requiring API keys, LLMs, or embedding providers.345 npm16Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables concurrent MCP clients to share a persistent SQLite-backed key-value memory store with semantic search, write attribution, and audit history.MIT
- 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.14 npmMIT
- AlicenseNot gradedqualityFmaintenanceLocal-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.2Apache 2.0
- 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.125 npmMIT
- AlicenseNot gradedqualityAmaintenanceLocal-first MCP memory server providing persistent, versioned, queryable memory for AI agents using JSON categories and SQLite FTS5, with optional fleet sync.2Apache 2.0
TDQS
Scored across 16 tools
Most tools have clearly distinct purposes, but memory_search and memory_recall overlap as search mechanisms, and memory_bootstrap overlaps with handoff_load/handoff_list by also returning handoff data. Descriptions help clarify preferred usage, so misselection is unlikely for careful agents.
All tool names use consistent snake_case with a predictable domain prefix: memory_ or handoff_. Actions are generally verbs and the pattern is stable across the set.
16 tools is slightly above the typical 3-15 range, but each tool serves a distinct role in memory management or handoff lifecycle. The set is rich but not bloated.
The surface covers memory CRUD, search, recall, admin tasks, and handoff lifecycle, so core workflows are complete. Minor gaps include no direct handoff_get by id, though handoff_load/list and memory_prune cover most needs.