reflex-brain
Related Servers
Alternatives to reflex-brain
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that gives AI agents and teams persistent, shared memory using a knowledge graph with vector embeddings, automatic consolidation of related facts, and hybrid search.3-
- AlicenseNot gradedqualityDmaintenanceMCP server providing persistent brain storage for LLM agents, including memory, personality, social intelligence, and context management.1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that provides AI agents with persistent memory, cross-agent sharing, and context management, enabling them to remember conversations, track complex tasks, and evolve skills across tools.2MIT
- AlicenseNot gradedqualityBmaintenanceMCP server that gives AI agents persistent long-term memory, storing and recalling facts, decisions, errors, procedures, and episodes across sessions.40 npm6Apache 2.0
- -licenseNot gradedqualityNot gradedmaintenanceA sophisticated MCP server providing advanced memory capabilities with RAG, hallucination detection, and enterprise-grade AI infrastructure for intelligent agent ecosystems.-
- AlicenseAqualityBmaintenanceAn MCP server providing long-term memory for AI agents with forgetting curves, consolidation, and graph-based retrieval.10MIT
TDQS
Scored across 22 tools
Most tools target a distinct resource+action (remember vs query vs research vs propose_lesson), and the scheduler_* family is clearly scoped. Minor overlap exists between reflex_query and list_lessons/list_skills, and between scheduler_check_coverage and reflex_status, since both report knowledge/state summaries.
All tools share a reflex_ prefix and snake_case, with a clean reflex_scheduler_* sub-namespace. Deviations are mild: several tools are verb-only or noun-only (reflex_status, reflex_snapshot, reflex_research) rather than verb_noun, but the pattern remains readable.
22 tools for a memory/refinement/research brain is at the heavy end; the scheduler alone consumes 8 slots (tasks + triggers + coverage + stats) that could be consolidated. Several pairs (get_lesson/get_skill, list_lessons/list_skills) suggest mergeable surface.
Lifecycle coverage is strong for proposals/refinements (propose, list, get, apply, rollback) and the scheduler (add/remove/list for tasks and triggers), plus retrieval via query/research. However, there is no forget/delete for memories, no update/delete for lessons or skills, leaving dead ends for correcting or pruning stored knowledge.