Geniuz
Related Servers
Alternatives to Geniuz
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenancePrivacy-first personal knowledge database for your AI that ingests data exports (Google Takeout first) and exposes them via MCP tools like search and list items. Runs locally with no cloud or telemetry.MIT

Make0 Brainofficial
AlicenseAqualityAmaintenanceGives every AI agent you use one shared, versioned memory in a local SQLite file, so a fact saved from one app is found by all the others. Runs fully offline with no API key, records which agent wrote each change, and keeps every prior version so nothing is silently overwritten.71,212 npm3MIT- AlicenseAqualityAmaintenancePrivacy-first local document search using semantic search. Runs entirely on your machine with no cloud services, supporting PDF, DOCX, TXT, and Markdown files.94,565 npm426MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to maintain persistent, local memory with retrieval-augmented search, knowledge graphs, and context surfacing, without any cloud dependencies.293 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables natural-language semantic search over a fully local knowledge base, keeping embeddings, storage, and retrieval on the machine.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to share a persistent, local-first memory of architectural decisions, conventions, bug root causes, and session handoffs, searchable via full-text ranking, so context carries across tools and sessions without any cloud dependency.MIT
TDQS
Scored across 3 tools
recall and recall_recent both retrieve memories and are both recommended at conversation start, which could cause initial confusion. However, the descriptions clearly distinguish semantic search from recency-based retrieval, and remember is clearly separate.
All tool names use lowercase snake_case and are readable, with recall and recall_recent sharing a clear prefix. The use of remember as a different verb is intuitive, though not perfectly aligned with the recall_* pattern.
Three tools is well-scoped for a memory server: one for semantic retrieval, one for recent retrieval, and one for storage. Each tool has a distinct role and no tool feels redundant or missing from the core workflow.
The server covers create and two forms of read, but lacks any update, delete, or forget operation. This is a notable lifecycle gap for a memory system where preferences and facts may change or need removal.