jevmem
Related Servers
Alternatives to jevmem
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to persist project memory across sessions by compiling decisions, progress, and pitfalls into git-linked, evidence-backed entries. It lets clients add, query, inject, scan for stale, check assertions on, and compute ROI of those memories over stdio.MIT
- AlicenseNot gradedqualityCmaintenanceGives AI coding agents persistent, branch-aware memory and a dependency-tracked task graph by storing decisions, lessons, and tasks as plain JSON and Markdown committed directly into the repository. Agents can record and fuzzy-search past decisions, dump instant project context, and create, claim, complete, and query tasks whose completion automatically unblocks downstream work.MIT
- AlicenseNot gradedqualityBmaintenanceProvides AI coding agents with git-native persistent memory and a dependency-aware task graph, letting them record and fuzzy-recall architectural decisions, lessons, and gotchas while creating, claiming, and completing tasks that auto-unblock downstream work. Stores everything as plain JSON and Markdown committed inside the repository, so context stays branch-aware, team-shared, and reviewable in pull requests.11 npmMIT
- AlicenseAqualityBmaintenanceProvides AI coding assistants persistent engineering memory stored as Markdown files in an Obsidian vault, enabling project context retrieval, session capture, decision recording, and memory search without requiring Obsidian to be running.71MIT
- AlicenseAqualityAmaintenanceEnables AI coding assistants to contribute to and query a team-shared project memory, storing human-confirmed decisions with source and scope so work can continue across machines.12Apache 2.0
- FlicenseNot gradedqualityDmaintenanceAuto-captured, auto-recalled, path-scoped memory for AI coding agents and teams.2-
TDQS
Scored across 4 tools
list_memory and search_memory both retrieve memories, but one returns all live memories while the other ranks by relevance to a query; add_memory and audit_memory have clearly distinct actions. No two tools overlap in purpose.
All tool names follow a consistent snake_case verb_noun pattern: list_memory, search_memory, add_memory, audit_memory. There are no deviations or mixed conventions.
Four tools cover the core operations of the memory server: listing, searching, adding, and auditing. This is well-scoped and neither excessive nor thin for the domain.
The server supports create (add_memory), read (list_memory, search_memory), and a limited update (audit_memory flagging stale items). There is no delete or full edit operation, so lifecycle coverage is notably incomplete.