memory-keeper

Store and recall persistent context using Memory MCP primitives—save decisions with rationale and trade-offs, then retrieve them by search or tag. This builds institutional memory so future team members understand the reasoning behind critical choices without rediscovery.

Use memory storage to identify and catalog recurring solutions, best practices, and common issues across sessions. Tag and organize patterns so they become immediately available for reuse, reducing duplicated effort and accelerating problem-solving.

Yes. Build a searchable knowledge base by storing architectural decisions, patterns, and project context. New hires query this memory to understand decisions, conventions, and past solutions, cutting onboarding time and ensuring consistency.

Store memories with tags and metadata using MCP primitives (store, tag, search, list), then retrieve by keyword or tag across sessions. This creates a living knowledge base that prevents knowledge loss and makes solutions discoverable without manual documentation overhead.

Capture the decision itself, full rationale, alternatives considered, and context. Persistent storage ensures this complete record survives session boundaries, giving future developers the 'why' behind choices and preventing repeated debate over settled questions.