Compartment
Related Servers
Alternatives to Compartment
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEngram is an epistemic engine that provides persistent, confidence-ranked memory with contradiction detection and autonomous learning, enabling AI coding agents to recall and reason across projects via MCP.6 npm1MIT
- AlicenseNot gradedqualityDmaintenanceEngram MCP provides persistent, cross-session memory for AI agents by automatically encoding errors, decisions, and discoveries during development sessions. It enables local, intelligent recall and automated context management to help AI learn from experience and avoid recurring mistakes.54 npmBusiness Source 1.1
- AlicenseAqualityBmaintenanceEngram is a local-first memory server that lets AI agents remember things across sessions with zero cloud dependencies.623 npm9MIT
- AlicenseNot gradedqualityCmaintenanceZero-knowledge, self-hostable MCP server providing encrypted durable memory for AI agents, with tools to save, recall, search, list, and delete memories.61MIT
- AlicenseNot gradedqualityBmaintenancePersistent cognitive memory for AI agents. Sub-millisecond recall, fully offline, encrypted. 8 tools: recall, recall_structured, store, store_code, store_decision, search, insights, consolidate.1,223 PyPI85MIT
- AlicenseAqualityAmaintenanceEmbedded memory and retrieval engine for AI agents, providing local-first memory with MCP support for multi-agent access control.348 PyPI2MIT
TDQS
Scored across 14 tools
Most tools target clearly distinct operations: store vs store_many (one vs many), search vs recent (relevance vs recency), link/relations/unlink (graph edges), get/forget (single record). The only mild overlap is memory_status vs memory_selftest (vault status vs canned health queries) and store vs link, but the descriptions explicitly delineate each.
Every tool uses a consistent memory_ prefix with snake_case verb_noun patterns (memory_store, memory_search, memory_forget, memory_link, memory_relations, memory_list_namespaces). Multi-word variants like memory_store_many and memory_list_namespaces remain predictable.
14 tools is well within the ideal 3-15 range and each earns its place: write (single/batch), read (search/get/recent/relations), mutation (link/unlink/forget), and lifecycle (lock/unlock/status/selftest). No obvious filler.
Covers the full memory lifecycle: create, batch create, search, get, link/unlink relations, forget (with shred), namespaces, status, and lock/unlock. Minor gaps: no dedicated update tool (handled indirectly via supersedes) and no namespace/tag management or bulk-export operation.