raggy-mcp
Related Servers
Alternatives to raggy-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides persistent knowledge graph memory for AI agents, enabling them to store, recall, and query facts about people, projects, and relationships across sessions.MIT

Memsolus MCP Serverofficial
AlicenseAqualityDmaintenanceProvides persistent long-term memory for AI agents through semantic search and automated knowledge graph extraction. It enables agents to store, recall, and reason over facts, preferences, and relationships across multiple conversations and sessions.1414 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables persistent, graph-based memory for AI agents, allowing them to store, traverse, and recall relationships between facts, decisions, and context across sessions for efficient reasoning and reduced token usage.MIT

Hebbrix MCP Serverofficial
AlicenseAqualityAmaintenanceProvides long-term memory and a temporal knowledge graph for AI agents, enabling persistent memory and reasoning across sessions.3352 PyPI2MIT- AlicenseNot gradedqualityBmaintenanceProvides coding agents with persistent graph-backed memory, storing decisions, reasons, and contradictions across sessions so conversations pick up where they left off.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides persistent, cross-session memory for AI agents, allowing them to store and automatically retrieve information across different conversations and sessions without repeating context.9 npm175MIT
TDQS
Scored across 11 tools
Tools are largely distinct, but raggy_remember and raggy_capture both create memories, and raggy_context and raggy_recall both handle memory retrieval. Descriptions do separate them well via structured vs unstructured capture and session-start vs targeted lookup, so confusion is unlikely in practice.
All tools share the raggy_ prefix and snake_case formatting, but naming style is mixed: upload, remember, capture, recall, forget, and link are verbs, while context, timeline, threads, and private_sources are noun phrases. There is no consistent verb_noun pattern.
11 tools is well-scoped for a memory/knowledge server covering ingestion, retrieval, deletion, graph linking, and session introspection. Each tool has a clear role and the count feels appropriate rather than bloated or thin.
The set covers upload/list/delete for private sources, capture/remember/forget for memories, context/recall/timeline/threads for retrieval, and link for graph relationships. The main gap is no explicit update/edit operation for a memory, though supersedes links and forget redaction partially address that.