sqlite-memory-mcp
Related Servers
Alternatives to sqlite-memory-mcp
No user-submitted related servers found.
Related Servers
- 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
- AlicenseAqualityDmaintenanceProvides persistent cross-session memory and full-text search for AI coding assistants, storing project context, decisions, and preferences while enabling searchable access to conversation history via local SQLite.81MIT
- -licenseNot gradedqualityDmaintenanceProvides persistent memory for AI assistants like Claude, storing and retrieving information across conversations using a local SQLite database.-
- AlicenseNot gradedqualityBmaintenanceEnables Claude Code to query and store memories from past conversations using FTS5 search and topic-based retrieval, with no API costs.54 npm1Apache 2.0
- AlicenseAqualityDmaintenanceCross-surface persistent memory for Claude. Bridges context between Claude Chat, Code, and Cowork via local SQLite with full-text search.610 npm7MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code and Codex to write, update, and retrieve durable long-term memories that survive session boundaries and context compaction. All recall runs locally against a single SQLite file using hybrid BM25, embedding, and recency ranking cut to an explicit token budget, with no cloud dependency.MIT
TDQS
Scored across 23 tools
Tools are grouped into clear domains: context, memory, skill, and failure, which makes their purposes generally obvious. A few retrieval tools like memory_read, memory_list, and memory_search have overlapping connotations, but their descriptions specify distinct lookup modes.
All tool names follow a consistent lowercase snake_case verb_noun pattern, such as memory_write, context_set, skill_register, and failure_record. Each domain uses predictable verbs, so the naming convention is uniform and scannable.
23 tools is on the higher end and feels slightly heavy, but the server covers four distinct subdomains that each need CRUD, search, and stats operations. The count is reasonable given the combined scope, though it could be tightened.
Each core domain has solid coverage: create, read, list, search, and delete/update where expected. Minor gaps exist, such as no memory update, no single-key context delete, and no skill unregister, but agents can generally work around these.