crystal_why_did_we
Decision archaeology — why a past choice was made
How to use it
crystal_why_did_we is exposed by the Memorycrystal MCP server. Add the server to your MCP client (Claude Desktop, Cursor, Windsurf and others), and the crystal_why_did_we tool becomes available to the model automatically. See the full listing for setup details and every tool this server provides.
FULL MEMORYCRYSTAL LISTINGOther tools in Memorycrystal (25)
Snapshot memory state at a milestone
Trace dependency chains between entities
Update an existing memory
Delete all chunks but keep the KB row/id/bindings
Explain relationships between concepts
Archive or delete a memory
Act on Organic ideas
List active Organic ideas and discoveries
Import reference chunks into a KB (upsert-by-dedupeKey replaces in place)
Enumerate a KB's chunks with cursor pagination + ids
List available knowledge bases
Pre-flight check before risky actions
Search a knowledge base
Semantic search across all long-term memory
Recent messages for short-term context
Store a memory — decisions, facts, lessons
Hybrid search over verbatim conversation history, with time-window (fromMs/toMs or ISO dates) and pagination
Override channel scope for the session
Memory and usage statistics
Trace a memory back to its source conversation
Session startup — briefing and guardrails
Everything known about a topic
Find ownership of a file, module, or area
Read a full memory by ID or path
Search LTM and return crystal paths