memory-lite-mcp
Related Servers
Alternatives to memory-lite-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenancePersistent memory for any AI assistant. Zero token cost until recall. Stores memories in local SQLite, ranks by 6-factor scoring, returns results 79% smaller than JSON. Works with Claude, ChatGPT, Grok, Cursor, Windsurf, and any MCP client.57Apache 2.0
- AlicenseAqualityBmaintenanceGives every AI agent on a machine a shared, local-first long-term memory: 16 tools to save, search, edit and organize structured notes in one SQLite file, with attribution per client. Runs over stdio or localhost HTTP, so Claude Code, omp and any other MCP client recall the same facts, decisions and entities.16154 PyPI2MIT
- FlicenseNot gradedqualityCmaintenancePortable AI memory vault — save memories, skills, and configs to a local database and share them across Claude Desktop, Claude Code, Cursor, Cline, and more.1-
- AlicenseAqualityCmaintenanceLocal-first memory for Claude Code and any MCP client: hybrid vector + keyword search and a bi-temporal knowledge graph in one SQLite file. Local embeddings, no API key, $0/token.51175 npm2PolyForm Noncommercial 1.0.0
- AlicenseNot gradedqualityDmaintenanceProvides persistent, searchable memory for Claude Code using local SQLite, semantic embeddings, and full-text search, enabling Claude to recall and retrieve context across sessions and projects without external services.23 npm4MIT
- AlicenseAqualityCmaintenancePersistent semantic memory for AI agents. SQLite-backed, local-first, zero config. Semantic search via Ollama embeddings with keyword fallback. Tools: remember, recall, history, forget, stats.1737 npm1MIT
TDQS
Scored across 3 tools
The three tools map to unmistakable lifecycle phases: write (remember), read (recall), and delete (forget). There is no overlap in purpose and an agent can pick correctly from the name alone.
All three names are single, lowercase verbs in a consistent style and follow a coherent memory metaphor (remember/recall/forget). No mixing of conventions or noun/verb forms.
Three tools is exactly right for a 'lite' memory server; each one earns its place and nothing peripheral is bolted on. The surface stays small and predictable.
Create, keyword-read, and delete are covered, but there is no update/edit operation and no way to enumerate stored memories without guessing keywords (recall is capped at 10 and requires terms). Agents must fall back to forget-then-remember to correct a fact, which is a notable but workable gap.