Turnbook
Related Servers
Alternatives to Turnbook
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceSaves the user's exact words as immutable, SHA-256-hashed captures before anything else, then derives events, entities, context cards, and causal hypotheses — every fact traceable to its verbatim source. Local-first personal memory for Claude Code, Codex, and any MCP client.133MIT
- AlicenseAqualityBmaintenanceGives any MCP client (Claude, ChatGPT, Cursor, and others) one shared knowledge-graph memory where agents record decisions, problems, and approaches together with their reasoning, then retrieve them by meaning rather than keyword. Spreading activation pulls in linked context and decay lets unused knowledge fade without deleting it.918Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code to retain cross-session memory of facts, decisions, and lessons with semantic search, while tracking user corrections as behavioral patterns and evolving self-improving frameworks over time. All processing runs locally through an MCP server and hooks, requiring no cloud service or API key.6 npmMIT
- AlicenseNot gradedqualityDmaintenanceCross-machine memory system for Claude Code that records sessions as searchable markdown, syncs across machines via Git, and exposes full-text search, semantic search, session summarization, and a knowledge graph through an MCP server.40 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables Claude Code and other LLM agents to capture, consolidate, and retrieve memories from conversation history, building a local-first knowledge graph with semantic search and dream-state consolidation.63 npm1MIT
- AlicenseAqualityCmaintenancePersistent memory for Claude Code. Automatically indexes every conversation and provides production-grade hybrid search (BM25 + vectors + reranker) via MCP tools. 100% local, zero config, zero API keys, zero invoice.1671 npm8MIT
TDQS
Scored across 7 tools
The brain_* tools have clearly delineated roles: context returns a ready packet, recall returns structured rows, remember saves, forget deletes, folder configures storage, checkpoint handles team sharing. The context/recall split is the only pair an agent could plausibly confuse, and the descriptions explicitly disambiguate them. code_activity is clearly separate.
Six of seven tools follow a clean brain_<verb/noun> pattern (brain_remember, brain_forget, brain_recall, brain_context, brain_folder, brain_checkpoint). code_activity is the sole deviation, but it covers a distinct domain so the break is defensible.
Seven tools is well within the ideal 3-15 range and each maps to a distinct capability (save, recall, context, forget, storage config, team sharing, code history). No tool feels redundant or padded.
The memory lifecycle is well covered: write, read (two modes), delete, storage/share configuration, team publishing, and code activity. Minor gaps exist—no explicit edit/update tool (handled indirectly via supersedes_memory_id) and no dedicated listing tool (recall with no args serves this), but agents can work around both.