sqlite-local-ai-memory
Related Servers
Alternatives to sqlite-local-ai-memory
- AlicenseAqualityBmaintenanceGoverned cross-agent memory for coding agents with hybrid retrieval, provenance tracking, and cross-machine sync.918MIT
- AlicenseBqualityDmaintenanceProvides persistent memory, skill tracking, failure indexing, and context sharing for Claude Code using SQLite with FTS5 full-text search.238 npm1MIT
- AlicenseAqualityCmaintenanceEmbedded, local-first agent memory: facts extracted into a per-namespace SQLite file (vec0 + FTS5) with hybrid retrieval and point-in-time (time-travel) queries. ADD-only history over stdio — no server process, no cloud dependency.730 PyPI43Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to store, search, update, and manage local long-term memories with namespaces, tags, expiration, and audit trails, without requiring cloud accounts, API keys, or network access.MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceLightweight persistent memory for AI agents using a single SQLite file with hybrid search (keywords + semantics). Zero to 12MB install, no cloud or server required.7MIT
- -licenseNot gradedqualityNot gradedmaintenanceProvides persistent local memory functionality for AI assistants, enabling them to store, retrieve, and search contextual information across conversations with SQLite-based full-text search. All data stays private on your machine while dramatically improving context retention and personalized assistance.3-
- AlicenseAqualityCmaintenanceProvides persistent local memory for any MCP-compatible AI agent, enabling agents to store, search, recall, forget, export, and manage preferences, rules, and facts with zero dependencies, no cloud, and no API keys.8MIT
- AlicenseAqualityBmaintenancePersistent long-term memory for AI coding assistants. Local SQLite, no cloud - 16 MCP tools to store, search, relate, and consolidate typed memories with a confidence lifecycle, hybrid BM25 + semantic search, namespaces, a knowledge graph, and a built-in OS keychain credential vault.237MIT
- 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.56Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to keep durable long-term memory on the user's own machine, writing sessions and messages into a local SQLite database and retrieving them via keyword, exact, or optional semantic search with surrounding context. Runs entirely offline over stdio, so no cloud service or API key is required to give an agent recall across sessions.1MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: two targeted reads (get_fact_lineage, get_current_state), a broad search (search_memory), an atomic write (save_fact), and a batch maintenance write (consolidate). The descriptions explicitly cross-reference each other with 'use X instead of Y' guidance, eliminating selection ambiguity.
Four tools follow a clean verb_noun or verb_noun-ish pattern (get_fact_lineage, get_current_state, save_fact, search_memory), while 'consolidate' is a bare verb. This is a minor deviation that remains readable and predictable.
Five tools is well-scoped for a local memory server, with each earning its place across read, search, write, audit, and maintenance roles. No redundant or trivially fragmented tools.
The surface covers search, atomic persistence, lineage auditing, dashboard state, and batch consolidation, which spans the core memory lifecycle. An explicit forget/delete or update operation is absent, though append-only supersede via save_fact mostly compensates.