BrainOS
Related Servers
Alternatives to BrainOS
- AlicenseAqualityBmaintenanceBasic Memory is a knowledge management system that allows you to build a persistent semantic graph from conversations with AI assistants. All knowledge is stored in standard Markdown files on your computer, giving you full control and ownership of your data. Integrates directly with Obsidan.md21210,764 PyPI4,634AGPL 3.0

mem0-mcpofficial
AlicenseAqualityDmaintenanceSelf-hosted Mem0 MCP server integrating Qdrant, Neo4j, and Ollama for semantic memory search, graph entity relationships, and memory management via OpenMemory API.64MIT
Related Servers
- AlicenseBqualityBmaintenanceProvides persistent project memory, task lists, time tracking, and shared rules and learned preferences so coding agents can recall decisions and conventions across sessions and coordinate multi-step work.191MIT
- AlicenseNot gradedqualityDmaintenancePersistent decision memory and contradiction detection for AI coding agents. Enforces architectural consistency across sessions — the agent cannot code until it loads prior decisions. Human resolves conflicts on a dashboard or in chat.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to persist and resume project and task context across sessions, organizing plans, phases, and tasks while recording progress, decisions, pending work, and history locally through MCP.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to maintain project continuity through a file-based state hub with tasks, phases, and handoff snapshots. Provides MCP tools for reading and updating project state, with gatekeeping enforced via real-state evaluation and per-tool authorization.3MIT
- AlicenseNot gradedqualityDmaintenanceProvides operational continuity for AI coding agents, preserving task state, decisions, checkpoints, and project context across sessions and model switches via MCP.1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables persistent storage and retrieval of decisions, settings, and operational rules across chat sessions, maintaining context continuity and decision consistency for long-term development projects through structured memory management.-
TDQS
Scored across 24 tools
There are many read-oriented tools (entity_read, focus_get, memory_check, audit_log, semantic_recall, pattern_detect, decision_review, project_evidence_scan, operational_state_check), but descriptions explicitly delineate boundaries with phrases like 'not semantic_recall' and 'this is NOT context_resolve.' A few pairs (decision_check vs decision_review, semantic_recall vs audit_log) require reading the full description to separate, keeping it just shy of 5.
All names are snake_case and organized around clear prefix families (plan_*, decision_*, entity_*, wrap_*). Minor inconsistency in verb/noun ordering (memory_commit, decision_log, audit_log vs entity_read, focus_get), but the pattern remains highly predictable.
24 tools sits in the heavy band for a memory/state server, and several read-path tools could plausibly be consolidated (e.g. project_evidence_scan and operational_state_check both do read-only repo introspection). Each has a defensible role, but the surface feels broader than strictly necessary.
Plan lifecycle (set/add/advance/read), decision lifecycle (log/check/refresh/review), entity read/update, wrap (check/auto/commit), setup, audit, and risk/guard are all covered. Gaps exist around entity deletion/archival and explicit entity listing, but these are minor workarounds.