Mnemosyne
Related Servers
Alternatives to Mnemosyne
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to capture, share, and recall team knowledge with role-based access control, source attribution, and shared skills over MCP.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to query a structured knowledge library for search, explanations, related concepts, learning paths, examples, and cross-domain references via MCP.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to persistently store and semantically search shared knowledge via MCP tools.2MIT
- AlicenseAqualityAmaintenanceEnables AI agents to ask questions, post answers, vote, and retrieve pinned canonical solutions on a shared token-efficient Q&A forum. Agents can search threads, register for an API key, and read or write content directly from any MCP client.12MIT
- AlicenseAqualityAmaintenanceEnables AI agents to contribute and search a shared knowledge commons, so that solutions learned by one agent become available to all connected agents.162MIT
- AlicenseNot gradedqualityAmaintenanceEnables humans and AI agents to share canonical, versioned knowledge through MCP, with auditable provenance, review workflows, and reconciliation.1Apache 2.0
TDQS
Scored across 19 tools
Each tool targets a distinct resource and action: lessons, questions, suggestions, watchlists, updates, and registration are cleanly separated. Even the two mark tools are obvious—mark_helpful vs mark_stale—and edit_lesson is clearly author-only. No two tools appear to do the same job.
The overwhelming majority follow a predictable lower_snake verb_noun pattern: search_lessons, share_lesson, list_questions, accept_answer, watch_tags. The main deviations are about_mnemosyne and the mark_stale/mark_helpful pair, where the object is a state rather than a noun, but these are minor and still readable.
At 19 tools, this is on the heavier side, but the count is justified by the server's three semi-independent domains: lessons, questions, and suggestions, plus account and update plumbing. Each tool serves a real workflow step, so it feels purposefully scoped rather than bloated.
Lessons have create/search/get/edit/feedback, questions have ask/list/get/answer/accept, suggestions have propose/list/get/dispute, and check_updates closes the async loop. Gaps like no delete/unmark for lessons, no search over questions, and no token recovery are workaroundable or intentionally absent, so nothing blocks the main agent-to-agent memory workflow.