mnemoth
Related Servers
Alternatives to mnemoth
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceProvides persistent, multi-tenant knowledge graph memory for MCP-capable AI tools, allowing them to recall and store entities, observations, and relations across sessions with keyword search.1033 npm3MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to interact with a persistent knowledge graph backend using MCP tools for reading, searching, and analyzing wiki pages with vector search and graph algorithms.4-
- FlicenseNot gradedqualityAmaintenanceEnables agents to work with an embedded graph database over MCP by exposing tools for entity storage, declarative rule creation, similarity search, association explanations, role-filtered queries, and historical edge inspection. It supports building and querying self-maintaining graphs locally with explainable derived relationships.5-
- AlicenseAqualityBmaintenanceProvides persistent, graph-based memory for AI agents via MCP, enabling semantic search, wikilink traversal, reminders, and injection protection.933Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables storing and querying a personal knowledge graph as a shared memory, allowing agents and tools to remember facts, entities, relations, and recall relevant context via natural language hybrid search.1MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI coding agents and IDEs to capture conversations, extract structured knowledge into a queryable graph database, and recall past decisions, patterns, files, and errors across all projects and workspaces. Provides persistent memory tools for saving, searching, and cleaning up knowledge via MCP.2-
TDQS
Scored across 24 tools
Each tool targets a distinct operation or resource: recall searches, history traces provenance, remember writes, supersede/mark_contradiction/forget handle different lifecycle actions, and the session_* tools are clearly separated. Even the candidate-generating tools (contradiction_candidates vs memify_candidates) are distinguished by their output and follow-up tools.
Most tools use snake_case imperative phrases (add_entity_type, merge_entities, set_bucket_summary), but the set mixes in noun-style commands (history, global_context, contradiction_candidates), the session_* prefix sometimes precedes an action (session_get) and sometimes a noun (session_timeline), and memify_candidates is an inconsistent invented form. The overall style is readable, but the conventions are not uniform.
24 tools is on the heavy side for a memory server, though the broad domain (ontology, session management, maintenance, provenance) justifies much of it. A few session/maintenance operations could be consolidated without loss of clarity, making the surface feel slightly bloated.
The core memory lifecycle is well covered: create (remember), read (recall/history/global_context), update (supersede/merge_entities/set_bucket_summary), and delete (forget), plus ontology and session workflows. Minor gaps exist, such as no direct listing of all sessions or entities and no way to create/remove datasets beyond listing/forgetting, but these are workaroundable.