Project Memory
Related Servers
Alternatives to Project Memory
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI clients to append durable, content-hashed records of each decision to an owner-controlled markdown notes folder, then recall them across sessions and across different tools with their dates, project provenance, and the exact note versions cited. Records are append-only and searchable by full text, topic stance, or recent activity, so past conclusions can be revisited without relying on an ephemeral session.3317 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides local, evidence-aware research memory with human review, revision history, and an inspector, allowing assistants to preserve source reports, inferences, assumptions, and evidence across sessions.14 npmMIT
- AlicenseNot gradedqualityAmaintenanceIt enables AI agents to retrieve Git-backed project context, handoff packages, and next actions, then append validated, audited progress events as project-record commits.MIT
- AlicenseNot gradedqualityBmaintenanceEnables LLM agents to capture every project turn into an encrypted write-ahead log, retroactively filter entries against the shipped product, and semantically recall what mattered in later sessions.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to retain, review, approve, and retrieve encrypted local notes, decisions, preferences, and follow-ups across sessions, with retained source evidence and correction history.MIT

ideate MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI-augmented software delivery through an append-only process record, with hooks for capturing decisions, session outcomes, and commit boundaries, and provides session priming with recency-based context.AGPL 3.0
TDQS
Scored across 3 tools
memory_write is clearly distinct, and memory_get covers structured views, discovery, and next-action recovery while memory_context handles bounded subject-level evidence retrieval. The only real ambiguity is that both memory_get and memory_context can retrieve evidence, but their stated use cases are mostly complementary.
All three tools share the memory_ prefix and use lowercase snake_case, so the set reads predictably. memory_get and memory_write are verb-based names, while memory_context is a noun phrase, creating a minor pattern break.
Three tools is on the low end, but each tool is a deliberate command hub covering a very large number of operations, so the count does not feel arbitrarily thin. The design compresses read and write surfaces into three broad endpoints rather than many small ones.
The read/write/context triad covers capture, retrieval, planning, decisions, progress, reviews, and context management, with append-only behavior making delete unnecessary. Minor gaps exist for externally referenced processes such as lesson_review and skill activation not appearing as first-class tools.