rmbr
Related Servers
Alternatives to rmbr
AlicenseAqualityDmaintenanceA server that provides data retrieval capabilities powered by Chroma embedding database, enabling AI models to create collections over generated data and user inputs, and retrieve that data using vector search, full text search, and metadata filtering.13590Apache 2.0- AlicenseNot gradedqualityCmaintenanceMCP protocol server exposing Mem0 AsyncMemory API for AI agent context retention1MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceLocal-first AI memory layer with hybrid retrieval and brain-inspired namespaces. Enables agents to save, search, and manage memories directly via MCP tools.5MIT
- AlicenseBqualityCmaintenanceLocal-first persistent memory layer for MCP agents with hybrid search, file ingestion, and GDPR compliance.2024Apache 2.0
- AlicenseNot gradedqualityDmaintenanceLocal-first memory engine that synthesizes entity profiles at ingestion. Enables persistent, reasoning memory for AI agents via MCP tools like add, search, and profile.MIT
- AlicenseNot gradedqualityDmaintenanceLocal-first persistent memory for AI agents via MCP, enabling semantic search and memory sharing across agents with zero cloud cost and full privacy.61MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to store, recall, link, and manage durable local memories using ranked fuzzy search and optional graph context through a compact MCP interface.MIT
- AlicenseCqualityAmaintenanceLocal-first, governable long-term memory for AI agents. Provides SQLite-backed storage, cross-session recall, and traceable memory corrections through a standard MCP interface.401MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: search retrieves from the knowledge base, recall retrieves from the agent's own memory, and remember writes a new memory. The descriptions explicitly cross-reference each other to prevent confusion.
All tool names are single, lowercase verbs (search, recall, remember) that directly describe their action. This is a consistent and predictable naming pattern.
With only three tools, the server is tightly scoped to its core purpose of storing and retrieving memories and reference documents. The count is appropriate for this narrow domain.
The server provides create and read operations for memories but lacks update and delete capabilities, leaving no way to correct or remove stored memories. Additionally, the knowledge base search has no matching tool to add or manage indexed documents, making the surface incomplete for full lifecycle management.