openmemkit
Related Servers
Alternatives to openmemkit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to write, search, browse, link, consolidate, and promote layered Markdown-backed memories with SQLite FTS5 indexing, rule checks, and optional semantic retrieval across projects.1Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to capture, structure, remember, and retrieve source-backed memory as local Markdown files, with reviewable writes and no cloud dependency.218MIT
- AlicenseBqualityBmaintenanceEnables AI agents to store, recall, audit, and govern version-controlled project memory as Git-committed Markdown artifacts, with deterministic SQLite FTS5 search and read-only constitutional guardrails.6235 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables agents to persist, search, and consolidate durable cross-session memory through a dual-vault SQLite/FTS5 store with hybrid reranking, retrieval gating, temporal relations, and Markdown wiki projection.MIT
- AlicenseAqualityBmaintenanceA local-first shared memory layer for MCP-aware agents like Claude, Codex, and Hermes, enabling persistent memory across chats and clients via Markdown files and SQLite FTS.62MIT
- AlicenseAqualityBmaintenanceProvides AI agents with persistent, long-term memory via OKF-formatted markdown and SQLite indexing, enabling stateful storage, retrieval, and search across sessions.6223MIT
TDQS
Scored across 11 tools
memory_domains, memory_list, and memory_stats all return overlapping inventory/index information, which could cause misselection. memory_update and memory_write also both suggest writing, though they target different backends; the descriptions help, but boundaries are not always obvious.
All tools share the memory_ prefix and most follow a verb-oriented pattern like search, get, list, update, delete, write, and flush. A few noun-style names such as domains, stats, and history deviate slightly, but the overall convention remains predictable.
11 tools is well within the ideal range for a memory-management server. Each major operation—bootstrap, read, search, list, stats, update, delete, history, write, and flush—has a dedicated tool without excessive fragmentation.
The set covers session bootstrap, reading/searching, metadata inspection, update/delete, audit history, and the write_log flush pipeline. Minor gaps exist: delete is described as recoverable but no restore tool is exposed, and there is no direct create-file operation apart from the write_log/flush path.