jevmem
Related Servers
Alternatives to jevmem
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to persist decisions, rules, bugs, to-dos and dead ends from chat sessions into a JEVMEM.md file in the repository, then automatically recall the relevant lines in later sessions and check tool calls against saved rules before they run. This keeps project memory current across Claude Code, Cursor, Codex and Claude Desktop without hand-maintaining a context file.848 npmMIT
- AlicenseNot gradedqualityAmaintenanceSaves the decisions, rules, and failed approaches from AI coding chats into a JEVMEM.md file in your repo, then brings the relevant lines back in later sessions. Also checks each command or file edit against those saved rules before it runs, asking first when one might be broken.848 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenancePersists decisions, rules, bugs, to-dos and dead ends from AI coding chats as lines in a repo's JEVMEM.md file, then brings the relevant ones back in later sessions. Also checks commands and file edits against the saved rules before they run, flagging possible violations for confirmation.848 npmMIT
- AlicenseNot gradedqualityAmaintenancePersists the decisions, rules, bugs and dead ends from coding chats into a JEVMEM.md file in your repo and surfaces the relevant lines again in later sessions, so consistent project conventions carry across sessions. It also checks planned commands and file edits against those saved rules before they run.848 npmMIT
- AlicenseNot gradedqualityAmaintenanceSaves decisions, rules, bugs, to-dos and dead ends from AI coding chats into a JEVMEM.md file in the repo, then brings the relevant lines back in later sessions and checks each command or file edit against the saved rules before it runs.848 npmMIT
- AlicenseNot gradedqualityAmaintenancePersists decisions, rules, bugs, to-dos and dead ends from Claude Code, Cursor, Codex and Claude Desktop chats as single lines in a repo's JEVMEM.md, then surfaces the lines relevant to each new prompt in later sessions. Also checks commands and file edits against saved rules before they run, flagging possible rule breaks.848 npmMIT
TDQS
Scored across 4 tools
Each tool maps to a distinct memory operation: add_memory (write), audit_memory (re-validate/stale-flag), list_memory (enumerate), and search_memory (rank by query). There is no meaningful overlap between writing, auditing, listing, and searching, so an agent can select correctly without guessing.
All four tools follow a strict verb_noun pattern (add/audit/list/search + _memory) in consistent snake_case. This is a textbook predictable naming scheme.
Four tools is a lean but sensible surface for a single-file memory store covering write, list, search, and audit. It is slightly on the thin side, but every tool clearly earns its place with no redundancy.
Core lifecycle is covered: add, list, search, and audit. There is no explicit update or delete/edit tool, but the descriptions indicate dead-end replacement and stale-flagging handle correction, so the gap is minor and workable.