MemCore
Related Servers
Alternatives to MemCore
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides 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.52MIT
- 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
- FlicenseAqualityDmaintenanceA 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.94-
- AlicenseAqualityBmaintenanceLocal-first memory for AI coding agents using SQLite, enabling persistent recall of decisions, lessons, and project context without cloud or API keys.10139 PyPI289Apache 2.0
- AlicenseNot gradedqualityDmaintenancePersistent memory for AI coding agents with local-first, zero-cost, privacy-first SQLite/FTS5 storage and biological-inspired decay.17 npm3MIT
- AlicenseAqualityAmaintenancePersistent AI memory with SQLite hybrid search (FTS5 + semantic), built-in Qwen3 embedding, and rclone sync across machines.15307 PyPI13Apache 2.0
TDQS
Scored across 13 tools
Each tool targets a distinct axis: content search, exact-key fetch, browsing by scope/type, time-ordered recents, audit events, version history, semantic status, healthcheck, and lifecycle mutations. The descriptions explicitly cross-reference nearby tools and state when to use one instead of another, so an agent can reliably select the right tool.
All names use the consistent `memory_` prefix and snake_case, making the family easy to scan. However, suffixes mix verbs (`search`, `get`, `write`, `archive`) with nouns/adjectives (`stats`, `recent`, `events`, `scopes`, `history`, `healthcheck`), so the verb_noun pattern is not fully uniform.
Thirteen tools is well within the appropriate range for a memory store with search, scopes, audit history, versioning, archive/restore, and health checks. Each tool earns its place by covering a distinct operation rather than duplicating functionality.
The lifecycle is fully covered: create/update via `memory_write`, read via search/get/list/recent, soft-delete via archive, restore, audit events, prior-version history, scope discovery, stats, semantic embedding status, and end-to-end healthcheck. The absence of hard delete is intentional and explained, not a dead end.