brain
Related Servers
Alternatives to brain
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLocal-first, multi-user shared memory for AI agents with semantic search, offline support, and team synchronization.MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to search and retrieve memories from your Mac, including screen captures, meeting transcripts, and browsing history, all locally and privately.1-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to capture, structure, remember, and retrieve source-backed memory as local Markdown files, with reviewable writes and no cloud dependency.213MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to maintain persistent, local memory with retrieval-augmented search, knowledge graphs, and context surfacing, without any cloud dependencies.439 npmMIT
- FlicenseNot gradedqualityCmaintenanceProvides AI agents with persistent, local cross-session shared memory by combining vector semantic retrieval with knowledge graph relationships, and supports short/long-term memory management and local backups.-
- AlicenseNot gradedqualityBmaintenanceGives AI agents a private, on-device persistent memory using semantic search over stored facts, preferences, and decisions. It enables agents to remember information, recall it by meaning even without keyword overlap, delete memories, and list them by tag.7 npm4MIT
TDQS
Scored across 28 tools
Most tools target clearly distinct resources: file editing (append/str_replace/set_frontmatter/write), sources, memory, connections, graph and skills are well separated. The only mild overlaps are among the four write/edit tools and between list_vault and vault_overview, but descriptions make the boundaries clear enough.
Names follow a consistent snake_case verb_noun pattern (append_file, save_url, add_memory, propose_connection). A few are noun-based rather than verb-based (file_history, memory_history, fact_check, vault_overview), but the convention is still predictable and readable.
28 tools is on the heavy side, though the server covers several genuinely distinct sub-domains (files, sources, memory, skills, connections, graph, fact-check). It is borderline rather than bloated, but consolidating the write/edit variants could trim it.
File lifecycle is thoroughly covered (read/write/append/replace/frontmatter/delete/move/history/restore), plus sources, memory, connections and graph. Minor gaps remain: no direct memory read/list or full-text search over plain vault notes, though read_file and search_knowledge partially cover these.