Unified Memory MCP
Related Servers
Alternatives to Unified Memory MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables any MCP-capable AI client to search and write a local-first personal memory store backed by one SQLite file, fusing FTS5 keyword and locally computed vector search over records and git-tracked markdown knowledge pages. An optional authenticated HTTP mode shares the same memory across agents and devices without any cloud dependency.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents and any MCP-compatible client to persist, search, update, and delete plain-text memories across sessions, using BM25 lexical ranking over SQLite FTS5 with namespace filtering, tags, free-form metadata, and JSONL export/import — entirely local, with zero external infrastructure.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM applications and agents to persist and recall scoped memories in a local SQLite store, with semantic/hybrid/metadata search, review-first corrections and summaries, and controlled export, backup, and purge operations over stdio.60 PyPIApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables coding agents and other MCP clients to read and write the same durable facts in a local SQLite memory, searched by embedding plus full text and separated into global and per-repository scopes, with a browser notebook and ZIP backup/migration. Runs over stdio or HTTP, keeping search on-machine and secrets redacted before storage.MIT
- 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.1,593 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
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.