RAMen Connector
Related Servers
Alternatives to RAMen Connector
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityBmaintenanceEnables persistent memory storage and retrieval for MCP clients, allowing AI assistants to remember facts and context across conversations.26 npmMIT
modelbrain-mcpofficial
AlicenseAqualityBmaintenanceEnables MCP clients to connect to a locally running memory layer for AI assistants, providing tools to remember, recall, forget, expand, and sync connectors.14316 npmMIT- FlicenseNot gradedqualityDmaintenanceEnables each user to have a private, per-user memory store that persists across AI tools, allowing them to store, recall, search, list, and delete memories via MCP.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable agents and chat apps to store, recall, pin, and manage hierarchical, provenance-aware memories with deterministic scoring and shared access across clients.401 npm3MIT
- AlicenseNot gradedqualityDmaintenanceProvides persistent, cloud-based memory for AI agents, letting them remember preferences, skills, and decisions across sessions via an MCP-compatible interface.Apache 2.0
- AlicenseAqualityDmaintenanceProvides persistent memory for AI assistants via MCP, enabling them to store and recall facts, preferences, and tasks across conversations using either local file storage or a cloud backend with semantic search.514 npmMIT
TDQS
Scored across 7 tools
The three memory-facing verbs (recall, recall_thread, memory_status) and the thread verbs (save_thread, resume_thread, recall_thread) overlap: recall_thread explicitly searches 'every thread and the user's memory notes', which duplicates recall's territory, and the boundary between resuming a thread and recalling a thread's details requires careful reading. The long descriptions help, but an agent can easily pick the wrong lookup tool.
Patterns are mixed: bare verbs (recall, remember, forget), verb_noun (save_thread, resume_thread, recall_thread), and a noun phrase (memory_status). Individually readable, but there is no single predictable convention an agent can generalize from.
Seven tools for a personal-memory connector is well-scoped: two fact tools, three thread tools, a delete, and a status/settings tool. Each earns its place and nothing feels padded or missing at the count level.
Coverage is solid: create/read/delete for facts, save/resume/read for threads, plus status and settings. Minor gaps exist—no explicit edit/correct operation for a saved fact (only re-remember), and thread listing is only implicit through resume_thread without a name.