Memoreei
Related Servers
Alternatives to Memoreei
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA self-hosted MCP server that captures, compresses, and indexes AI conversations, enabling persistent cross-session memory for AI assistants via hybrid retrieval.MIT
- AlicenseNot gradedqualityBmaintenanceA self-hosted MCP server that provides a personal semantic memory layer for AI tools. It enables storing, searching, and managing memories using hybrid vector and keyword search, allowing AI assistants to recall information by meaning.MIT
- AlicenseAqualityAmaintenanceA local MCP server that gives AI assistants a long-term memory by capturing sessions verbatim and surfacing relevant context automatically.15917MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server for managing persistent AI memory using hybrid search (keyword + semantic vector) with SQLite storage and offline-first local embeddings.-
- FlicenseNot gradedqualityBmaintenanceA local MCP server for AI assistants to store and retrieve personal memories on disk, with optional semantic search using embeddings.1-
- FlicenseAqualityDmaintenanceAn MCP server that provides AI assistants with long-term semantic memory using a Markdown-based knowledge base with hybrid search (vector + FTS5) and syntax-aware chunking. It supports idempotent ingestion, project isolation, and integrity linting.4-
TDQS
Scored across 24 tools
Three tools—sync, sync_all, and refresh_memoreei—all appear to do essentially the same thing (refresh/re-sync configured sources), making selection confusing. The per-source sync_* tools are clearer, but the trio of generic sync tools creates real overlap that descriptions do not resolve.
Most tools follow a predictable verb_noun pattern (sync_discord, import_messenger, list_sources), but add_memoreei, refresh_memoreei, and search_memoreei inconsistently append the server name while the rest do not. Readable overall but the mixed convention is a notable deviation.
24 tools is on the heavy side (16-25 is borderline), though a broad multi-platform memory ingester legitimately needs many per-source connectors. The count is defensible but feels inflated by redundant generic sync tools.
Ingestion across a wide range of platforms plus search, context retrieval, source listing, and contacts coverage make the surface strong. The main gap is the lack of any delete or update operation for stored memories, leaving a lifecycle dead end.