Skip to main content
Glama
charonferries

Mnemosyne

by charonferries
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Mnemosyne

No user-submitted related servers found.

    Related Servers

    • OpenKT

      generalmachines
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to capture, share, and recall team knowledge with role-based access control, source attribution, and shared skills over MCP.
      Apache 2.0

    • knowlib

      uladzimir23
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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

    • AgentBase

      vhspace
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to persistently store and semantically search shared knowledge via MCP tools.
      2
      MIT

    • HiveMind

      AmirK-S
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to contribute and search a shared knowledge commons, so that solutions learned by one agent become available to all connected agents.
      16
      1
      MIT

    • Knoverge

      gynsus
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables humans and AI agents to share canonical, versioned knowledge through MCP, with auditable provenance, review workflows, and reconciliation.
      1
      Apache 2.0
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 19 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources