rutter-memory
Related Servers
Alternatives to rutter-memory
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI coding sessions to persist the reasoning behind work — decisions and their justifications, rejected options, side findings and nuances — as append-only Markdown records with reversible review, archive and human-confirmed purge. Retrieval scores records against the current task and returns only a short, budgeted list of hits, with full text fetched on demand, plus optional session hooks and handoff support.MIT
- FlicenseNot gradedqualityBmaintenanceEnables users to turn a decision into an append-only judgment record that keeps their own wording and premises separate from the AI's suggestions, then returns on a chosen event or fallback date so reality and later answers can be appended without rewriting the original. Runs over any MCP-capable assistant with records stored in a local project ledger, and never scores or profiles the person.487 npm1-
- AlicenseNot gradedqualityBmaintenanceGives AI agents a long-term memory layer over plain Markdown notes, letting them run ranked, citable searches, record new facts, and inspect conflicts and stale entries. Results carry freshness labels, supersession history, and audit fields like search timestamp and no-match status so agents can prove a search actually ran.MIT
- AlicenseNot gradedqualityAmaintenanceLets AI assistants read a per-project markdown log at session start and append decisions, bug fixes, current state, roadmap, and handoff notes, with ranked full-text search across all projects.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to search and read Markdown notes by keyword, meaning and links, with cited recall and honest no-match results. It also supports guarded, evidence-checked memory writes with receipts, conflict handling and lifecycle-aware filtering.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI tools and agents to share a persistent memory space, so a decision, task, or encrypted secret saved in one client can be searched, recalled, and handed off from another. It also tracks goals day by day, moves unfinished work between sessions, and keeps exports, trash recovery, and per-account isolation under the user's control.-
TDQS
Scored across 4 tools
Each tool has a distinct retrieval target: a single note by path (get-note), ranked note search (search), session history (recent), and recorded stances (positions). There is mild conceptual overlap between search's prior-engagement notes and recent/positions recall, but the primary purposes are separable.
All four tools share the 'librarian-' kebab-case prefix, giving a predictable namespace. The suffix mixes verb and noun forms (get-note vs recent/positions/search), a minor deviation but still readable and consistent in style.
Four tools is a small but sensible surface for a focused memory-vault server, with each tool covering a different recall mode. It is slightly lean—one or two more (e.g. a list/browse) would round it out—but nothing feels redundant.
Notes are well covered by search plus get-note, and sessions/stances have their own recall tools. However, there is no way to browse or list notes/topics, no delete or update path, and the surface is read-only, leaving noticeable operational gaps for the stated memory domain.