MemCore
Related Servers
Alternatives to MemCore
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides long-term memory for LLMs via local SQLite storage with hybrid search (BM25, vectors, recency decay), enabling AI coding agents to persist and recall memories across sessions without cloud or API keys.53MIT
- AlicenseAqualityBmaintenanceProvides 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
- FlicenseAqualityCmaintenanceA lightweight, local memory server for AI coding assistants that stores durable knowledge (decisions, facts, gotchas) in a tree structure, enabling persistent context across sessions with efficient retrieval via summaries and FTS5 search.934 npm4-
- AlicenseAqualityAmaintenanceLocal-first memory for AI coding agents using SQLite, enabling persistent recall of decisions, lessons, and project context without cloud or API keys.10107 PyPI281Apache 2.0
- AlicenseNot gradedqualityDmaintenancePersistent memory for AI coding agents with local-first, zero-cost, privacy-first SQLite/FTS5 storage and biological-inspired decay.11 npm3MIT
- AlicenseAqualityAmaintenancePersistent AI memory with SQLite hybrid search (FTS5 + semantic), built-in Qwen3 embedding, and rclone sync across machines.156 npm1,540 PyPI11Apache 2.0
TDQS
Scored across 13 tools
Each tool has a sharply distinct purpose (write/search/get/list/recent/scopes/stats/events/history/archive/restore/embed_status/healthcheck), and the read-heavy tools explicitly cross-reference each other with 'use X instead when...' guidance, eliminating overlap. An agent can determine the right tool without guessing.
Every tool uses a uniform snake_case memory_ prefix followed by a clear verb or noun (memory_write, memory_search, memory_archive, memory_restore, memory_healthcheck). No mixing of conventions or inconsistent verb styles.
13 tools is well-scoped for a persistent memory store covering full CRUD, search, auditing, and maintenance. Each tool earns its place with no redundant or filler operations.
The full lifecycle is covered: create/update (write), read (get, search, list, recent), soft-delete/restore (archive, restore), plus history, audit events, scope discovery, stats, embedding status, and healthcheck. No obvious gaps for a memory domain.